From: Pip Cet <pipcet@gmail.com>
To: Pip Cet <pipcet@gmail.com>,
Prateek Mehta <prateekmehta.in@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: beamer_env tag issue with empty headlines
Date: Thu, 27 Aug 2015 21:42:32 +0000 [thread overview]
Message-ID: <CAOqdjBeAB7AnZ-ThDNpEqnYcOgjT0cumdZJ6MsxOqGKTmY2qng@mail.gmail.com> (raw)
In-Reply-To: <878u8wtvfb.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
On Thu, Aug 27, 2015 at 6:53 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> 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.
>
IMHO it would be a good idea to reduce the number of regexps anyway; for
example, there are more than twenty regexps trying to match the tags at the
end of the line. (I've fixed that here, and will submit a patch as soon as
the copyright papers have been accepted)
> 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.
>
I think we have three options:
1. declare empty headlines forbidden
2. declare empty headlines allowed, and hope everything goes well
3. declare empty headlines allowed and go through the code making sure we
deal with them everywhere.
My preference is 3, but 1 is better than 2. I'm volunteering to try to find
the time for #3 (if only there were some sort of Emacs extension to help me
organize things better), but can't really promise anything. However, I
think we should make the decision first so it's not a total waste of effort.
I should clarify that I consider only headlines with at least one space
following the stars "empty headlines". A star on a line of its own doesn't
count.
Thanks!
Pip
[-- Attachment #2: Type: text/html, Size: 2861 bytes --]
next prev parent reply other threads:[~2015-08-27 21:42 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
2015-08-27 21:42 ` Pip Cet [this message]
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=CAOqdjBeAB7AnZ-ThDNpEqnYcOgjT0cumdZJ6MsxOqGKTmY2qng@mail.gmail.com \
--to=pipcet@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).