From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: :noweb header argument
Date: Wed, 11 Jan 2012 15:06:39 +0000 [thread overview]
Message-ID: <8739bmcm80.fsf@ucl.ac.uk> (raw)
In-Reply-To: <808vlezmmy.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 11 Jan 2012 09:09:09 +0100")
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Thomas, Eric(s) and all,
Hi Sebastien,
[...]
> I use HTML export more and more, and would be sad if the solution wasn't
> targeted at all to HTML as well.
I agree although this doesn't preclude target specific customisation
variables; it just means that each target would have to have its own
variable. Maybe less aesthetically pleasing than a single org
intermediary but possibly easier to use...
>
> I see rare cases where I wouldn't want to see the code name: if they have a
> name, most of the time, it's because they are referenced one or multiple times
> from elsewhere and you'd better be able to display that information to the
> reader of your LP/RR document.
Well, my case is the opposite! I seldom want the names in the exported
output. That's partly because I tend to name *every* code
block. First, I use yasnippet to insert code blocks and it prompts for
the name; second, I find it good practice as I never know if or when I
might actually want to refer to the code block so naming as I go along
is most convenient; third, most importantly, it makes it possible to
jump to code blocks quickly in a large file!
> Without knowing what it implies, I'd find an extra option rather sexy,
> something such as:
>
> #+OPTIONS: H:4 num:nil noweb-names:t
I would be happy with this!
> The real question is: should we be able to turn that off for some code blocks?
> Not sure, but difficult to answer that it's totally unwanted.
It would be nice but, at least for my use case, not necessary.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.76.ga9c15)
next prev parent reply other threads:[~2012-01-11 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 23:04 :noweb header argument Thomas S. Dye
2012-01-10 8:04 ` Sebastien Vauban
2012-01-10 8:24 ` Andreas Leha
2012-01-10 11:30 ` Eric S Fraga
2012-01-10 15:41 ` Thomas S. Dye
2012-01-10 16:44 ` Eric Schulte
2012-01-10 18:42 ` Thomas S. Dye
2012-01-11 8:09 ` Sebastien Vauban
2012-01-11 15:06 ` Eric S Fraga [this message]
2012-01-14 19:59 ` Eric Schulte
2012-01-14 23:06 ` Thomas S. Dye
2012-01-15 15:28 ` Eric Schulte
2012-01-18 10:03 ` Eric S Fraga
2012-01-18 19:11 ` Yagnesh Raghava Yakkala
2012-01-11 17:17 ` Eric Schulte
2012-01-10 21:04 ` Eric S Fraga
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=8739bmcm80.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).