emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: nicholas.dokos@hp.com
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export: Skip headline lines? "Paragraph" sectioning?
Date: Sun, 29 Aug 2010 20:54:24 -1000	[thread overview]
Message-ID: <86EDC831-F315-431E-B4F7-105C0632BDF3@tsdye.com> (raw)
In-Reply-To: <20131.1283147209@gamaville.dokosmarshall.org>


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

On Aug 29, 2010, at 7:46 PM, Nick Dokos wrote:

> Scot Becker <scot.becker@gmail.com> wrote:
>
>> 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.
>>
>
> OK, thanks for the clarification: that was one of the interpretations
> that did not make much sense to me, but I was looking at it from a  
> much
> more rigid point of view, where the headlines are what give  
> structure to
> the document, so you want to preserve them at all costs; I wasn't
> thinking about different meanings that they might have for different
> people.
>
> However, it still sounds like an ill-defined problem to me: in
> particular, your manual algorithm would wreak havoc on an outline with
> headlines at multiple levels. What is the "real" algorithm supposed to
> do with something like this:
>
> ,----
> | * foo
> | text1
> | ** foo1
> | text2
> | * bar                  :omit-this-header:
> | text3
> | **bar2                 :omit-this-header:
> | text4
> | ***bar3
> | text5
> `----
>
> Or are we supposed to imagine headings at a single level only?
>
> I suspect that one would be better off with two (or more) outlines:  
> one for
> the writer, one for the reader (perhaps one for each class of  
> readers), with
> some way to pick text from one outline and plug it into the other(s).
>
> Nick

Aloha Alan et al.,

This is what I use LaTeX blocks in Babel for.  The outline stuff that  
helps me write is separate from the stuff I actually write.  I've been  
doing this for a while now and have been amazed at how much of what I  
write gets left behind, including headlines.

All the best,
Tom

[-- Attachment #1.2: Type: text/html, Size: 2997 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  6:54 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
2010-08-30  5:46             ` Nick Dokos
2010-08-30  6:54               ` Thomas S. Dye [this message]
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=86EDC831-F315-431E-B4F7-105C0632BDF3@tsdye.com \
    --to=tsd@tsdye.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).