From: Nick Dokos <nicholas.dokos@hp.com>
To: Sebastian Hofer <sebhofer@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: latex export - skipping lvls breaks export
Date: Tue, 22 Jun 2010 10:41:50 -0400 [thread overview]
Message-ID: <5028.1277217710@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Sebastian Hofer <sebhofer@gmail.com> of "Tue, 22 Jun 2010 13:10:01 +0200." <8739wfmigm.wl%sebhofer@gmail.com>
Sebastian Hofer <sebhofer@gmail.com> wrote:
> At Tue, 22 Jun 2010 11:51:30 +0200,
> Giovanni Ridolfi wrote:
> >
> > Sebastian Hofer <sebhofer@gmail.com> writes:
> >
> > > I'm working on a customized latex-export-class for a CV.
> > nice!
> > > I noticed that if you skip a level in the outline structure
> > > (cf. example below) it is not exported to latex.
> > > Is there a reason for this
> > IIRC it depends in how is written the LaTeX export.
> > (I thought I've read recently this answer by Carsten, but, unfortunately,
> > I can't find the citation in the list archive)
> >
> > > or could this be changed easily?
> > IMHO skipping a level it's <Spock voice> a bit illogical
> > ;-)
> I guess it depends on the situation, it may or may not be illogical.
> Anyway, I don't see a reason why the user should not be allowed to decide himself or herself to skip a level.
>
If the outline tree were a real tree, skipping a level would be
equivalent to chopping out a node somewhere in the middle. Would you
expect the tree to stay intact?
Tongue-firmly-in-cheek-ly yours,
Nick
prev parent reply other threads:[~2010-06-22 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 17:52 latex export - skipping lvls breaks export Sebastian Hofer
2010-06-22 9:51 ` Giovanni Ridolfi
2010-06-22 11:10 ` Sebastian Hofer
2010-06-22 12:51 ` Robert Hennig
2010-06-22 13:06 ` Carsten Dominik
2010-06-22 14:40 ` Sébastien Vauban
2010-06-22 14:43 ` Sebastian Hofer
2010-06-22 14:41 ` Nick Dokos [this message]
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=5028.1277217710@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebhofer@gmail.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).