From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: [babel] Feature request, was Re: [bug] [babel] results eat up following text
Date: Sun, 30 Jan 2011 14:33:45 +0000 [thread overview]
Message-ID: <87zkqifol2.fsf_-_@ucl.ac.uk> (raw)
In-Reply-To: <87wrln1zt7.fsf@gmail.com> (Eric Schulte's message of "Sat, 29 Jan 2011 08:42:44 -0700")
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi Eric,
>
> Thanks for catching this issue. It turns out this was a result of
> adding lists as supported output types, the code block thinks that the
> enclosing list is the results list, and deletes it before inserting new
> results.
>
> Luckily this was a quick 2-character change, which has been committed.
>
> Cheers -- Eric
Eric,
maybe this will also be a quick change...
I have a (very low priority) feature request: as I often have babel
source code blocks within lists, it would be nice if the #+results line
were generated to be indented to the same level as the #+begin_src
&/or #+begin_end lines. Babel appears to generate a results header with
only 2 spaces before it, if no such line exists already, regardless of
the indentation of the code block.
However, if the results header is already there, the indentation is
preserved, which is really nice! This is why it's a low priority
request: it's straightforward enough to indent the line the first time
it is generated!
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.4 (release_7.4.260.gba0f6.dirty)
prev parent reply other threads:[~2011-01-30 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 20:30 [bug] [babel] results eat up following text Eric S Fraga
2011-01-29 15:42 ` Eric Schulte
2011-01-29 21:51 ` Eric S Fraga
2011-01-30 14:33 ` Eric S Fraga [this message]
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=87zkqifol2.fsf_-_@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).