Just to make it clear : I’m not trying to embarrass with trick questions, I’m genuinely wondering what is the expected behavior and how this should be solved. would this line remain a sibling of h2 or should it remain a child of h3 ? # new heading <- typing headings at this level there are a lot of difficult cases, like the one I highlighted above: what is the expectation in this case ? # parent.> that it is no longer obvious which blocks are on which level. So in this case : # H2.2 xxx It becomes problematic when we try to render an outline in such a way, The request to have headings acting as hierarchical markers too (as in most markdown editors) would alter the paradigm as it implies that - dashes and tabs become relative indentations (relative tio their heading’s own indentation), as highlighted in your examples. in current logseq, hierarchy is based on the absolute indentation : no tab = root level, 1 tab=level 1, 2 tabs = level 2, etc (I use tab for convenience, it can apply to 2 spaces or 4spaces too).headings in sub levels are just a display style, they do not impact the hierarchy.top levels headings are treated as a new section (bullet), disregarding the actual number of #.That seems to be what current Logseq do.Īs you noted in current logseq, there are currently two behaviors for headings: The simplest is just literally enter all those markdown formatting on input, just storing them as is. I’ve tested in Logseq v0.2.5 and found that it treats # H2.2.1 as top-level, and make - D2.2.1 as 2nd level (not 3rd). Thanks I was wondering what was the expected output, in fact this markup is working but it’s rendered as a code block in most md editors Also I wanted to see what Logseq do with it after a # block (…) Also because GFM Markdown specs specifically allow such markup and describe how it should be rendered. Why two tabs? Because that defines a 3rd level “-” block in Logseq. Ok : ) this solves part of my initial confusion as you both seemed to agree on the output. I think made a mistake in his example there. But a clever combination of both capabilities would be interesting. What I don’t want is for Logseq to lose its outline capabilities in favour of free text. Then we would have the behaviour of outliners in the outline blocks and a pure Markdown behaviour in the text blocks.So we would need a “way” to determine if we want to create a block as an outline block or as a text block.I understand the contributions so far that we are talking most of the time about mixing either text blocks OR outline blocks within a page.It becomes problematic when we try to render an outline in such a way, that it is no longer obvious which blocks are on which level.not rendering a bullet point in some situations) OR whether we are discussing the behaviour of outliners. It makes a significant difference in the discussion whether we are only talking about visual adjustments (e.g.moving outline blocks (also up and down, taking sub-elements into account).indenting paragraphs in different levels.And by the behaviour of an outliner I mean ….* 1.2.I am not concerned about the style of the headers, but the behaviour. item, second level - 8 spaces possible too item, first level - no space in front the bullet character.item, first level - no space in front the bullet character (as said in the editor-help, just on this page) Ab item, second level - 4 spaces possible tooī item, first level Nested bulleted lists, deeper levels:.Aa item, second level - 1 space is enough. A item, first level - no space in front the bullet character.* Ab item, second level - 4 spaces possible too * Aa item, second level - 1 space is enough * A item, first level - no space in front the bullet character You can see this if you highlight the "code." Note that you have to manually insert line breaks with two trailing spaces on all lines of the list except the last one. German Shepherd: The German Shepherd Dog (GSD, also known as an Alsatian), (German: Deutscher Schäferhund) is a breed of large-sized dog that originated in Germany. I was inspired by DavRob60's attempt at making a faux nested list.
0 Comments
Leave a Reply. |