emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus.pank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections ?
Date: Wed, 30 Mar 2011 12:05:56 +0200	[thread overview]
Message-ID: <imuv8e$m8h$1@dough.gmane.org> (raw)
In-Reply-To: 87hbal7o60.fsf@fastmail.fm


> --8<---------------cut here---------------start------------->8---
>  * Main headline
>    Some thoughts expressed here
>
>  ** Subheading 1
>     More thoughts expressed here
>  ** Subheading 2
>     More thoughts expressed here
>  ** Main headline (cont.)
>
>   I would like to have this text part of 'Main headline', not of
>   'Subheading 2'
> --8<---------------cut here---------------end--------------->8---

I don't understand the logic in this. 

In terms of final layout, do you want to have subheading appear as a
"box"? Like in some (introductory) textbooks? If so, you could program a
certain ** to be export as a certain type of object. You might even be
able to use tags to determine how output should be formatted, like in
Org-latex-beamer mode. This might require some hacking. 


I do however, strongly support the idea of terminating headings, but for
other reasons. 

My problem is ending * COMMENT headings. 

This sketch the issue (in terms of LaTeX export):
#+begin_src emacs-org
* COMMENT This is were I put all my export settings, various notes and such

  it could be placed as the very last headline, but that is somewhat
  annoying an illogical to me. 

** Export 
#+TITLE: Test
#+AUTHOR: me 
[A bunch of paper-specific #+latex_header:] 

** An outline of the task at hand 
[...]

And HERE I want to put text before the first subsection. That is beneath
Title but before first section. 
#+end_src

In terms of LaTeX I need something like: 

#+begin_src latex
\begin{document}
\maketitle 
This is where I want some initial text
\section{first section}
#+end_src

Of course, I could start explicitly with a \section{intro} (i.e. *
Intro) right after \maketitle/\begin{document}, but for short papers I
find this is redundant.

Is my style the problem or should there be a way to terminate section, maybe
with an artificial new heading (similar to the :B_ignoreheading: tag)? 

Cheers,
Rasmus

  reply	other threads:[~2011-03-30 10:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 15:02 Continuation of main section text after subsections ? Marcel van der Boom
2011-03-27 15:37 ` Jambunathan K
2011-03-27 15:52   ` Cian
2011-03-27 16:11     ` Marcel van der Boom
2011-03-27 16:34       ` William Gardella
2011-03-27 16:45       ` Nick Dokos
2011-03-27 17:00         ` Thomas S. Dye
2011-03-27 16:49       ` Filippo A. Salustri
2011-03-27 17:08         ` Nicolas
2011-03-27 17:10           ` Filippo A. Salustri
2011-03-27 17:02       ` William Gardella
2011-03-27 17:08         ` Filippo A. Salustri
2011-03-27 17:18           ` William Gardella
2011-03-27 17:20             ` Filippo A. Salustri
2011-03-27 20:21             ` Achim Gratz
2011-03-27 21:26               ` William Gardella
2011-03-29 18:59             ` Matt Lundin
2011-03-30  6:26               ` Aankhen
2011-03-28 14:54           ` Marcel van der Boom
2011-03-27 18:24         ` Aankhen
2011-03-27 19:29           ` Samuel Wales
2011-03-27 19:48       ` Cian
2011-03-28  0:00 ` FAQ? (was: Continuation of main section text after subsections ?) Memnon Anon
2011-03-28  8:36   ` Marcel van der Boom
2011-07-02 12:18     ` FAQ? Bastien
2011-03-29 18:54 ` Continuation of main section text after subsections ? Matt Lundin
2011-03-30 10:05   ` Rasmus [this message]
2011-03-30 11:06     ` Filippo A. Salustri
2011-03-31  1:41     ` Matt Lundin
2011-03-31  3:25       ` Samuel Wales
2011-03-31  3:26         ` Samuel Wales
2011-03-31  3:31         ` Samuel Wales
2011-03-31 20:04         ` Matt Lundin
2011-03-31 22:14           ` Aankhen
2011-03-30 18:26 ` Mark Elston
  -- strict thread matches above, loose matches on Subject: below --
2011-03-27 17:01 Rustom Mody

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='imuv8e$m8h$1@dough.gmane.org' \
    --to=rasmus.pank@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).