nvim-neorg / tree-sitter-norg3 Goto Github PK

we need to test the parser in both native build & wasm build because there can be some runtime errors in wasm.

For example: iswpunct() throws error in wasm.

GFM has all it's edge cases as numbered list.
tree-sitter-markdown is following it too.

Numbered list of test cases would be useful to note/filter test cases (e.g. tree-sitter test -f "UNIQUE ID".)

I'm thinking of numbering all test cases like 1.1.1 to easily categorize/filter them.

There are some edge cases when incremental parsing is needed.

Easy example is single-line paragraph for heading title

* heading
* heading

Try remove second * . now second line also be part of first heading’s title.

I’m sure there are more bugs that only occur incremental parsing.
We need some test method for these cases.

Originated here: nvim-neorg/neorg#1318

Feature description

This would allow users to click a concealed link to open it a browser, as is possible in Emacs org-mode. E.g.

See here for more info about OSC 8. See here for some examples.

Most major terminals support it already, and if one doesn't, I don't think printing the sequences will break anything.

Originally posted by @carterprince in nvim-neorg/neorg#1318.

Comments

Currently (v1 + neorg) the link_target_url is mapped to @conceal inside highlight.scm but maybe we can map it to @text.reference as shown in the linked PR?
I might be completely wrong and if it’s more than a hassle, just ignore this plz

@pysan3

that’s cool. unfortunately I’m not sure if my mobile terminal supports OSC8 links.
I’m going to home tomorrow, but I’m planning to do some mobile works in this week. So I’ll keep that in todos and apply when that PR is merged.
@pysan3 can you open an issue on official v3 repo so we can keep track of it?

@boltlessengineer

Blocked by

• neovim/neovim#27109

• neovim/neovim#27132

• What should we do when the terminal doesn't support OSC8? Maybe just make neovim decide?

  • List of supported terminals: https://github.com/Alhadis/OSC8-Adoption/

Hi guys,
I'd like to contribute to your tree-sitter grammar. Is this still maintained? If yes, do you have any tasks at hand?
What is the status of the current grammar?

My longterm goal is to write an LSP for norg files in rust. For this to work I depend on this crate. There is a different grammar published to crates.io. Which one should one pick, this (unpublished) or the published version?