Re: Org lint and named source blocks

2021-10-04 Thread Tom Gillespie
Thanks for the pointer! The actual point of contact seems to be https://github.com/milisims/tree-sitter-org. Good to find another group that is working on this. Best, Tom

Re: Org lint and named source blocks

2021-10-04 Thread Timothy
Hi Tom, > The issue for me is that I don’t have the bandwidth to get started > with a full tree sitter implementation, especially because it is going > to need a custom scanner, and because you’re effectively on your > own when it comes to reconstructing the output of the AST into the > actual int

Re: Org lint and named source blocks

2021-10-04 Thread Tom Gillespie
> By the way, wouldn't it be better to use tree-sitter rather than > something else for the format grammar? Not really since we are going to need more than one implementation using a parser generator to avoid baking implementation specific details into the spec by accident. This is true for more t

Re: Org lint and named source blocks

2021-10-03 Thread Ihor Radchenko
Tom Gillespie writes: >> Should we allow syntax like #+KEYWORD:value to be correct or do we >> require a whitespace/space after colon all the time? > > The spec as written is ambiguous/silent on this issue. In my work on > laundry tokenizer and grammar I have found keyword syntax to be a > thorny

Re: Org lint and named source blocks

2021-10-03 Thread Ihor Radchenko
Ihor Radchenko writes: > This one is tricky. The linter (org-lint-duplicate-name) expects that > NAME keyword must have space before value. However, the actual Org > parser (org-element--collect-affiliated-keywords) does not care about > space. My intuition says that the parser behaviour is > uni

Re: Org lint and named source blocks

2021-09-21 Thread Tom Gillespie
> Should we allow syntax like #+KEYWORD:value to be correct or do we > require a whitespace/space after colon all the time? The spec as written is ambiguous/silent on this issue. In my work on laundry tokenizer and grammar I have found keyword syntax to be a thorny issue, and I strongly suggest th

Re: Org lint and named source blocks

2021-09-21 Thread Ihor Radchenko
Dominik Schrempf writes: > Running =org-lint= on an Org file containing > > #+NAME:Hello > #+BEGIN_SRC emacs-lisp :exports code > #+END_SRC > > I get the following error: > #+begin_quote > Debugger entered--Lisp error: (search-failed "^[ \11]*#\\+[A-Za-z]+: +Hello > *$") > #+end_quote Confirmed

Org lint and named source blocks

2021-09-21 Thread Dominik Schrempf
Thank you for the Haskell fix! I found another issue (not a bug but could be handled better): Running =org-lint= on an Org file containing #+NAME:Hello #+BEGIN_SRC emacs-lisp :exports code #+END_SRC I get the following error: #+begin_quote Debugger entered--Lisp error: (search-failed "^[ \11]*#\