vhyrro

@SevorisDoe this would actually make the syntax very satisfyingly consistent. Currently URIs cannot have an attached path (obviously): `{:this:https://is-invalid}`. Similarly the `{:path:123}` syntax could be disallowed, but line links to...

@boltlessengineer what are your thoughts on these compromises? Summary: - `{:path:123}` is disallowed - Line numbers within the same file are allowed: `{123}` - The path + line number syntax...

Extra: spec doesn't define what sort of objects are allowed after a single definition (only a paragraph? or any single complex object?)

Since detached modifiers have a higher precedence than attached modifiers it becomes an unclosed `*bold`, a syntax error for the unordered list and then `word*`

> escape sequence can be used to escape non-punctuation character, is this intended behavior? > > ``` > \* - this is common usecase of escape sequence > > \a...

I realized that the current usage of `\\n` within norg is very counterintuitive. Currently when you use the escape character: ```norg here is\ some text ``` The expected result (as...

Image placement is delegated to the currently undocumented `macro` feature set. Its syntax looks like this: ``` .image /path/to/image.png ``` The implementation of the `image` macro is not documented anywhere...

This has been since fixed in the dev branch, but I'll only close this once that gets merged :)

We know as of right now that installation on macos is rather painful. We're also hoping to work with the nvim-treesitter guys to make the process easier. Danymat has a...

@shaunsingh Hm, that's a very weird error. All I can say is that it's unrelated to our TS parser - something at a lower level (presumably on the `tree-sitter` side)...