From: Sebastian Miele <sebastian.miele@gmail.com>
To: David Masterson <dsmasterson92630@outlook.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Empty headline titles unsupported: Bug?
Date: Tue, 25 May 2021 13:43:58 +0200 [thread overview]
Message-ID: <87lf83kphd.fsf@gmail.com> (raw)
In-Reply-To: <87o8czksaq.fsf@gmail.com>
Sebastian Miele <sebastian.miele@gmail.com> writes:
>David Masterson <dsmasterson92630@outlook.com> writes:
>> Sebastian Miele <sebastian.miele@gmail.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:" (which is an "other part [to
be] matched [before the TITLE]") and TITLE "" (which is matched "after
every other part").
But the way Org currently is implemented is different in such cases (no
TAGS, the ":t:" is the TITLE).
next prev parent reply other threads:[~2021-05-25 11:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 11:15 Empty headline titles unsupported: Bug? 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 [this message]
2021-05-25 16:10 ` Nicolas Goaziou
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 \
--in-reply-to=87lf83kphd.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=dsmasterson92630@outlook.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).