emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric Schulte <eric.schulte@gmx.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] :wrap header documentation
Date: Wed, 11 Jan 2012 19:44:17 -0700	[thread overview]
Message-ID: <87obu97i7y.fsf@gmx.com> (raw)
In-Reply-To: <m11ur5650i.fsf_-_@tsdye.com> (Thomas S. Dye's message of "Wed, 11 Jan 2012 16:14:53 -1000")

Hi Tom,

Thanks for this patch, I've just pushed up an augmented version which
more closely matches the current behavior.

tsd@tsdye.com (Thomas S. Dye) writes:

> Hi Eric,
>
> Attached please find a first draft of a patch for the manual entry
> documenting a :wrap header argument.
>
> All the best,
> Tom
>
>
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Eric Schulte <eric.schulte@gmx.com> writes:
>>
>>> Achim Gratz <Stromeko@nexgo.de> writes:
>>>
>>>> tsd@tsdye.com (Thomas S. Dye) writes:
>>>>> The attached patch defines a new header argument, :special, which wraps
>>>>> the results of Org babel source block execution in a #BEGIN_ ... #+END_
>>>>> block.  The block name is taken from a new variable
>>>>> org-babel-wrap-special, which is initialized as "results".
>>>>
>>>> What is the rationale for feeding the block name via a configuration
>>>> variable rather then a value to the header argument ":special"?
>>>>
>>>>
>>>> Regards,
>>>> Achim.
>>>
>>> Attached is an alternate patch and an example of its use.  This patch
>>> introduces a ":wrap" header argument which accepts an optional value
>>> used to specify the name of the block with which to wrap results.  If
>>> this looks workable we could push it up once it gets some documentation
>>> and tests.
>>>
>>> Cheers,
>>>
>>>
>>> #+Title: demonstrating the new :wrap header argument
>>>
>>> #+begin_src emacs-lisp :wrap schulte
>>>   '((1 2)
>>>     (3 4))
>>> #+end_src
>>>
>>> #+results:
>>> #+BEGIN_schulte
>>> | 1 | 2 |
>>> | 3 | 4 |
>>> #+END_schulte
>>
>> Hi Eric,
>>
>> Thanks for the :wrap header argument.  It works for me.
>>
>> The attached patch on top of your patch looks for :wrap drawer, and puts
>> the result in a drawer, rather than wrapping the results in #+begin
>> ... #+end.
>>
>> What I'm trying to do is make :results wrap obsolete.
>>
>> Also, note that with the :wrap header argument, :results org and
>> :results latex are both redundant.  I'm not sure how you want to handle
>> this--whether to leave them in place or remove them.
>>
>> I'll volunteer to work on the documentation.
>>
>> All the best,
>> Tom

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

next prev parent reply	other threads:[~2012-01-12  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 16:12 [PATCH] Add :special header argument Thomas S. Dye
2012-01-08 18:24 ` Achim Gratz
2012-01-08 19:58   ` Eric Schulte
2012-01-08 21:31     ` Thomas S. Dye
2012-01-12  2:14       ` [PATCH] :wrap header documentation Thomas S. Dye
2012-01-12  2:44         ` Eric Schulte [this message]
2012-01-12  4:09           ` Thomas S. Dye

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=87obu97i7y.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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

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).