Re: [PATCH] org-babel-demarcate-block: split using element API

gerard.vermeu...@posteo.net writes: >> Have you tried the latest main? > > Yes (just tried again), the minimal function still triggers the > "infinite" list of warnings > "Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org > buffer # (python-mode)" > It is coming from the la

[DISCUSSION] Face priority in Org fontification (was: [BUG] org dates, radio links, and special keywords override heading backgrounds [9.7 (9.7-??-902dacb @ /home/st/.config/emacs/.local/straight/buil

StrawberryTea writes: > Hello. Currently, if you have a heading background, and you have a date, > radio link, or special keyword, the background is overridden. I have > attached a patch that fixes this issue by using the `prepend' property > instead of the `t' property. Here is also a minimal ex

Re: Provide sane default for the @direntry

Stefan Monnier writes: >> May you please supply a ChangeLog entry? I am not sure if I understand >> the purpose of each change in the diff. >> >> Also, it looks like you introduce some DWIM behaviour for auto-generating >> @direntry contents. Such new behaviour ought to be documented in the >> ma

Re: [BUG] Re: The orgframe construct in the Beamer exporter as a default needs a rethink

Pedro Andres Aranda Gutierrez writes: > Org-lint will signal that… IHvHO that’s more than enough May you elaborate? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support

Re: [BUG] we should obsolete org-fontify-whole-heading-line [9.7 (9.7-??-b127d72 @ /home/st/.config/emacs/.local/straight/build-30.0.50/org/)]

StrawberryTea writes: > We should make org-fontify-whole-heading-line default to t and obsolete > it. That variable was added before the introduction of the :extend > keyword for text properties. Now that we have :extend, we can make the > whole heading line face extend to the end of the window w

Re: [PATCH] org-babel-demarcate-block: split using element API

On 04.03.2024 11:12, Ihor Radchenko wrote: What about after https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5f5db3d35 ? This fixes the bug. I resubmit my patch (attached) without any caveats in the commit message. Regards -- Gerard 0001-org-babel-demarcate-block-split-u

Re: [PATCH] org-babel-demarcate-block: split using element API

gerard.vermeu...@posteo.net writes: > I resubmit my patch (attached) without any caveats in the commit > message. Thanks! Applied, onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c2ea553be -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode

Re: [BUG] (wrong-type-argument integer-or-marker-p nil) [9.6.15 (release_9.6.15 @ /home/phi/Source/emacs/lisp/org/)]

Ihor Radchenko writes: > Philip Kaludercic writes: > >> This just popped up in my *Warnings* buffer: >> >> --8<---cut here---start->8--- >> ⛔ Warning (org-element-cache): org-element--cache: Org parser error >> in .links.org::29638. Resetting. >> The error wa

Re: Provide sane default for the @direntry

>> * doc/misc/org.org (Texinfo specific export settings): Adjust accordingly. > It would be nice to provide etc/ORG-NEWS entry as well. Yes, thanks. >>#+cindex: @samp{TEXINFO_DIR_TITLE}, keyword >>The directory title of the document. >> + This is the short name under which the ~m~ comman

naming: Re: Experimental public branch for inline special blocks

On 02/03/2024 03:34, Juan Manuel Macías wrote: Finally, I have made public on GitLab my experimental branch for the new (possible) inline-special-block element: I find the feature name confusing, however I am unsure if others share my opinion. In Org syntax, "elements" are paragraphs and la

Re: naming: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > Does anybody have an idea of a better name for a feature? Maybe > something like inline custom objects, snippets. "Objects" are used to > describe syntax, but not used in the manual though. Custom inline markup. -- Ihor Radchenko // yantar92, Org mode contributor, Learn

Re: naming: Re: Experimental public branch for inline special blocks

Ihor Radchenko writes: > Max Nikulin writes: > >> Does anybody have an idea of a better name for a feature? Maybe >> something like inline custom objects, snippets. "Objects" are used to >> describe syntax, but not used in the manual though. > > Custom inline markup. Custom span? I chose "inl

Re: naming: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > In Org syntax, "elements" are paragraphs and larger parts, while parts > within paragraphs are named objects. I admit that for org-element > everything is element. In my initial message I used 'element' loosely. Note that inline-special-block is included in org-element-all-o

Re: naming: Re: Experimental public branch for inline special blocks

If language is not correct, then what is said is not what is meant; if what is said is not what is meant, then what must be done remains undone; if this remains undone, morals and art will deteriorate; if justice goes astray, the people will stand about in helpless confusion. Hence there must be no

Re: naming: Re: Experimental public branch for inline special blocks

[i did not aim that at any particular person!] On 3/4/24, Samuel Wales wrote: > If language is not correct, then what is said is > not what is meant; if what is said is not what is meant, > then what must be done remains undone; if this remains > undone, morals and art will deteriorate; if justic

[tip] Export to PDF with latexmk 'continuous preview' option

A little-known (and sometimes very useful) latexmk option is the -pvc option. According to the latexmk manual: [...] The second previewing option is the powerful -pvc option (mnemonic: "preview continuously"). In this case, latexmk runs continuously, regularly monitoring all the

[BUG] unfolding headlines with :extend face keyword & background broke after 2da622cad [9.7 (9.7-??-8ac99c33f @ /home/st/.config/emacs/.local/straight/build-30.0.50/org/)]

Hi, using the following test case with Emacs -Q: (let ((default-directory (file-name-directory load-file-name))) (when (file-exists-p (expand-file-name "default.el" default-directory)) (load-file (expand-file-name "default.el" default-directory (straight-use-package 'org) (require 'o