emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Feature Proposal: Titled Paragraphs
Date: Wed, 23 Oct 2019 16:55:23 +0200	[thread overview]
Message-ID: <87ftjjtstg.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 87h83zy28j.fsf@gmail.com

Hi,

What would be an actual example of a "paragraph that is not related to
Section I, but doesn't deserve a section title"?

Cheers,

Loris

Dominik Schrempf <dominik.schrempf@gmail.com> writes:

> Hello!
>
> I agree with this proposal. At some point I already asked if the following
> structure is possible:
>
> #+begin_example
> * Title
> ** Section I
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor
> tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis
> eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis
> parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor.
> Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum.
> Nam vestibulum accumsan nisl.
>
> Another paragraph that is not related to Section I, but doesn't deserve a
> section title. Another paragraph that is not related to Section I, but doesn't
> deserve a section title. Another paragraph that is not related to Section I, but
> doesn't deserve a section title. Another paragraph that is not related to
> Section I, but doesn't deserve a section title.
> #+end_example
>
> With titled paragraphs, this document structure could be achieved.
>
> All the best,
> Dominik
>
> Christoph Michelbach <michelbach94@gmail.com> writes:
>
>> On 2019-10-23 15:24, Fraga, Eric wrote:
>>> Why not use a further headline if you are exporting to LaTeX?  In the
>>> default configuration, the 4th level heading corresponds to \paragraph
>>> in LaTeX.
>>>
>>
>> 1. Because headlines and paragraphs are different things. One is used for
>> hierarchical structuring and description, the other only for description.
>> 2. Because that'd mean skipping hierarchical levels when using paragraphs on a
>> high level.
>> 3. Because headlines are collapsed by default. I realize the default can be
>> changed but if you like hierarchical levels to be collapsed, you still have to
>> expand paragraphs far up individually or expand all the hierarchical levels
>> below by dobule-tabbing.
>
>
>
-- 
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin         Email loris.bennett@fu-berlin.de

  reply	other threads:[~2019-10-23 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 13:13 Feature Proposal: Titled Paragraphs Christoph Michelbach
2019-10-23 13:24 ` Fraga, Eric
2019-10-23 13:51   ` Christoph Michelbach
2019-10-23 14:18     ` Dominik Schrempf
2019-10-23 14:55       ` Loris Bennett [this message]
2019-10-24  7:50       ` Julius Müller
2019-10-23 14:20     ` Fraga, Eric
2019-10-23 16:44 ` Nicolas Goaziou
2019-10-24  5:20 ` Fraga, Eric

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=87ftjjtstg.fsf@hornfels.zedat.fu-berlin.de \
    --to=loris.bennett@fu-berlin.de \
    --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).