Re: [BUG] Tags following a timestamp does not work.

Thanks a lot for the quick fix ! It works. On 2025/07/20 18:17, Ihor Radchenko wrote: >Miki Kawabe writes: > >> I'm wondering if it's allowed to use both timestamp and tag in the same >> headline in Org mode. >> Although I read the manual on Tags and Timestamps, I couldn't find any >> explanat

Re: Bug in org-element with jit-lock and visual lines, and folding

Samuel Wales writes: > i discovered another major bug by coincidence. is it related? > > * folded > lorem > * unfolded > point > > if i do an isearch backward, isearch will not notice lorem. it seems > to act as if isearch-invisible were nil. Sorry, I am unable to reproduce. Could you

Re: Bug in org-element with jit-lock and visual lines, and folding

Samuel Wales writes: > is commenting out that line intended to fix the bug or cause a bug? > it did not ause a bug. the bug is intermittent. It might fix the bug, if my blind guess on what the bug is about is right. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode

Re: org element bug filling

Samuel Wales writes: > i set teh variables and tried to repro and was not able to. Then, you can try adding those variable into init.el and then monitor *Redisplay-trace* buffer. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Or

Re: [BUG] Error about org-link-types when creating a link [9.7.31 (9.7.31-4e6d38 @ /home/dsmasterson/.emacs.d/elpa/org-9.7.31/)]

Ihor Radchenko writes: > Ihor Radchenko writes: > >> But there is no such variable in Org mode - `org-link-types'. There is a >> *function*. Bug in org-ac. > > Looks like there used to be such variable long time ago. > But it has been removed in > https://git.savannah.gnu.org/cgit/emacs/org-mode

Re: [FR] Org export: expanding links to included files (was: [BUG] Export backend cross-references are broken [9.7.30 (release_9.7.30 @ /home/user/org-mode-git/lisp/)])

Samuel Wales writes: > could the duplicate issue, at least, be fixed by adding the feature of > allowing id links? What do you mean by "duplicate issue"? -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at

Re: [FR] Org export: expanding links to included files (was: [BUG] Export backend cross-references are broken [9.7.30 (release_9.7.30 @ /home/user/org-mode-git/lisp/)])

could the duplicate issue, at least, be fixed by adding the feature of allowing id links? On Sun, Jul 20, 2025 at 5:27 AM Ihor Radchenko wrote: > > Louis Vigneras writes: > > > Following yantar92’s suggestion on the matrix channel, I am reporting > > here what appears to be a bug. > > > > I have

Re: Bug in org-element with jit-lock and visual lines, and folding

i discovered another major bug by coincidence. is it related? * folded lorem * unfolded point if i do an isearch backward, isearch will not notice lorem. it seems to act as if isearch-invisible were nil. isearch-invisible is its standard value of open. search-visible is its standard v

Re: Modifying org-mode links

Hi Heime, `org-insert-link' (bound to C-c C-l by default) lets you edit the link URL and display text for the link at point, if there is one. Otherwise, it inserts a link at point. This is what I use to edit links in all my org documents. Regards, Zoey On 21/7/25 09:11, Heime wrote: Have

Modifying org-mode links

Have been using the general link format to make internal links for use with the mouse. [[LINK][DESCRIPTION]] But then, how can I see it in its original text. I find it difficult to modify it when I use the delete key to remove the first "[".

Re: org element bug filling

i got the error upon scroll-up-command. [i am not sure if i was in the buffer being reported on for sure, but i always have only one window, so if so, it woudl be oerhaps strange that it would try to font lock something not visible. one thing that would help is if th4e warnings buffer could conta

Re: [BUG] Numeric priorities only partially supported

Sounds good. I'm happy to update the documentation, the regexp, and other mentioned locations to match one of A-Z or 0-64. Are we OK restricting it to uppercase only? Thanks! Derek On Sat, Jul 19, 2025 at 10:29 AM Ihor Radchenko wrote: > Derek Chen-Becker writes: > > > I guess looking at http

Re: org element bug filling

i will try, but i doubt that i wil be able to retrigger immediately aft4r the first trigger. On Sun, Jul 20, 2025 at 8:04 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > ⛔ Warning (org-element): org-element--cache: Org parser error in > > fix.org::22506. Resetting. > > The error was: (w

Re: Bug in org-element with jit-lock and visual lines, and folding

i use emacs isearch. no other packages related to isearch that i am aware of. is commenting out that line intended to fix the bug or cause a bug? it did not ause a bug. the bug is intermittent. On Sun, Jul 20, 2025 at 8:09 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > 2] as a heads

Suggestion: Document `org-extend-today-until` in Clock Table section

Hi Org Maintainers, In the Clock Table[1] documentation, I think that `org-extend-today-until` should be documented. For users that don't start their day at 00:00 midnight due to overnight shifts. People seem to be applying hacks around this [2] to get the desired effect. In fact I patched

Re: renumbering chapters

* Sharon Kimble [2025-07-20 16:14]: > Hi folks. > > I've written a book and just created a new chapter by splitting one in half. > > They are numbered Chapter 1, Chapter 2, etc, and they're all level one > headings. > > So how can I auto-renumber them please? #+TITLE: My Book #+OPTIONS: num:t

Re: [BUG] Misuse of `latexenc-find-file-coding-system` in `org-latex-compile` (Org 9.7.11)

Stephen Wheeler writes: > You're right that Org itself does not call > `latexenc-find-file-coding-system`, but the error appears during PDF export > when using Org 9.7.11 bundled with the Snap version of Emacs 31.0.50. > > Here is the **full backtrace**, obtained with `debug-on-error` enabled,

Re: [BUG] Org mode fails when export to latex buffer with auctex

Vangelis Evangelou writes: > Scenario 2: > >1. Load auctex and set TeX-parse-self to t >2. Create a scratch buffer and type in "\documentclass{amsart}". Note >that this is different from Scenario 1. The difference is that amsart uses >the amstex package. Org export to latex also u

Re: [BUG] Org mode fails when export to latex buffer with auctex when TeX-parse-self is t [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.1/lisp/org/)]

Vangelis Evangelou writes: > I started with emacs -q. Then in the scratch buffer, I evaluated the > following code > > (use-package reftex-auc) > (use-package tex > :load-path "site-lisp/auctex-14.0.9" > :custom > (TeX-parse-self t)) > > Then, I created an org buffer which I exported to lat

Re: [BUG] Misuse of `latexenc-find-file-coding-system` in `org-latex-compile` (Org 9.7.11)

Stephen Wheeler writes: > I am writing to report a bug in the LaTeX export pipeline in Org Mode 9.7.11 > as packaged with the Snap version of Emacs 31.0.50. The issue appears to stem > from a recent change in `org-latex-compile` which results in the following > error when exporting to PDF: > >

Re: [BUG] Invalid search bound (wrong side of point) [9.7.11 (release_9.7.11 @ d:/Programs/emacs-30.1/share/emacs/30.1/lisp/org/)]

Amit Tendulkar writes: > Emacs : GNU Emacs 30.1 (build 2, x86_64-w64-mingw32) > of 2025-02-23 > Package: Org mode version 9.7.11 (release_9.7.11 @ > d:/Programs/emacs-30.1/share/emacs/30.1/lisp/org/) > org--warnings '("org-element--cache: Org parser error in TODO.org::# at 284247 in TODO.org>

Re: Error Emacs told me to report

Jeffrey Brown writes: > Wait I was wrong about being wrong -- I *am* on 9.7.30. How strange. I > obliterated it from my .emacs.d/ folder, and the string "9.7.30" is not > present therein, and 9.7.30 still isn't part of the NixOS channel I'm on. > > And I see there's a new channel available. I'm u

Re: [BUG] org-element--list-struct: Tab width in Org files must be 8, not 4 [9.7.11 (release_9.7.11 @ /Applications/MacPorts/Emacs.app/Contents/Resources/lisp/org/)]

"Y. E." writes: >> Could you please upgrade and let me know if you still experience any >> problems? >> > > It's good to know the issue has already been addressed, thank you. > I encountered this only with one small project setup and currently use > whatever Macports-shipped Emacs app is packa

Re: [BUG] org-element--cache [9.7.31 (9.7.31-??-4e6d38d1a @ /home/buntu/.config/emacs/.local/straight/build-29.4/org/)]

Buntu Ngcebetsha writes: > Emacs : GNU Emacs 29.4 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, > cairo version 1.16.0) > of 2024-11-04 > Package: Org mode version 9.7.31 (9.7.31-??-4e6d38d1a @ > /home/buntu/.config/emacs/.local/straight/build-29.4/org/) > org--warnings '("org-elemen

Re: Bug in org-element with jit-lock and visual lines, and folding

Samuel Wales writes: > 2] as a heads up, upgrading to this version of org has caused a rise > in folding glitches. now, list actions, includign creating a new list > item, can intermittently and brokenly [e.g. in middle of headings] > fold headings, making it necessary to go up levels and toggle

Re: org element bug filling

Samuel Wales writes: > ⛔ Warning (org-element): org-element--cache: Org parser error in > fix.org::22506. Resetting. > The error was: (wrong-type-argument integer-or-marker-p nil) > Backtrace: > " backtrace-to-string(nil) > org-element-at-point() > org-adaptive-fill-function() > fill-mat

Re: Slow marking item DONE with many LOGBOOK entries

Yasushi SHOJI writes: > I've been experiencing slow `C-c t d` (org-todo DONE) with more than > 2000 LOGBOOK entries. Has anybody seen the same syndrome? > > I've narrowed it down to about 10 commits but around these commits I > started to have the following error and can't go down any more. > >

Re: Org mode version 9.8-pre (9.8-pre-n/a-g5b419c @ /Users/tsujp/.config/emacs/elpaca/builds/org/); Org parser error

Jordan Ellis Coppard writes: > I'm mostly submitting this because the *Warnings* log requests I do so. > It happens sometimes, and the org-file in-question is quite large and > (dare I say) complex. > ... > Package: Org mode version 9.8-pre (9.8-pre-n/a-g5b419c > @ /Users/tsujp/.config/emacs/elp

Re: org-persist causes delay when terminating emacs

mahmood sheikh writes: > this is related to > https://lists.gnu.org/archive/html/emacs-orgmode/2025-03/msg00166.html > i make heavy usage of the new org-latex-preview (not sure if its related) > the profiler report upon exiting (using `(add-hook 'kill-emacs-hook 'debug > 99)`) is included in this

Re: [BUG] org-mode warning [9.7.11 (release_9.7.11 @ c:/bin/emacs/emacs/share/emacs/30.1/lisp/org/)]

Adrian Chira writes: > Emacs : GNU Emacs 30.1 (build 2, x86_64-w64-mingw32) > of 2025-02-23 > Package: Org mode version 9.7.11 (release_9.7.11 @ > c:/bin/emacs/emacs/share/emacs/30.1/lisp/org/) > ... > org--warnings '("org-element--cache: Org parser error in all.org::165185. > Resetting.\n The

Re: [BUG] Exporting an org buffer from the source editor breaks editing

"Jacob S. Gordon" writes: > After exporting an `org` buffer in the editor of a source block, I > find that `org-edit-special` stops working in some places. To > reproduce: >... > ... > 5. At this point `org-edit-special` fails on the source blocks and >`LaTeX` equation with message “Marker do

Re: org-open-at-point fails to open files externally with double prefix

Max Nikulin writes: >> https://list.orgmode.org/t7aqif$c2f$1...@ciao.gmane.io/ >> [PATCH] org.el: Use `call-process' to launch external viewers (was: Re: >> [BUG] org-open-file immediately termininates when calling xdg-open that >> calls emacsclient). >> Fri, 3 Jun 2022 00:04:12 +0700 >> >> Co

Re: [BUG] Given timestamp with repeater, then it gets broken when it is manually updated [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]

Diego Ezequiel Vommaro writes: > SCHEDULED timestamp gets broken when I update it manually if it has a > repeater: > > 1. Given an entry like this > TODO do something > SCHEDULED: <2025-07-04 Fri .+1d> > > 2. Then I move forward the date manually > SCHEDULED: <2025-07-05 Fri .+

Re: Org mode version 9.8-pre (9.8-pre-n/a-g5b419c @ ~/.config/emacs/elpaca/builds/org/); org-persist: merging with disk file fails. Incorrect usage of cl-set-difference?

Umar Ahmad writes: > I've recently started facing some issues where all org files refuse to > load with the error message: > ``` > Debugger entered--Lisp error: (wrong-number-of-arguments # org-persist--find-index> 2) > ``` > I think the culprit is the use of cl-set-difference with > org-persist-

Re: [BUG] (Experimental LaTeX preview) org-persist-write-all causes Emacs to close very slowly [9.8-pre (cd2269ddb @ c:/Users//.emacs.d/straight/build/org/)]

Kai Bagley via "General discussions about Org-mode." writes: > After installing and using the org latex preview experimental features > according to https://abode.karthinks.com/org-latex-preview/, I get > severe freezing when closing Emacs, due to the `org-persist-write-all` > function in the `ki

Re: org-refile confusing refiling

jman writes: > I don't have the context to figure out things further, all I could do was > disabling xclip-mode > around executing `org-refile`: > > --8<---cut here---start->8--- > ;; disable xclip-mode before executing org-refile > (advice-add 'org-refile :b

Re: [BUG] reveal-mode and org-mode incompatibility

Brett writes: > Create a 3-line file named foobar.org containing exactly this: > ... > ... > But now, pressing TAB does nothing, while it should unfold the second > heading. In fact, moving around, folding/unfolding the first heading, etc, > will never fix the now broken TAB: from now on, if "**

renumbering chapters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi folks. I've written a book and just created a new chapter by splitting one in half. They are numbered Chapter 1, Chapter 2, etc, and they're all level one headings. So how can I auto-renumber them please? Thanks Sharon Kimble. - -- A ta

Re: [BUG] Error "Marker does not point anywhere" in Emacs 30.1 after export source block in latex or pdf [9.7.11 (release_9.7.11 @ /opt/homebrew/Cellar/emacs-plus@30/30.1/share/emacs/30.1/lisp/org/)]

Иван Чижов writes: > You need to do the following to reproduce the problem. > ... > ... > 5. In the file.org put the cursor in the source block and press C-c > '. You will get the error message "Marker does not point anywhere" and > the buffer will not open. Fixed, on bugfix. https://git.savan

Re: question about latex export and title

Przemysław Kamiński writes: > ... > This worked well for many months. However, sometime around April 2025 I > have my PDF files containing a TITLE which is some kind of > concatenation of current file name and the template-defined #+TITLE. > ... > However, when I have these 2 files: > > <2025-0

[FR] Org export: expanding links to included files (was: [BUG] Export backend cross-references are broken [9.7.30 (release_9.7.30 @ /home/user/org-mode-git/lisp/)])

Louis Vigneras writes: > Following yantar92’s suggestion on the matrix channel, I am reporting > here what appears to be a bug. > > I have an index.org file with the following: > #+include: chapter-1.org > #+include: chapter-2.org > > In chapter-1.org I have the following: > * Heading > [[file:c

Re: [BUG] org-capture--fill-template side-effect can occasionally cause org-roam-capture to fail to find file+head+olp target

Lewis Baker writes: > In org-capture--fill-template there is a section that creates a new buffer > named "*Capture*" and then activates this buffer so that it can insert the > template and perform various regexp search/replace operations on the > placeholders. However, the activation of this temp

Re: [BUG] org-capture with file+olp target matches todo keywords case insensitively

Lewis Baker writes: > The problem is that org-find-olp does not set case-fold-search to nil and > so the regular expression matching performs a case-insensitive match. > ... > This should be reproducible by running: > > (setq org-capture-templates > '(("t" "Do today" entry > (file+

Re: [BUG] org-edit-src-code with code argument is broken

hiecaq writes: > 1. `emacs -Q temp.org`, with the following content: > --8<---cut here---start->8--- > #+begin_src emacs-lisp > #+end_src > --8<---cut here---end--->8--- > > 2. Put cursor on the block and `M-:`, in eval type

Re: [BUG] Error about org-link-types when creating a link [9.7.31 (9.7.31-4e6d38 @ /home/dsmasterson/.emacs.d/elpa/org-9.7.31/)]

Ihor Radchenko writes: > But there is no such variable in Org mode - `org-link-types'. There is a > *function*. Bug in org-ac. Looks like there used to be such variable long time ago. But it has been removed in https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9bc294003 9 years ago

Re: [BUG] Error about org-link-types when creating a link [9.7.31 (9.7.31-4e6d38 @ /home/dsmasterson/.emacs.d/elpa/org-9.7.31/)]

David Masterson writes: > When trying to create a link in an Org file, I get the following errors > immediately after typing '[['. I can continue filling in the link and > autocomplete kicks in fine as I am typing the link. When closing the > link with ']]', the link is collapsed properly. Wha

Re: [BUG] Tags following a timestamp does not work.

Miki Kawabe writes: > I'm wondering if it's allowed to use both timestamp and tag in the same > headline in Org mode. > Although I read the manual on Tags and Timestamps, I couldn't find any > explanation for these limitation. > > org-open-at-point does not work for tags, when the tags are foll

Re: [PATCH][Worg] publish.sh: Suppress subscripts without braces

On 17/07/2025 16:02, Christian Moe wrote: Max Nikulin writes: I have noticed another case when "latex" in "#+begin_latex" is rendered as subscript in a Worg article. Do you expect massive regressions if subscript without explicit curly braces are suppressed? [...] org-contrib/babel/examples/d

Re: Users of org-publish

On 19/07/2025 19:32, Ihor Radchenko wrote: Also, note thathttps://orgmode.org/ andhttps://orgmode.org/worg/ are generated using publishing system 🙂 Worg uses custom elisp code for export that iterates over .org files, see publish.sh. Current CI does not allow persistent state required for sta

Re: [PATCH] org-protocol.org: Add history section (was: Re: [PATCH v5] WORG Org Protocol Page Rewrite)

On 15/07/2025 19:26, Christian Moe wrote: I've drafted a history section, attached here as a patch. Great work. I had only a part of added links in my notes. +make the code easier to maintain and offer more options, Carsten +Dominik [[https://list.orgmode.org/orgmode/c46f10dc-de51-43d4-affe

Re: [PATCH] ob-dot: Add `graphviz-dot' language alias

Ihor Radchenko writes: >> The test creates a `src' block with the language set to `any-language'. >> It passes with that fake language, but when I change it to something >> real, such as `c' or `fundamental', the indentation is incorrect, and >> the test fails. > > I can reproduce. > The test is

Re: Yesterday's meetup

Hi again. The change may need a bit more thinking: When testing, I got FAILED test-org-export/get-inbuffer-options ((should (equal (org-test-with-temp-text (format "#+DESCRIPTION: l1\n#+LANGUAGE: es\n#+SELECT_TAGS: a\n#+TITLE: a\n#+SETUPFILE: \"%s/examples/setupfile.org\"\n#+LANGUAGE: fr\n#+SEL