From: Nicolas Goaziou <firstname.lastname@example.org> To: Sebastian Miele <email@example.com> Cc: firstname.lastname@example.org, David Masterson <email@example.com> Subject: Re: Empty headline titles unsupported: Bug? Date: Tue, 25 May 2021 18:10:14 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Sebastian Miele's message of "Tue, 25 May 2021 13:43:58 +0200") Hello, Sebastian Miele <firstname.lastname@example.org> writes: > Sebastian Miele <email@example.com> writes: >>David Masterson <firstname.lastname@example.org> writes: >>> Sebastian Miele <email@example.com> writes: >>>> Currently org-syntax.org says that "TITLE can be made of any >>>> character but a new line. Though, it will match after every other >>>> part have been matched." This does not reflect the currently >>>> effective behavior that "* :t:" is a headline with title ":t:" and no >>>> tags. >>> >>> Can you describe what should happen in a parser grammar (ie. BNF)? If >>> not, I would tend toward rethinking the structure of the Org file so >>> that it can be described in a grammar. Having a good grammar for Org >>> files will promote it's acceptance beyond Emacs. >> >> [...] However, the way I understand the above quote from >> org-syntax.org (which is, I think, in the end preferable) [...] > > To be clearer: Preferable to the way it currently is implemented. > > In the headline "* :t:", the above quote from org-syntax.org (at least > in my way of reading it) means TAGS ":t:" This is your way of reading it, but it's unfortunately not the sole way to look at it. Also, I'm sympathetic to Ihor Radchenko's desire to see consistent code in that area. But being consistent means we favor one interpretation over the other. We can do that, of course, but I can't see which one is better. The one you prefer might be more common, but it is also nicer to fix, by adding some space-like character in the headline. Fixing it the other way requires the same space after the headline. Of course it's not a big deal either way. The whole thread isn't, actually. Currently, what Org does in this situation is unimportant, because the behaviour is simply undefined, which is, IMO, tolerable. If we decide to define it, it needs to be documented. Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2021-05-25 17:13 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-22 11:15 Sebastian Miele 2021-05-22 12:21 ` Nicolas Goaziou 2021-05-23 4:45 ` Ihor Radchenko 2021-05-23 14:06 ` Nicolas Goaziou 2021-05-23 14:33 ` Ihor Radchenko 2021-05-23 14:55 ` Nicolas Goaziou 2021-05-23 15:22 ` Ihor Radchenko 2021-05-24 11:01 ` Sebastian Miele 2021-05-24 10:37 ` Sebastian Miele 2021-09-26 9:04 ` Bastien 2021-09-26 23:47 ` Tom Gillespie 2021-09-27 19:59 ` Nicolas Goaziou 2021-09-29 11:26 ` Bastien 2021-05-24 10:46 ` Sebastian Miele 2021-05-24 22:17 ` David Masterson 2021-05-25 10:43 ` Sebastian Miele 2021-05-25 11:43 ` Sebastian Miele 2021-05-25 16:10 ` Nicolas Goaziou [this message] 2021-05-25 21:04 ` David Masterson 2021-05-25 23:06 ` Tim Cross 2021-05-26 23:37 ` David Masterson 2021-05-26 14:07 ` Ihor Radchenko 2021-05-26 23:42 ` David Masterson 2021-05-27 3:29 ` Ihor Radchenko 2021-05-27 22:35 ` David Masterson 2021-05-28 5:36 ` Tom Gillespie 2021-05-29 6:21 ` David Masterson 2021-05-29 6:54 ` Tom Gillespie 2021-05-29 8:04 ` Ihor Radchenko 2021-05-29 19:33 ` Tom Gillespie 2021-05-30 4:06 ` Ihor Radchenko 2021-05-29 14:09 ` Ihor Radchenko 2021-05-30 2:19 ` David Masterson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Empty headline titles unsupported: Bug?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).