From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Wed, 28 Dec 2022 09:58:36 +0100 [thread overview]
Message-ID: <Y6wFPMjM/iQUSQUw@tuxteam.de> (raw)
In-Reply-To: <87wn6cksy8.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
On Wed, Dec 28, 2022 at 05:17:35AM +0000, Ihor Radchenko wrote:
> abq@bitrot.link writes:
>
> > And can anybody think of any costs besides the ones already mentioned?
> > Any adverse interaction with other features?
>
> Export. If those special "continuations" are not considered sections
> structurally, it is unclear how to represent them when exporting to
> LaTeX/HTML/etc. The most painful is situation with third-party exporters
> that may need to be adapted.
That's why I was suggesting a "low profile" approach. "Official" Org
shouldn't have to care about it (after all, for those interested, it
isn't that difficult to make a derived exporter). Perhaps that "feature"
ends up as something needing special exporters (after all, for
(La)TeX, Markdown, (possibly?) OpenDocument, the exporters will have
to do "funny stuff", because the target document model doesn't know
what we are talking about.
For this idea to bear any weight, I think first is having interested
users agreeing on some conventions. The tools will come, I wouldn't
start with those (perhaps only as proof of concept, to test and
validate ideas).
It'd be too early now to commit Org to that, potentially ossifying
stuff of which we don't know yet whether it is a good idea at all.
As far as I am concerned, I don't think the feature is important
enough to complexify Org, but (a) I see that there are people who
really want it (and offer myself as sparring partner to bounce ideas
off) and (b) Org is chock full of features I'd rather not have,
but others need badly. Software is like that :-)
Thanks & cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-28 8:59 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 [this message]
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
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=Y6wFPMjM/iQUSQUw@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).