From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Pip Cet <pipcet@gmail.com>
Cc: emacs-orgmode@gnu.org, Prateek Mehta <prateekmehta.in@gmail.com>
Subject: Re: beamer_env tag issue with empty headlines
Date: Thu, 27 Aug 2015 20:53:28 +0200 [thread overview]
Message-ID: <878u8wtvfb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAOqdjBcN2gySb=C3h7-tDvhG_vvCV2VUQg74ejKvZftAa-AFQg@mail.gmail.com> (Pip Cet's message of "Fri, 21 Aug 2015 17:37:27 +0000")
Pip Cet <pipcet@gmail.com> writes:
> Could you explain your reasoning for this in some more detail? I use
> empty headlines + tags (properties, actually) in my "set properties in
> headlines rather than special drawers" code, and I wouldn't want it to
> break even more than it currently is because of this limitation.
The reasoning is that it is a tricky situation, which may not be handled
everywhere in code base, e.g., depending on the regexp used. As
a consequence you're in /terra incognita/ anytime you use such
constructs.
> As you say, there are limitations in both cases, but do you actually
> see headlines beginning with a colon being useful anywhere?
FWIW, I don't even see empty headlines useful anywhere. You can, for
example, use \nbsp{} or some such to hide a headline. But IMO, it looks
weird in overview display and is totally uninformative.
> I don't, but empty headlines are useful for setting tags (or, in my
> case, properties) without making up a title, so in my humble opinion
> it's a clear-cut case to support empty headlines + tags.
Possible. The fact that we're having this discussion means we should
probably choose one option, write it down in Org syntax, then deal with
the bugs. Which option is open for debate. I am not married to any of
them.
Regards,
next prev parent reply other threads:[~2015-08-27 18:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 3:11 beamer_env tag issue with empty headlines Prateek Mehta
2015-08-18 12:43 ` Suvayu Ali
2015-08-19 8:56 ` Nicolas Goaziou
2015-08-19 9:18 ` Prateek Mehta
2015-08-19 9:29 ` Nicolas Goaziou
2015-08-21 17:37 ` Pip Cet
2015-08-27 18:53 ` Nicolas Goaziou [this message]
2015-08-27 21:42 ` Pip Cet
2015-08-19 22:38 ` Rafael
2015-08-20 1:22 ` Nicolas Goaziou
2015-08-20 17:15 ` Rafael
2015-08-21 11:51 ` Nicolas Goaziou
2015-08-21 16:43 ` Rafael
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 22:01 Prateek Mehta
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=878u8wtvfb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=pipcet@gmail.com \
--cc=prateekmehta.in@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).