From: Ihor Radchenko <yantar92@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Sebastian Miele <sebastian.miele@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Empty headline titles unsupported: Bug?
Date: Sun, 23 May 2021 22:33:19 +0800 [thread overview]
Message-ID: <878s45bjv4.fsf@localhost> (raw)
In-Reply-To: <87sg2d4k9k.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Because, as I wrote, this is ambiguous. You cannot distinguish the
> following two cases:
>
> * :mytag:
> * :myheadline:
Makes sense.
> So, your patch would only move the problem elsewhere.
Actually, my patch would solve the existing inconsistency.
Org mode already puts tag fontification on :tag: in "* :tag:" headline;
org-get-tags returns ("tag") on such headline; org-set-tags sets the
:tag: on "*" headline making it look like "* :tag:" (which is even
tested in test-org/set-tags); org-tag-line-re used across the
codebase also parses "* :tag:" as headline containing tags. It is only
the org-element parser that does not recognise the :tag: in empty
headline.
> I suggest to not tag emptiness. `org-set-tags' could raise an error in
> this case.
Of course, we can go the other way around and recognise "* :myheadline:"
as non-empty headline with no tags. Though it will be more tricky than
simply changing `org-set-tags' as you suggest.
Best,
Ihor
next prev parent reply other threads:[~2021-05-23 14:29 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 [this message]
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
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=878s45bjv4.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=sebastian.miele@gmail.com \
/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).