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

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: Tue, 10 Jan 2012 11:30:43 +0000	[thread overview]
Message-ID: <8739bn7q1o.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <801ur8rnjg.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 10 Jan 2012 09:04:35 +0100")

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

[...]

> Some time after that, we had block names in the HTML/PDF output, but not
> anymore.

I've been wondering about this for some time.  The appearance of source
code block names in exported latex output comes and goes in what appears
to me as a random process!  Personally, I don't want these names
exported *ever* as they cause problems with latex, my usual target,
especially because the # sign is interpreted by latex as an argument to
a macro which typically doesn't make sense.

My most recent use of exporting code blocks has not included the names,
so I'm happy.  However, only a couple of weeks ago, the names were
exported.  That was for a different file so maybe my settings were
different?

It would be nice to have some clarity on when names will appear or not
and how this can be controlled.  I've looked at the manual but have not
found any reference to how code block names are treated on export.  Any
pointers would be most welcome!

Thanks,
eric

PS - apologies for possibly hijacking this thread.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.67.g56c73)

next prev parent reply	other threads:[~2012-01-10 11:30 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 [this message]
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
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=8739bn7q1o.fsf@pinto.chemeng.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

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