Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] markdown not rendered correctly #2375

Closed
ghost opened this issue Sep 6, 2018 · 4 comments
Closed

[bug] markdown not rendered correctly #2375

ghost opened this issue Sep 6, 2018 · 4 comments
Labels
bug 🐛 Issue concerns a bug.

Comments

@ghost
Copy link

ghost commented Sep 6, 2018

Current behavior

Markdown not rendered correctly. Not sure if this is a known issue. My apology if it has been reported before.

markdown_error

Expected behavior

git remote set-url origin --push --add <a remote>
git remote set-url origin --push --add <another remote>

markdown in this section messed up

code section even more messed up

git remote set-url origin --push --add <a remote>
git remote set-url origin --push --add <another remote>

Steps to reproduce

  1. create note
  2. copy and paste markdown posted below

```
git remote set-url origin --push --add
git remote set-url origin --push --add
```
markdown in this section messed up

code section even more messed up
```
git remote set-url origin --push --add
git remote set-url origin --push --add
```


Environment

  • Version : 0.11.9
  • OS Version and name : 16.04 Ubuntu
@ghost
Copy link
Author

ghost commented Sep 6, 2018

Update


due to issues in 0.11.8 I set Sanitization to "Allow dangerous html tags". I no longer need this in 0.11.9 and changing the setting to anything else works fine.

@ZeroX-DG
Copy link
Member

ZeroX-DG commented Sep 6, 2018

Solution: If you're having Allow dangerous html tags on in your setting then turn it off. However, this is still a bug so I'll let this issue open till me or someone found the fix for it.

@ZeroX-DG ZeroX-DG added the bug 🐛 Issue concerns a bug. label Sep 6, 2018
@ghost
Copy link
Author

ghost commented Sep 20, 2018

Despite some effort, I am no longer able to replicate this issue. Back then I could definitely reproduce it by changing the Preferences back and forth. Meanwhile I made other changes to my preferences so other dependencies may apply here, or it simply went away after a complete restart?!

@ZeroX-DG
Copy link
Member

In any case, I'll close this issue until someone able to reproduce this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Issue concerns a bug.
Projects
None yet
Development

No branches or pull requests

1 participant