emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scot Becker <scot.becker@gmail.com>
To: nicholas.dokos@hp.com
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export: Skip headline lines? "Paragraph" sectioning?
Date: Mon, 30 Aug 2010 06:14:48 +0100	[thread overview]
Message-ID: <AANLkTik26x8sOE3ZnZ8EMuKZSbrmqbDapdJ1B9KY-+Mb@mail.gmail.com> (raw)
In-Reply-To: <15790.1283141198@gamaville.dokosmarshall.org>


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

He wants to write up a document using org-mode's outline facilities as a
skeleton to help him build up, navigate and visualize his document, but then
he wants only to use SOME of the headlines but ALL of the text when he
actually makes a printed version for others to read.   I've wanted this as
well, since when you think about it the structure you need as a writer may
not be the structure you want to pass on to your readers.

I'd be glad to see a formal feature for this in org-mode, and even more glad
if I could figure out a good way to basically keep up to two headlines per
'node' (org section): one for me while I'm writing (the outline of my
argument, in sentence form, say) and another for export (the catchy
'heading' which goes---for some headings only---in the printed output).

Until we get something like that, Alan, you could just use a little manual
work (or some elisp and one of org's export hooks) to help manage something
like this:

1) choose a :tag: for "don't print this headline (just the text under it)"
2) If you want to keep those headings in the file (I assume you do), then
when you want to export, you'll want to make a temporary (saved) copy of the
file somewhere then:
3) use emacs' "M-x flush-lines" to kill lines with that tag just before
export.

As for exporting lists as \paragraph{} sections, I'm not sure.  But on this
you might take nick's suggestion and give a sample input and output file to
help visualize (and show us) what you're asking for.  And do make sure your
org lists are compatible with the new list definitions (see recent
discussions elsewhere on this list).  When you do this kind of thing it
becomes critical that you pay attention to what constitutes a new item and
the end of the list.

As you'll see org-mode's latex export is currently designed to use org for
basic document structuring and only allows for a limited set of mappings
between org's structure and latex structure.  But you'll see in the latex
configuration documentation that it is possible to define what kind of
\section{}, \chapter{}, or \subsubparagraph{} is exported for each level of
org's headlines.

Also have a look at the documentation for the latex package 'easylist'  It's
not what you're asking for here, but you may find it interesting if you want
to get structured thought-outlines out to paper.  It basically takes
something like an org-mode header list and typesets in latex as nested
(numbered or un-numbered) lists, i.e. not as LaTeX headers.


Scot









On Mon, Aug 30, 2010 at 5:06 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> Alan E. Davis <lngndvs@gmail.com> wrote:
>
> > Sometimes, I have used outliners, like ThinkTank, to organize my
> > thoughts, and reorganize the structure of a document of whatever kind.
> > I don't need headings or sectioning in some cases.
> >
> > I have not found a way to exclude heading lines from
> > LaTeX output in Orgmode, nor have I found a
> > tag to say, "omit this headline."  I do see the variables
> > org-export-exclude-tags, and org-export-select tags; as well as an
> > option to include a specific number of headings as LaTeX sections.  In
> > the later case, other  headings are exported as plain list items, not
> > what I have in mind.
> >
> > A related issue perhaps: what would it take to export, say list items,
> > as "paragraph" and "subparagraph" sections in LaTeX.
> >
> > The ability to export a pdf almost automatically through LaTeX, even
> > with images, is magical.  Many thanks for this.
> >
>
> Some examples might help. I may be particularly dense tonight but I have
> read your mail a few times and I still have no idea what you are asking
> (or rather I have multiple ideas, none of which make much sense to me.)
>
> Thanks,
> Nick
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please 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: 4956 bytes --]

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

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

  reply	other threads:[~2010-08-30  5:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  6:28 Questions about org-capture templates and usage Alan
2010-12-05 11:58 ` Matt Lundin
2010-12-06  3:59   ` Bernt Hansen
2010-12-06  5:02     ` Alan E. Davis
2010-12-06  8:20       ` Carsten Dominik
2010-12-06 14:27         ` Carsten Dominik
2010-12-06  8:33       ` Carsten Dominik
2010-12-06 14:10       ` Bernt Hansen
2010-12-06 14:48       ` Nick Dokos
2010-12-06 16:48         ` Nathan Neff
2010-12-06 17:53         ` Carsten Dominik
     [not found]           ` <9588.1291658230@gamaville.americas.hpqcorp.net>
2010-12-06 18:08             ` Carsten Dominik
2010-12-07  3:14           ` Štěpán Němec
2010-12-07 19:33         ` Nick Dokos
2010-12-06 21:35       ` Alan Davis
     [not found]     ` <lngndvs@gmail.com>
2010-08-30  3:31       ` LaTeX export: Skip headline lines? "Paragraph" sectioning? Alan E. Davis
2010-08-30  4:06         ` Nick Dokos
2010-08-30  5:14           ` Scot Becker [this message]
2010-08-30  5:46             ` Nick Dokos
2010-08-30  6:54               ` Thomas S. Dye
2010-08-30 14:22                 ` Scot Becker
2010-08-30 16:20                   ` Thomas S. Dye
2010-08-30 22:05                     ` Scot Becker
2010-08-31  0:04                       ` Alan E. Davis
2010-08-30 16:40                   ` Alan E. Davis
2010-08-30 17:04                     ` Nick Dokos
2010-08-31  1:09             ` Alan E. Davis
2010-08-31  1:43               ` Alan E. Davis
2010-08-31  1:59                 ` Thomas S. Dye
2010-08-31  2:01                 ` Nick Dokos
2012-03-15 17:24       ` Mail composed using emacs --- saving a copy in an org file Alan E. Davis
2012-03-15 17:34         ` Jos'h Fuller
2012-03-15 17:48           ` Peter Salazar
2012-03-15 17:55         ` brian powell
2012-03-15 18:05           ` brian powell
2012-03-15 19:19         ` Nick Dokos
2012-03-15 19:48           ` brian powell
2012-03-16  9:32         ` Karl Voit
2012-03-16 13:46           ` brian powell
2012-03-16 16:07             ` Memacs and Gnowsis (was: Mail composed using emacs --- saving a copy in an org file.) Karl Voit
2010-12-05 21:44 ` Questions about org-capture templates and usage Charles Cave

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=AANLkTik26x8sOE3ZnZ8EMuKZSbrmqbDapdJ1B9KY-+Mb@mail.gmail.com \
    --to=scot.becker@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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).