From: Marcin Borkowski <mbork@mbork.pl>
To: tomas@tuxteam.de
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Sun, 01 Jan 2023 22:19:37 +0100 [thread overview]
Message-ID: <87fscu9cly.fsf@mbork.pl> (raw)
In-Reply-To: <Y61sPAJvFmSpywsS@tuxteam.de>
On 2022-12-29, at 11:30, tomas@tuxteam.de wrote:
> On Thu, Dec 29, 2022 at 10:21:52AM +0000, Ihor Radchenko wrote:
>> <tomas@tuxteam.de> writes:
>>
>> > 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.
>>
>> >From my experience, there is a temptation to have a dedicated "closing"
>> text at the end of subtree. In particular, literal configs are often
>> structured as
>>
>> * Heading 1
>>
>> #+begin_src emacs-lisp
>> (when condition
>> #+end_src
>>
>> ** Sub-heading 1
>> ...
>> ** Sub-heading N
>>
>> ** extra
>>
>> #+begin_src emacs-lisp
>> ) ; closing ")"
>> #+end_src
>>
>> * Heading 2
>
> Must be our deformed "computer folks" brains. Too many years of
> Djkstra's "goto considered harmful" or something ;-)
This. Also, I guess "normal" people are perfectly fine with attaching
the "closing" to the last subsection or putting it into a dedicated
subsection.
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-01-01 21:20 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
2022-12-29 10:21 ` Ihor Radchenko
2022-12-29 10:30 ` tomas
2023-01-01 21:19 ` Marcin Borkowski [this message]
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=87fscu9cly.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=tomas@tuxteam.de \
--cc=yantar92@posteo.net \
/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).