-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
[Enhancement] [2.0] (Option to) hide markup annotations for code blocks #2378
Comments
Not the same option! ☝🏻 |
You prefer this option/toggle/setting to be separate from #2377? I'm happy either way, but for simplicity, I think you can merge this into one option i.e.: Same option: Rendering:
Not the same option: Rendering:
|
Exactly like this. Since I started micro-managing all the rendering options, it would be more confusing if SOME of the rendering options triggered multiple elements (which, strictly speaking, are completely distinct semantically) than if you can actually trigger every single element. I don't have any telemetry so I don't know which things people are using as opposed to what they are not. Could well be that I could actually combine all the rendering options into one single "WYSIWYG" option, but I don't know, and so it's easier to just stick with one mechanism, right? |
That is what I would vote for, and judging from digging through Zettlr topics on Reddit, that's what telemetry would show the more popular option. Like I said, I'm happy to click two boxes (or more, because we also need an option to hide inline code backticks) and forget about it. But I'm not sure that's the right approach against confusion. Because there are already some non-optional hidden annotations: links, tables, and now that I think of it, even images. So there is a third option: Make hiding code block annotations non-optional, just like with links, tables and images. There is also a fourth option: Group all the options into one WYSIWYG, and also add an option for pure colorized markdown mode, where even tables and images are pure markdown. That would mean the option is as follows: Rendering:
|
Haha, don't worry :D What we could ALSO do is allow a radio-control for that:
… whereas the checkboxes are only enabled if you select "choose". Full WYSIWYG would activate everything, Plain Markdown would disable everything. |
I would love to see the three options implemented in Zettlr. I somehow missed this post when I commented on #1634 , which can be ignored in light of this newer thread. |
Hello, I'm checking on this issue to see if you plan to further work on this? In addition to hiding the coding characters, would it be possible to fully hide the heading characters? For now, when I hide them in the preferences, I still see h1, h2, ... Would it be possible to hide them fully? (@Redsandro if it makes sense for you, would it be possible to change the title of your issue to include the heading characters? It would avoid creating a new issue for a very similar issue). This was suggested in #856 but the issue is closed now. Another suggestion: the way Obsidian does it would be really perfect, notably for headings and code block (```)
Thanks again for your great program! |
It appears similar, but header tags are uniquely different in how they work. It is preferred to have one issue per one commit, so closing them can be automated. That's why these are also separate issues:
Header tags are arguably more similar to the former, because code blocks are parsed and themed in a different... well, code block. I recommend you open a new issue and link back to that issue, or both. |
Thanks for all the work here and the great software! I created the issue for headers: #5086 |
I think this issue can be closed, since Code block info strings are now hidden with the emphasis renderer (we can discuss which renderers should affect which element, but this is (a) a different discussion and (b) probably something for the UX side of things) |
Description
Implement an option to hide the markup annotations for markdown code blocks. This would be the same option as #2377, so consider this an upgrade to that issue.
This would make behavior for code-blocks similar to that of links (and to some degree tables), where you only see the markup annotations while the cursor is in the relevant position.
Caveats
When user wants to edit a line in an existing code block, user is likely to place the cursor at the position to be edited. Appearing markup annotations at the beginning of a code block causes the text to jump one line down. This can be compensated to scroll one line up at the same time.
Backlinks: #2369 #2243
The text was updated successfully, but these errors were encountered: