From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: OrgMode ML <emacs-orgmode@gnu.org>,
Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Subject: Re: Inserting a comma as prefix of headlines (in Org code blocks)
Date: Thu, 28 Feb 2013 11:52:37 +0100 [thread overview]
Message-ID: <87ehg0pv62.fsf@gmail.com> (raw)
In-Reply-To: <87y5e8d9rx.fsf@bzg.ath.cx> (Bastien's message of "Thu, 28 Feb 2013 11:15:30 +0100")
Bastien <bzg@altern.org> writes:
> But be prepared for dealing with some stubbornness on my side:
> documenting the parser does not mean every issue should be solved
> thinking in terms of the parser. Sometimes there should be a
> tradeoff between what the parser can parse and what the UI should
> offer.
Obviously, it depends on the tradeoff. For example, `org-fill-paragraph'
contains one. Here is an excerpt of its docstring:
For convenience, when point is at a plain list, an item or a footnote
definition, try to fill the first paragraph within.
This is perfectly fine because it doesn't go against the parser. It
merely acts as if the point was elsewhere in the buffer. But it doesn't
pretend that the buffer is different.
Another possible kind of tradeoff is commands working on a region.
Regions don't mean anything for the parser, so commands acting of them
may ignore what the parser knows about the buffer.
Nevertheless, in other cases, I highly suggest to never discard the
output from the parser. A command ought to always consider that the
parser is correct. So, if it means to go against it, it should be
specified explicitly somewhere (e.g. C-S-up can clearly break the
syntax).
Commands activated through simple keys (i.e. TAB) on basic syntax (i.e.
an headline) shouldn't, IMO, belong to that category, as it would
confuse users even more.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-28 10:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 8:56 Inserting a comma as prefix of headlines (in Org code blocks) Sebastien Vauban
2013-02-27 9:22 ` Bastien
2013-02-27 9:43 ` Nicolas Goaziou
2013-02-27 12:16 ` Bastien
2013-02-27 12:54 ` Nicolas Goaziou
2013-02-27 22:55 ` Bastien
2013-02-27 23:29 ` Nicolas Goaziou
2013-02-28 8:54 ` Bastien
2013-02-28 9:56 ` Nicolas Goaziou
2013-02-28 10:15 ` Bastien
2013-02-28 10:52 ` Nicolas Goaziou [this message]
2013-02-28 11:17 ` Achim Gratz
2013-02-28 21:23 ` Nicolas Goaziou
2013-02-28 16:17 ` François Pinard
2013-02-28 17:02 ` Yagnesh Raghava Yakkala
2013-02-28 19:26 ` François Pinard
2013-02-28 20:06 ` Yagnesh Raghava Yakkala
2013-03-01 16:23 ` Takafumi Arakaki
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=87ehg0pv62.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).