Seongmin Lee

Oh I get it now. I haven’t thought like that. Sorry for misunderstanding.

If escaped character cannot occur after a closing attached modifier, how can I write `bold:word` with only “bold” as bold and `:word` as literal characters? ``` *bold*:\word ``` Should I...

I agree that it is useful when linking to source code file. Maybe we can change the behavior of line number linking to only support source code files. Norg is...

That still leaves the main problem: line number can be changed in same Norg document. i.e. ``` some paragraph with multiple lines target paragraph see line {7} ``` This Norg...

> In the case that the link modifier is opening (the attached modifier appears on the right): > - The link modifier may only be preceded by a regular character...

I agree what you said @vhyrro . Consistency is definitely one of most important parts in Norg syntax. But still, line number would only works well for `/` modifier. `{*...

Sorry for the lack of explanation. I meant to add syntax to the `/` modifier itself to make the line number only work on external files. This is more concise...

Ok, then how about allow existing line number links only at the end of scoping? Because line number _between_ scopes is nonsense. We usually need line number only at the...

whitespace/end-of-line rules in link destination: ``` {/ pa th/to /file.txt} {:pa th/t\ o/file:} {:path/t\ o/file:} ```

### link destinations should be case-insensitive I couldn't find this in doc, but Neorg seems to be working like this. ``` $ Paragraph Break description ... {$ Paragraph Break} ......