emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Julius Müller" <Julius.Muller@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Feature Proposal: Titled Paragraphs
Date: Thu, 24 Oct 2019 09:50:17 +0200	[thread overview]
Message-ID: <8df91ed0-912f-70f8-a4b3-b80a12bd53de@gmx.net> (raw)
In-Reply-To: <87h83zy28j.fsf@gmail.com>

Am 23.10.19 um 16:18 schrieb Dominik Schrempf:
> 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.

Only if you are very restrictive about it, as you hit a fundamental
problem of org markup here, a problem it shares with (La)TeX, HTML, all
printed books I'm aware of, and a lot of other formats. Org and (La)TeX
only markup the start of a section, not its end. Thus it would be
difficult to tell your construct apart from other kind of structures.

Contrary to your view, in the (La)TeX-world \paragraph is usually seen
as just another hierarchical level of document structuring. It is a
heading (with a weird default of not standing on a line of its own), and
it does NOT solely belong to the one paragraph it starts. In fact, with
your view, (La)TeX's \subparagraph macro would not make any sense at
all. That means, adding \paragraph in your sense will break document
structure the moment you also have nesting deeper than 3 (or 4 for
book-like formats).

Julius

  parent reply	other threads:[~2019-10-24  7:50 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
2019-10-24  7:50       ` Julius Müller [this message]
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=8df91ed0-912f-70f8-a4b3-b80a12bd53de@gmx.net \
    --to=julius.muller@gmx.net \
    --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).