emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scot Becker <scot.becker@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Latex export, unnumbered sections
Date: Mon, 26 Jan 2009 05:24:00 +0000	[thread overview]
Message-ID: <e0e1fe620901252124y263ab4d9id2c90bcf15fc1e0@mail.gmail.com> (raw)
In-Reply-To: <878wozqtap.fsf@selenimh.orion.org>


[-- Attachment #1.1: Type: text/plain, Size: 1926 bytes --]

I'm a new org user, but I've read the LaTeX export stuff pretty carefully,
and In don't think there is any native org-mode syntax that would allows
control over the numbering of an individual line. However, if you know what
level these unnumbered headings will be exported at, you may be able to just
to a Latex pass-through command:

\subsubsection{my unnumbered heading}

Just tested.  It appears to work.

Or you might be able to just figure out how you want the heading to look
(bold, font size, etc) and just pass through the commands to make that work,
just for those lines.

Barring that, I guess the solution is either to edit the LaTeX manually, or
come up with some bit of "unnumbering" syntax and write a LaTeX-adjusting
function that is run on one of the later hooks that are offered by the
export process. I can't find these in org's info documentation just now, but
they were added sometime after v.6.15, if I remember right, and were nicely
documented on the 'user visible changes' page.  That would require some
Emacs LISP, but it should be relatively simple

Scot


On Sun, Jan 25, 2009 at 3:50 PM, Nicolas Goaziou <n.goaziou@neuf.fr> wrote:

> Hello,
>
> I'm running into some kind of problem with my "export as latex and
> process as pdf" setup. I would like to have all my headings numbered
> but a few ones. Sadly, I don't know about any mean to specify
> individually what header should be exported as starred or not.
>
> I still can export to latex, edit it and then process it as pdf, but,
> being the lazy type, I'd rather have it done "automagically".
>
> So, am I missing an obvious option ? Has someone already solved that ?
>
> Thanks for any insight.
>
> --
> Nicolas Goaziou
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 2553 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-01-26 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 15:50 Latex export, unnumbered sections Nicolas Goaziou
2009-01-26  5:24 ` Scot Becker [this message]
2009-01-26 10:45 ` Carsten Dominik
2009-01-26 18:32   ` Nicolas Goaziou
2009-01-26 12:33 ` Bernt Hansen

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=e0e1fe620901252124y263ab4d9id2c90bcf15fc1e0@mail.gmail.com \
    --to=scot.becker@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).