From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [BUG] Inconsistency in src block hiding Date: Sun, 11 Dec 2011 09:25:39 -0700 Message-ID: <87y5uj6obx.fsf@gmx.com> References: <8739djqfkv.fsf@gmail.com> <87fwhiwwr0.fsf@gmail.com> <87bos6pp1a.fsf@gmail.com> <8739dhnxjs.fsf@gmail.com> <87ipmcxboo.fsf@gmail.com> <87pqgjipu8.fsf@gmail.com> <87y5v6x3lv.fsf@gmail.com> <87fwh86533.fsf@gmail.com> <87ehwbdxk2.fsf@gnu.org> <87k4632ob1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:55224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RZmfp-0000Gf-PC for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:54:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RZmfo-0002xG-70 for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:54:49 -0500 Received: from mailout-us.gmx.com ([74.208.5.67]:54507 helo=mailout-us.mail.com) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RZmfn-0002x3-Sf for emacs-orgmode@gnu.org; Sun, 11 Dec 2011 11:54:47 -0500 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Bastien , Org Mode List Nicolas Goaziou writes: > Bastien writes: > >> Eric Schulte 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: > > #+name: four > #+begin_src emacs-lisp > (+ 2 2) > #+end_src > > #+begin_center > #+results: four > #+end_center > One major utility of the wrap :results header argument is that it allows blocks of raw Org-mode text returned by a code block to be automatically replaced on every execution. This is possible because the wrapping block is used to delimit the result in the Org-mode file. This is not possible with your solution above. > > 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. > I agree a :RESULTS: drawer would be a more meaningful way to wrap code block results. I don't see why such a solution is not practical. I just pushed up a change that defaults to wrapping results in new RESULTS drawers rather than blocks. > > 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. > I would disagree because of the result delimitation functionality mentioned above. Best, -- Eric Schulte http://cs.unm.edu/~eschulte/