From: Tom Regner <tom@goochesa.de>
To: Mike Gauland <mikelygee@no8wireless.co.nz>, emacs-orgmode@gnu.org
Subject: Re: :wrap behaviour
Date: Thu, 28 Feb 2013 11:32:37 +0100 [thread overview]
Message-ID: <244e84b5-21c1-4d15-ac65-d8d1f1e35b90@email.android.com> (raw)
In-Reply-To: <loom.20130228T092832-498@post.gmane.org>
Mike Gauland <mikelygee@no8wireless.co.nz> schrieb:
>I've been using the :wrap parameter extensively, to give me control
>over the
>formatting of results from code blocks. For files with many such
>blocks, it
>makes sense to specify the formatting at the file level. This works
>well, unless
>I want a particular block to be unwrapped. Just specifying :wrap with
>no
>parameter wraps the output in #+BEGIN_RESULTS...#+END_RESULTS, which is
>*not*
>what I want. The only way to get what I want is to move :wrap from the
>file
>level to each block I *do* want wrapped.
>
>I'd like to be able to disable wrapping for particular blocks. I've
>started
>experimenting with code to do that, but I'm not sure what the best
>behaviour
>should be, and would appreciate suggestions.
>
>Some ideas I've considered:
> + Have :wrap by itself disable wrapping; if you want to wrap in
> BEGIN_RESULTS..END_RESULTS you'll have to specify :wrap RESULTS.
>+ Use a special string (e.g., :wrap off) to disable wrapping. Of
>course,
>this makes it impossible to wrap your output in a BEGIN_OFF..END_OFF
>block,
> should you ever want to do that.
>+ Use a special symbol instead of a string to turn off wrapping (e.g.,
>:wrap
> :off)
>
>Kind Regards,
>Mike Gauland
Hi,
I'd suggest: nowrap
regards
Tom
--
http://www.tomsdiner.de
xmpp: tom@goochesa.de
next prev parent reply other threads:[~2013-02-28 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 8:39 :wrap behaviour Mike Gauland
2013-02-28 10:32 ` Tom Regner [this message]
2013-02-28 20:47 ` Michael Gauland
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=244e84b5-21c1-4d15-ac65-d8d1f1e35b90@email.android.com \
--to=tom@goochesa.de \
--cc=emacs-orgmode@gnu.org \
--cc=mikelygee@no8wireless.co.nz \
/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).