From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Inconsistency in src block hiding
Date: Sun, 11 Dec 2011 15:08:50 +0100 [thread overview]
Message-ID: <87k4632ob1.fsf@gmail.com> (raw)
In-Reply-To: <87ehwbdxk2.fsf@gnu.org> (Bastien's message of "Sun, 11 Dec 2011 14:53:33 +0100")
Bastien <bzg@altern.org> writes:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> The attached patch entirely removes the #+name and #+results based
>> hiding. Note that the existing "wrap" argument to the ":results" header
>> argument will wrap results in a block which allows easy tab-based result
>> hiding.
I didn't notice it before, but the wrap option from :results property
could also be removed. Unlike to every other block "#+begin_results"
doesn't add any meaning. Its sole purpose is to group some Org data,
which is the job of drawers.
Moreover, it's already easy to install results in a block (I use it to
center results). You only need to put the results line in an appropriate
location and evaluate the code block, like in the following:
--8<---------------cut here---------------start------------->8---
#+name: four
#+begin_src emacs-lisp
(+ 2 2)
#+end_src
#+begin_center
#+results: four
#+end_center
--8<---------------cut here---------------end--------------->8---
Note that the wrap argument may be used instead to wrap results in
a :RESULTS: drawer, but that default drawer would have then to be added
to the `org-drawers' list, and, in the end, wouldn't be very practical.
In my opinion, we should forget any will to automatically group results
(because there is no option more interesting than others) and let the
user decide what suits him the best.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2011-12-11 14:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 10:00 [BUG] Inconsistency in src block hiding Nicolas Goaziou
2011-11-20 15:53 ` Eric Schulte
2011-11-20 19:33 ` Nicolas Goaziou
2011-11-21 18:24 ` Eric Schulte
2011-11-22 16:15 ` Eric Schulte
2011-11-22 18:19 ` Nicolas Goaziou
2011-11-22 23:23 ` Eric Schulte
2011-11-23 15:25 ` Nicolas Goaziou
2011-11-28 8:09 ` Eric Schulte
2011-12-11 13:53 ` Bastien
2011-12-11 14:08 ` Nicolas Goaziou [this message]
2011-12-11 16:25 ` Eric Schulte
2011-12-11 16:04 ` Eric Schulte
2011-12-11 17:04 ` Bastien
2012-01-17 2:26 ` Bernt Hansen
2012-01-17 17:49 ` Nicolas Goaziou
2012-01-17 17:59 ` Bernt Hansen
2012-01-18 10:45 ` Leo Alekseyev
2012-01-18 16:02 ` Rick Frankel
2012-01-18 16:19 ` Eric Schulte
2012-01-18 17:36 ` Nicolas Goaziou
2012-01-19 12:10 ` Martyn Jago
2012-01-19 14:48 ` Eric Schulte
2012-01-19 15:22 ` Rick Frankel
2012-01-19 19:18 ` Nicolas Goaziou
2012-01-19 14:41 ` Eric Schulte
2012-01-19 19:26 ` Nicolas Goaziou
2012-01-24 3:41 ` Eric Schulte
2012-01-24 4:23 ` Leo Alekseyev
2012-01-24 4:44 ` Jambunathan K
2012-01-24 7:59 ` Andreas Leha
2012-01-24 20:39 ` Nicolas Goaziou
2012-01-28 16:08 ` Nicolas Goaziou
2012-01-25 0:00 ` Nick Dokos
2012-01-25 2:23 ` Bernt Hansen
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=87k4632ob1.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@altern.org \
--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).