Suhail Singh <suhailsingh...@gmail.com> writes: > Ihor Radchenko <yanta...@posteo.net> writes: > >> Oops. >> I amended the fix now. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6c862699a > > It's better, but not quite there. For instance, tangle the block below > into an org file and observe the reported warning. > > #+begin_src org :tangle /tmp/misplaced-heading-mre-2.org > - Some words > ,#+RESULTS: > : this is a line with asterisks** in the middle > > #+end_src
Thinking some more about it, I am of the opinion that instead of allowing some select elements (as is currently done for comment-block, example-block, export-block, src-block), it might be better to *only* trigger the warning for select elements from org-element-all-elements. E.g., paragraph. For instance, it seems silly to trigger the warning in a table-row, or a babel-call etc. #+begin_src org :tangle /tmp/misplaced-heading-mre-3.org | Blah | Hello** world | | | | #+call: blah :var foo="hello** world" #+end_src On a related note, what specific situation(s) was this checker intended to help the user in? I.e., what are the situations that could result in misplaced headings? While the checker seems to be similar to the 'misplaced-planning-info checker in spirit, the difference (in reality) is that the regular expression to detect possibly misplaced headings is much easier to get false positives for. -- Suhail
