From: yaxp <yaxp@cock.li>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-beamer: Insert \framebreak between blocks
Date: Wed, 25 Oct 2023 22:02:54 +0530 [thread overview]
Message-ID: <420f6835-0697-4882-b9ec-0a7977803ae6@cock.li> (raw)
In-Reply-To: <87bkcmy8eu.fsf@ucl.ac.uk>
On 25/10/23 21:57, Fraga, Eric wrote:
> On Wednesday, 25 Oct 2023 at 21:32, yaxp wrote:
>> However, I would prefer to have a better solution than this because this
>> "breaks" the flow of the file.
> It does break the flow but only because *you* are imposing the break. I
> don't know of any other (more elegant) way to achieve what you want.
> Maybe others do.
>
>> I'd like to publish the .org file too, and I hope to make it just as
>> convenient to read as the produced PDF.
> It's difficult to have the marked text (which has both semantic and
> specific typographical directives) be as "clean" as the resulting PDF.
> org is good at minimising noise in the file but you cannot remove it
> completely. Sometimes macros can help but probably not in this case
> without being fragile.
>
>> Also, is there any reasoning behind why the current behavior is the way
>> it is?
> Yes, very simply: there is no way to indicate the end of a "block". The
> start is defined by the heading but only ends when another heading at
> the same or higher level is started. This is related to a longstanding
> desire by many to have the ability to explicitly end a subheading. The
> grammar does not allow for this and there have been many discussions on
> the mailing list over the years about this. The situtation is unlikely
> to change.
>
> eric
Makes sense. Thank you :)
--
(yaxp me) => t
next prev parent reply other threads:[~2023-10-25 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 18:54 org-beamer: Insert \framebreak between blocks yaxp
2023-10-25 9:00 ` Fraga, Eric
2023-10-25 16:02 ` yaxp
2023-10-25 16:27 ` Fraga, Eric
2023-10-25 16:32 ` yaxp [this message]
2023-10-25 16:44 ` yaxp
2023-10-25 16:13 ` yaxp
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=420f6835-0697-4882-b9ec-0a7977803ae6@cock.li \
--to=yaxp@cock.li \
--cc=e.fraga@ucl.ac.uk \
--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).