emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Wed, 28 Dec 2022 20:34:27 +0100	[thread overview]
Message-ID: <Y6yaQx6PtHceOHJB@tuxteam.de> (raw)
In-Reply-To: <874jtfa0jd.fsf@tec.tecosaur.net>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Thu, Dec 29, 2022 at 01:37:32AM +0800, Timothy wrote:
> Hi all,
> 
> 2¢ from me: I have yet to see an example which seems like it actually needs the
> ability to go “up” a level. Sometimes I need to rethink my initial impulses, but
> often it forces me to use a better structure.
> 
> Considering the example used in the thread, I would think it lends itself to
> something like this:

Thanks. I /think/ that's not the point: "classical" text documents
seem to do fine without (let me call it) XML-style nesting (aka
"going back", as witnessed by TeX/LaTeX, which after all, come from
"classical" (scientific) text. We had this in the discussion.

There seem to be a few folks around here which are uncomfortable
with this limitation. My intent is rather to understand where this
discomfort comes from and what we can do about it.

I must admit that I was surprised about that limitation at first,
but seeing how papers and books and TeX and LaTeX do helped to
dispel that irritation of mine. That isn't necessarily the case for
everyone, though.

Just once I had (or thought I had) to have this and I shared here
my "hack", which worked perfectly well (after "enhancing" the one
exporter). But I think I was misusing a document description language
as a data description language (people do such things, disgusting,
I know ;-)

Thanks & cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-12-28 19:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 13:08 section continuation (was: Is the cascading logic of outlines a feature, or a design bug?) abq
2022-12-27 13:57 ` tomas
2022-12-28  2:22   ` Samuel Wales
2022-12-27 14:15 ` section continuation abq
2022-12-27 15:36   ` tomas
2022-12-27 20:22   ` abq
2022-12-28  5:17     ` Ihor Radchenko
2022-12-28  8:58       ` tomas
2022-12-29  6:01         ` Tim Cross
2022-12-29  8:57           ` tomas
2022-12-29  9:21             ` Heinz Tuechler
2022-12-29 10:09               ` Jean Louis
2022-12-29 10:42                 ` Ihor Radchenko
2022-12-29 14:00                   ` Jean Louis
2022-12-31 12:16                     ` Ihor Radchenko
2022-12-31 12:26                       ` tomas
2023-01-01 21:29                         ` Tom Gillespie
2022-12-29 10:28               ` tomas
2022-12-31 12:03                 ` Greg Minshall
2022-12-29 10:06             ` Jean Louis
2022-12-29 12:47     ` Max Nikulin
2022-12-28 17:37   ` Timothy
2022-12-28 19:34     ` tomas [this message]
2022-12-29 10:21       ` Ihor Radchenko
2022-12-29 10:30         ` tomas
2023-01-01 21:19           ` Marcin Borkowski
2022-12-28 20:01     ` Heinz Tuechler

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=Y6yaQx6PtHceOHJB@tuxteam.de \
    --to=tomas@tuxteam.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).