org-beamer: Insert \framebreak between blocks

Adding  a framebreak between blocks does not work. ``` #+latex_class: beamer #+options: H:1 # [snip] * Example :B_frame: :PROPERTIES: :BEAMER_opt: allowframebreaks :BEAMER_env: frame :END: ** This should be on frame 1 - Some text #+LATEX: \framebreak ** This should be on frame 2 - Some

Re: Org-beamer: Have text overflows continue onto another frame

That does everything I needed. Thank you :D On 24/10/23 19:55, Fraga, Eric wrote: and there is some customization possible for continuation frames: https://tex.stackexchange.com/questions/295854/how-to-edit-behaviour-of-frame-titles-during-frame-break-in-beamer (and maybe more: still

[PATCH] ox-ascii.el: Consistently add brackets around links (was: Re: [RFC][PATCH] Allow to export to ascii custom link types as notes)

On 24/10/2023 17:40, Ihor Radchenko wrote: Max Nikulin writes: [Org mode] () man man (http://man.he.net/?topic=man=all) [...] Should be [man] () Side note: it should be either just "man(1)" or "man(8)" without any URL

Best practice for writing and debugging shell source blocks?

Hi, inspired by "Literate DevOps" (https://howardism.org/Technical/Emacs/literate-devops.html), I want to document some "stuff" in an Org file with the goal to be able to replay the steps done in the future so that I can either recreate the same "product" or variations there- of. My actual topic

Re: Org-beamer: Have text overflows continue onto another frame

and there is some customization possible for continuation frames: https://tex.stackexchange.com/questions/295854/how-to-edit-behaviour-of-frame-titles-during-frame-break-in-beamer (and maybe more: still searching) -- : Eric S Fraga, with org release_9.6.7-661-g34ee6f in Emacs 30.0.50

Re: Colons in :var header arguments

Thanks, and sorry for the slow reply! I was wondering if it would be more intuitive to try to resolve the reference in the same file before looking in other files. I think this would make little practical difference as I think files named sec, tab, eq and fig are rare (although I often use fig for

Re: Org-beamer: Have text overflows continue onto another frame

That works, thank you. The default titling scheme will have to suffice for now then methinks. On 24/10/23 18:47, Fraga, Eric wrote: On Tuesday, 24 Oct 2023 at 17:56, yaxp wrote: How do I have overflowing text continue on a new frame? Ideally, in a way that lets me also customize the title of

Re: Org-beamer: Have text overflows continue onto another frame

On Tuesday, 24 Oct 2023 at 17:56, yaxp wrote: > How do I have overflowing text continue on a new frame? Ideally, in a > way that lets me also customize the title of this new frame You can easily do the former by adding :BEAMER_opt: allowframebreaks to the PROPERTIES for any frame that needs to

Org-beamer: Have text overflows continue onto another frame

How do I have overflowing text continue on a new frame? Ideally, in a way that lets me also customize the title of this new frame Sample org file below. #+title: Beamer Test #+LANGUAGE: en #+options: H:1 toc:nil #+latex_class: beamer #+columns: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act)

Re: the opposite of the noexport tag

> Uwe Brauer writes: > I find this part confusing - we first talk about no "export" tags at all > and then immediately about using with "export" tags. I dropped it in the > attached patch. Maybe there is a better way to formulate the same? > In the attached patch, I incorporated your other

Re: [BUG] CI jobs do not appear to be running

Ihor Radchenko writes: > It does not look like there is any improvement. Yes, something is wrong with cron. I'll have a look this week-end, I don't have a stable connection right now. -- Bastien Guerry

Re: the opposite of the noexport tag

"Loris Bennett" writes: >> + List of tags that will *only* be selected for export. The default > > I find the emphasised 'only' confusing here, since it implies to me > there the tags might have some other function. I would find, in analogy > to the corresponding text regarding exclude tags,

Re: [RFC][PATCH] Allow to export to ascii custom link types as notes

Max Nikulin writes: > However "cond form will work without changes" is not clear for me. > `org-export-custom-protocol-maybe' is called twice and depending on > context the result should be either "[description]" inline or > "[description] path" for note, so the code around >

Re: the opposite of the noexport tag

Ihor Radchenko writes: > Uwe Brauer writes: > >>> Uwe Brauer writes: I recommend then to clarify this is in the manual: the expression in the manual is `("export")' >> >>> What about the attached patch? >> >> I added some lines, and run rediff and I hoper therefore the

Re: org-ditaa woes

Florin Boariu writes: > I can offer to try my luck with writing a patch for ob-ditaa.el, but > I'm not knowledgeable enough (or have enough time on my hands) to > actually keep maintaining it :-p Writing a patch is also welcome. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more

Re: No-description <> links

Max Nikulin writes: >> The main problem is how to properly design >> this - the current approach is that individual backends decide. And we >> have no control over third-party backends... > > If it were possible to customize fuzzy links through > `org-link-parameters' then Rudolf would be able

Re: org-ditaa woes

Hello, I hope, a couple of workarounds are still possible. 1. Get java command by adding bash -x (or /usr/bin/bash, or "/usr/bin/env bash") flatpak-spawn --host toolbox run bash -x /usr/bin/ditaa \ /tmp/foo.txt -o /tmp/foo.png - set `org-babel-ditaa-java-cmd' to something like

Re: [BUG] org-element--cache Cached element is incorrect (ox-hugo) [9.6.10 (release_9.6.10 @ /home/gk/.emacs.d/lib/org/lisp/)]

George Kettleborough writes: > I've been having a problem where some of my exports get truncated > randomly at the end. I haven't been able to figure out the exact > problem, but by bisecting org-mode I found the problem appears in > 072ddbc9 which sets `org-element--cache-self-verify' to t. By

Re: [BUG] code block side effects differences between "results: none" and "results: silent" [9.6.9 ( @ /home/jet/.config/emacs/elpa/org-9.6.9/)]

Jeff Trull writes: > In the following code block, a propertized (inverse video) before-string > overlay appears when "results: none" is used, but the property is absent > (the overlay text appears normal) when "results:silent" is used: > > # with ":results none" it works as expected - inverse

Re: the opposite of the noexport tag

Uwe Brauer writes: >> Uwe Brauer writes: >>> I recommend then to clarify this is in the manual: the expression in the >>> manual is >>> `("export")' > >> What about the attached patch? > > I added some lines, and run rediff and I hoper therefore the modified patch > is ok. > > > Feel free to

Re: [BUG] CI jobs do not appear to be running

Bastien Guerry writes: > Ihor Radchenko writes: > >> Still nothing, even though I did not address some recent >> failures, like "FAILED ob-octave/session-multiline". > > I've pushed a fix, it should be okay now. > > I've also updated the script which mirrors the main Org repository to > GitHub

Re: No-description <> links

On 23/10/2023 15:15, Ihor Radchenko wrote: I wonder, why not export [[link]] to <> as "link" by default, if no description is given, as is the case with URLs, Elisp, and the like? Yes, something like that. The main problem is how to properly design this - the current approach is that

Re: [RFC][PATCH] Allow to export to ascii custom link types as notes

On 23/10/2023 19:09, Ihor Radchenko wrote: Max Nikulin writes: Then, `org-ascii-make-link-with-note' may as well receive and modify INFO plist. This way, ((org-export-custom-protocol-maybe link desc 'ascii info)) cond form will work without changes as `org-ascii-make-link-with-note` will do all

Re: org-ditaa woes

On 23/10/2023 18:18, Florin Boariu wrote: sh-5.1$ flatpak-spawn --host toolbox run /usr/bin/ditaa /tmp/foo.txt -o /tmp/foo.png thanks I really _need_ to generically execute a command. I hope, a couple of workarounds are still possible. 1. Get java command by adding bash -x (or

Re: Feature request: export form feed as page break

Am Sonntag, dem 22. Oktober 2023 schrieb Jambunathan K: > I am the original author of ox-odt.el. > > The page break feature is available as part of > https://github.com/kjambunathan/org-mode-ox-odt I took a look at