From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [babel] Purpose of :results raw
Date: Sun, 21 Apr 2013 18:43:50 -0700 [thread overview]
Message-ID: <CAJcAo8sG6mpWBqR7-nbJ_yAJeK9Vvss926iB6JGwK8Kz9cSXgQ@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8uRp8xOk+_cZefMc8PBfMDywzARdkTyCR_FDuXCLjAnZA@mail.gmail.com>
[headers were somehow set to other than the mailing list itself.
maybe a gmane bug?]
On 4/20/13, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> I will slowly integrate org-element-at-point in core interactive
> functions, like visibility cycling. Though, fontification will have to
> wait, because the parser isn't ready for that yet.
In the grand scheme, this might be a minor point, but:
While consistency is a good thing, I am nevertheless glad for that
last point. I am concerned that incorporating the parser into
fontification will break inline footnotes that have more than one
paragraph (unless it is designed to be flexible enough to allow that).
To me, paragraphs naturally fit in inline footnotes, just as they do
in non-inline ones, but that is incompatible with the current parser,
which treats paragraphs as semantically larger units than inline
footnotes.
I appreciate your workaround for making them work again in export,
which works. Fontification currently works perfectly also as it
always has; I just don't want that to stop working for those who, like
me, use inline footnotes similarly to non-inline ones, occasionally
with more than one paragraph.
This of course leaves us open to the accusation that nobody should be
so long-winded in a footnote as to have more than one paragraph (and
quotes and more, which currently work perfectly, <ahem>), but the same
would apply to non-inline footnotes also, and Org is in any case by
tradition highly flexible.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY
can get it. There is NO hope without action. This means YOU.
next prev parent reply other threads:[~2013-04-22 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 22:11 [babel] Purpose of :results raw Sebastien Vauban
2013-04-19 22:27 ` Nicolas Goaziou
2013-04-20 7:14 ` Sebastien Vauban
2013-04-20 11:52 ` Nicolas Goaziou
[not found] ` <CAJcAo8uRp8xOk+_cZefMc8PBfMDywzARdkTyCR_FDuXCLjAnZA@mail.gmail.com>
2013-04-22 1:43 ` Samuel Wales [this message]
2013-04-20 21:34 ` John Hendy
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=CAJcAo8sG6mpWBqR7-nbJ_yAJeK9Vvss926iB6JGwK8Kz9cSXgQ@mail.gmail.com \
--to=samologist@gmail.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).