From: Eric Schulte <schulte.eric@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Error with :wrap org in babel and 8.0-pre
Date: Mon, 15 Apr 2013 20:37:41 -0600 [thread overview]
Message-ID: <87k3o3dwui.fsf@gmail.com> (raw)
In-Reply-To: <m1y5cj9wmn.fsf@poto.westell.com> (Thomas S. Dye's message of "Mon, 15 Apr 2013 13:56:00 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Hi all,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>>>
>>> - Can we prune some options/syntax that's no longer necessary? For
>>> example, what does =:wrap= (no argument provided) do?
>>
>> Wrap has been deprecated for some time. Perhaps it has been long enough
>> that we can go ahead and remove it entirely from the code and
>> documentation at this point.
>>
>
> I think :wrap is useful. It provides a very direct way to generate code
> that can be exported to an arbitrary LaTeX environment. Say I find a new
> LaTeX package that defines a =cutemarkup= environment, so I want
> something like this the LaTeX file:
>
> \begin{cutemarkup}
> ...
> \end{cutemarkup}
>
> Then, with babel:
>
> #+begin_src lang :wrap cutemarkup
> ...
> #+end_src
>
> gets me what I want,
>
> #+begin_cutemarkup
> ...
> #+end_cutemarkup
>
> IIRC, this is one reason why :wrap is there (thanks, Eric).
>
> Perhaps this result is possible some other way? I don't know, but it
> seems to me that :wrap is still potentially useful and we might want to
> keep it around.
>
> Tom
Hi Tom,
This is a reasonable use case, and I personally don't know of another
way to get these results. So I guess it is just the use of wrap to
delimit Org-mode results which is deprecated, and we *do* still have a
use for the ":wrap" header argument in general.
Thanks,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-04-16 2:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 22:45 Error with :wrap org in babel and 8.0-pre John Hendy
2013-04-12 22:24 ` Eric Schulte
2013-04-15 17:59 ` John Hendy
2013-04-15 18:12 ` Eric Schulte
2013-04-15 19:35 ` John Hendy
2013-04-15 19:48 ` Andreas Leha
2013-04-15 19:52 ` John Hendy
2013-04-15 19:56 ` Nicolas Goaziou
2013-04-15 20:05 ` John Hendy
2013-04-15 20:15 ` Nicolas Goaziou
2013-04-15 20:28 ` Eric Schulte
2013-04-15 20:51 ` Sebastien Vauban
2013-04-15 21:29 ` John Hendy
2013-04-15 21:44 ` Sebastien Vauban
2013-04-15 21:51 ` John Hendy
2013-04-15 21:24 ` John Hendy
2013-04-15 21:42 ` Sebastien Vauban
2013-04-15 22:38 ` Eric Schulte
2013-04-15 22:48 ` John Hendy
2013-04-15 23:27 ` Eric Schulte
2013-04-15 23:56 ` Thomas S. Dye
2013-04-16 2:37 ` Eric Schulte [this message]
2013-04-16 7:58 ` Sebastien Vauban
2013-04-16 8:23 ` Christian Moe
2013-04-16 14:58 ` John Hendy
2013-04-16 15:24 ` Eric Schulte
2013-04-16 21:06 ` Christian Moe
2013-04-15 20:09 ` Sebastien Vauban
2013-04-15 20:22 ` Nicolas Goaziou
2013-04-15 19:56 ` Eric Schulte
2013-04-15 19:47 ` Sebastien Vauban
2013-04-15 21:38 ` 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=87k3o3dwui.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--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
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).