Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

Paul Stansell writes: > Here are some diagnostic messages I just received when opening a file > called scratch.org: > ... Thanks! > org-element-cache diagnostics(scratch.org): Recovering persistent cached > element ... It is not the full log, right? -- Ihor Radchenko // yantar92, Org mode

Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

Paul Stansell writes: >> >> It's everything that was printed in the Warnings buffer. >> > > Actually, maybe it wasn't everything as I didn't scroll up in the buffer! > It just happened again: > > Warning (org-element): org-element--cache: Warning(scratch.org): Org > parser error in scratch.org::

Re: Generating the filename from name and file-ext for blocks with side-effects

Ihor Radchenko writes: > [...] and :file-ext is not given? But how will you know the desired > extension? Oh, I missed that. My local hack assumes `.svg', but that is not enough for the general use case. Perhaps, we could save as `$BASENAME.out', detect the image format, and then rename to `$

Re: Generating the filename from name and file-ext for blocks with side-effects

Rudolf Adamkovič writes: >> [...] and :file-ext is not given? But how will you know the desired >> extension? > > Oh, I missed that. My local hack assumes `.svg', but that is not enough > for the general use case. > > Perhaps, we could save as `$BASENAME.out', detect the image format, and > the

How to enter | in the Org mode table without expanding cell?

I just noticed that it is almost impossible to enter | into the Org cell without expanding it as new call by pressing TAB. | Key | Value | |-+---| | key | "123|value" | it becomes this: | Key | Value || |-+---+| | key | "123 | value" | | | || B

Re: Some hacks on top of org-publish

Nikolaos Chatzikonstantinou writes: >> > Finally a highlight of the hacks I had to pull off: apparently >> > #+INCLUDE: will strip away inline backend information such as >> > @@html:@@. I figured out that if I write something like >> > @@html@@a:@@:@@, only the inner @@a:@@ is recognized and str

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Pedro Andres Aranda Gutierrez writes: > A quick fix (on main) attached. With this ALT_TITLE is ignored in the > document with #+OPTIONS: num:nil and if #+OPTIONS: num:t and :PROPERTIES: > :UNNUMBERED: t Thanks! I am slightly concerned about generality of dropping ALT_TITLE from unnumbered sectio

Re: [PATCH] ob-calc: Format vector and matrix results as Org table

Visuwesh writes: > Thanks, these should be fixed in the attached patch. > > From 8ab27ec0c0732648d9c684decf8eda0e5e0ef1b5 Mon Sep 17 00:00:00 2001 > From: Visuwesh > Date: Thu, 26 Dec 2024 18:36:24 +0530 > Subject: [PATCH] ob-calc: Format vector and matrix results as Org tables Applied, onto ma

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Hi On Fri, 27 Dec 2024 at 18:42, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > A quick fix (on main) attached. With this ALT_TITLE is ignored in the > > document with #+OPTIONS: num:nil and if #+OPTIONS: num:t and :PROPERTIES: > > :UNNUMBERED: t > > Thanks! > I am slightly

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Pedro Andres Aranda Gutierrez writes: >> I am slightly concerned about generality of dropping ALT_TITLE from >> unnumbered sectioning command. > ... > I do think we can. Unnumbered sectioning commands never appear in the ToC... > Unless you use additional magic like, ... Good. I am not concerned

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

@Rudolf, WDYT? How can I phrase it? It looks like you were trying something that LaTeX doesn't allow... Best, /PA On Fri, 27 Dec 2024 at 19:00, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > >> I am slightly concerned about generality of dropping ALT_TITLE from > >> unnumber

Re: [PATCH v2] org-protocol: Add void() to bookmarklets

Max Nikulin writes: >> Then, no need to change your variant. > > I changed the patch to trailing ";void(0)" and I have found a typo in > first variant of the patch. Applied, onto bugfix. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9729c60eb4 I also added an entry to ORG-NEW

Re: The less ambiguous math delimiters in tables

Ihor Radchenko writes: > In a theoretical case if we agree to what you are suggesting, it should > not be just for tables. There are similar cases with other markup, like > > *foo =* *= bar* Agreed! We could introduce a kind of escaping that means "this MUST be interpreted as markup" and/or "t

Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

> > It's everything that was printed in the Warnings buffer. > Actually, maybe it wasn't everything as I didn't scroll up in the buffer! It just happened again: Warning (org-element): org-element--cache: Warning(scratch.org): Org parser error in scratch.org::8756. Resetting. The error was: (err

Re: [BUG] org-link-preview-file emits image not supported in daemon [9.8-pre (release_9.7.10-127-g07dd3b @ /home/bidar/.local/etc/emacs/lib/org/lisp/)]

Karthik Chikmagalur writes: >> 1. As a minimum, we can remove that message and do nothing on >>non-graphical displays. It will be consistent with earlier behavior. > > I will remove that message from org-link-preview-file. +1 >> 2. Maybe we can move the check about graphics to the specific

Re: Unexpected error using org-gnus-follow-link

Visuwesh writes: > From ee57860915308dc9bf30172cfd94f8985b536361 Mon Sep 17 00:00:00 2001 > From: Visuwesh > Date: Mon, 23 Dec 2024 11:59:16 +0530 > Subject: [PATCH] Error if org-link-frame-setup is ill-defined Thanks! Applied, onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/com

[TASK] Rewriting org-pcomplete into capf backend (was: Completions Registry)

Karthik Chikmagalur writes: > As discussed in the last Org meetup, I would like to write a CAPF that > provides completions and annotations when typing in keywords provided by > (loaded) Org libraries. The annotations providing inline documentation > require this information to be available in t

Re: The less ambiguous math delimiters in tables

On Wed, Dec 25 2024, Rudolf Adamkovič wrote: > Ihor Radchenko writes: > >> It is a syntax limitation. >> Org parser is outer-inner - the table row is parsed first. >> So, | are unconditionally used as table delimiters, *before* verbatim >> LaTeX markup is recognized. > > How is that not a parser

Re: The less ambiguous math delimiters in tables

Rudolf Adamkovič writes: >> In a theoretical case if we agree to what you are suggesting, it should >> not be just for tables. There are similar cases with other markup, like >> >> *foo =* *= bar* > > Agreed! We could introduce a kind of escaping that means "this MUST be > interpreted as markup

Re: [PATCH v2] org-protocol: Add void() to bookmarklets

On 24/12/2024 21:23, Ihor Radchenko wrote: Max Nikulin writes: javascript:location.href='org-protocol://store-link?'+new URLSearchParams({url:location.href, title:document.title}); void(0); If you think that ";void(0)" variant is less prone to errors then I may update my patch. I have no ide

Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

> > It is not the full log, right? > It's everything that was printed in the Warnings buffer.

Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

> > This looks more reasonable. > Is this with my patch applied? > Yes, the patch is applied.

Re: [BUG] "Invalid search bound (wrong side of point)" [9.8-pre (release_9.7.16-169-ge87ecf @ ~/.emacs.d/org-mode-git/lisp/)]

Hi Ihor, Here are some diagnostic messages I just received when opening a file called scratch.org: org-element-cache diagnostics(scratch.org): Recovering persistent cached element: "(keyword (:standard-properties [1 1 nil nil 22 0 nil top-comment element t nil nil nil nil # nil nil (section (:s

Re: Form feed characters break odt export

Ihor Radchenko writes: [...] > +(defconst org-odt-forbidden-char-re > + (rx (not (in ?\N{U+9} ?\N{U+A} ?\N{U+D} > + (?\N{U+20} . ?\N{U+D7FF}) > + (?\N{U+E000} . ?\N{U+FFFD}) > + (?\N{U+1} . ?\N{U+10} Indentation mismatch ^ > + "Regexp matching

Re: How to enter | in the Org mode table without expanding cell?

Jean Louis writes: > I just noticed that it is almost impossible to enter | into the Org > cell without expanding it as new call by pressing TAB. > ... > Is there way? \vert Also, see https://list.orgmode.org/878qs1vye4@t14.reltub.ca/t/#u -- Ihor Radchenko // yantar92, Org mode maintainer,

Re: [BUG] yank-media doesn't work

Visuwesh writes: > In any case, nothing much can be done from Org's side. This is clearly > an Emacs bug (or a mismatch of user environment and toolkit). So... Canceled. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org develo

Re: active region persistence

Samuel Wales writes: > my q is actually why would a user want the region to remain active? > e.g. select region and then m-w deactivates it. I just pushed a new option `org-edit-keep-region' that controls whether region is preserved during structure editing. The new option is on main branch. h

Re: [PATCH] Turn org-mouse features into minor-modes

Visuwesh writes: > [ Resending it as it seems like it never reached the mailing list. ] > > To make loading org-mouse less annoying for all, I was thinking of > introducing minor-modes like in the attached patch. If this approach is > acceptable, I will get to calling out the change in NEWS and

Re: [PATCH] Turn org-mouse features into minor-modes

[வெள்ளி டிசம்பர் 27, 2024] Ihor Radchenko wrote: > Visuwesh writes: > >> [ Resending it as it seems like it never reached the mailing list. ] >> >> To make loading org-mouse less annoying for all, I was thinking of >> introducing minor-modes like in the attached patch. If this approach is >> ac

Re: [PATCH] Turn org-mouse features into minor-modes

Visuwesh writes: >> Although they should probably be globalized to keep things closer to the >> existing behavior. > > That would make it hard to toggle the feature on/off on a per-buffer > basis, which was my intention behind using a minor mode. I don't have > strong opinions here so if you thi

Re: [BUG] yank-media doesn't work

[வியாழன் டிசம்பர் 26, 2024] the_wurfkreuz wrote: > It gives this: > > [TIMESTAMP TARGETS SAVE_TARGETS MULTIPLE STRING UTF8_STRING TEXT > chromium/x-source-url text/html text/plain text/plain\;charset=utf-8] No wonder nothing happened. There's no image/* element here so we cannot do anything her

Re: Form feed characters break odt export

Joseph Turner writes: > Thanks, Ihor! Tested working on my machine. > > Here's another potential solution to consider, which adds a defcustom to > let the user decide how to handle forbidden characters: > > https://github.com/kjambunathan/org-mode-ox-odt/commit/07fde1e9b7cdda3e3ef8136f5b1d478499

Re: Month-week and quarter-week datetrees (RFC and package announcement)

Ihor Radchenko writes: > Jack Kamm writes: > >>> The API of `org-datetree--find-create' is generally very limiting. >>> It would be nice to come up with something less limiting. >> >> Thanks for the feedback -- I'll start working on something along these >> lines. Though this might take me a li

Re: [PATCH] Add next-error support to org-lint report buffer

Thanks for the patch! Unfortunately, the patch seems to be malformed (something inserted line breaks in inappropriate places). May you please re-send the patch as an attachment, to make sure that your MUA does not break things? Apologies for the malformed patch. Here it is as an attachme

Re: [BUG] org-link-preview-file emits image not supported in daemon [9.8-pre (release_9.7.10-127-g07dd3b @ /home/bidar/.local/etc/emacs/lib/org/lisp/)]

>>> 1. As a minimum, we can remove that message and do nothing on >>>non-graphical displays. It will be consistent with earlier behavior. >> >> I will remove that message from org-link-preview-file. > > +1 Patch attached. Karthik >From 621396f4b5c46f109aaec5afcb0a983153d8a60a Mon Sep 17 00:00

Re: [TASK] Rewriting org-pcomplete into capf backend (was: Completions Registry)

> Yup. > We may simply define a new special variable like, > > (defvar org-babel-header-arg-docs:sqlite > '((db "" > (header "") > ...)) > "Description of sqlite-specific header arguments.") > > and global > > (defvar org-babel-header-args-docs ...) I'll work with this assumpti