[BUG] "Not enough arguments for format string" from failed fuzzy search containing % [9.6.19]

2024-02-24 Thread Corwin Kerr
Hello,

When a search link with a fuzzy expression contains the % character
and is not found in the file, the error message is burried by format
error. This affects ~org-link-search~, ~org-open-file~, etc.

Expected message:
: No match for fuzzy expression: % search bad
Actual message:
: Not enough arguments for format string

I ended up with this search term by storing a link to a comment in a tex file.

Here is the backtrace from how I originally discovered it:
#+begin_src elisp
  Debugger entered--Lisp error: (error "Not enough arguments for format string")
  format-message("No match for fuzzy expression: % search bad")
  apply(format-message "No match for fuzzy expression: % search bad")
  error("No match for fuzzy expression: % search bad")
  org-open-file(".../bad-file.tex" nil nil "% search bad")
  apply(org-open-file ".../bad-file.tex" nil (nil "% search bad"))
  org-link-open-as-file(".../bad-file.tex::% how thi..." nil)
  org-link-open((link (:type "file" :path ".../bad-file.tex" :format bracket 
:raw-link "file:.../bad-file.tex::% ho..." :application nil :search-option "% 
search bad" :begin 8347 :end 8450 :contents-begin 8432 :contents-end 8447 
:post-blank 1 :parent (paragraph (:begin 8347 :end 8461 :contents-begin 8347 
:contents-end 8460 :post-blank 1 :post-affiliated 8347 :mode nil :granularity 
element :cached t :parent (section (:begin 8312 :end 8461 :contents-begin 8312 
:contents-end 8460 :robust-begin 8312 :robust-end 8458 :post-blank 1 
:post-affiliated 8312 :mode section :granularity element :cached t :parent 
(headline ...) :org-element--cache-sync-key nil)) :org-element--cache-sync-key 
nil nil)
  org-open-at-point()
  org-open-at-mouse((mouse-2 (# 8438 (138 . 355) 
272166805 nil 8438 (14 . 16) nil (5 . 5) (11 . 22
  funcall-interactively(org-open-at-mouse (mouse-2 (# 
8438 (138 . 355) 272166805 nil 8438 (14 . 16) nil (5 . 5) (11 . 22
  call-interactively(org-open-at-mouse nil nil)
  command-execute(org-open-at-mouse)
#+end_src

* Versions
GNU Emacs 28.2 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 Version 
10.14.6 (Build 18G95)) of 2023-02-22
Org mode version 9.6.19 (release_9.6.19 @ 
/Users/Corwin/.emacs.d/straight/repos/org/lisp/)

* Minimal reproduction
#+begin_src tex :tangle bad-file.tex
  \begin{document}
  % search attempt
  \end{document}
#+end_src

#+begin_src elisp :tangle minimal.el
  (setq debug-on-error t
debug-on-signal nil
debug-on-quit nil)

  ;; Add latest Org mode to load path.
  (add-to-list 'load-path (expand-file-name 
"~/.emacs.d/straight/repos/org/lisp"))
  
  (org-open-file "bad-file.tex" nil nil "% search attempt") ;; works
  (org-open-file "bad-file.tex" nil nil "% search bad") ;; error
#+end_src

Running emacs with
: /Applications/Emacs.app/Contents/MacOS/Emacs -Q -l /path/to/minimal.el

Generates this backtrace:
#+begin_src elisp
  Debugger entered--Lisp error: (error "Not enough arguments for format string")
  format-message("No match for fuzzy expression: % search bad")
  apply(format-message "No match for fuzzy expression: % search bad")
  error("No match for fuzzy expression: % search bad")
  (condition-case err (org-link-search search) (error (funcall 
save-position-maybe) (error (nth 1 err
  (cond (line (org-goto-line line) (if (derived-mode-p 'org-mode) (progn 
(org-fold-reveal (search (condition-case err (org-link-search search) 
(error (funcall save-position-maybe) (error (nth 1 err))
  (cond ((org-string-nw-p cmd) (setq cmd (org--open-file-format-command cmd 
file link link-match-data)) (let ((wconfig (current-window-configuration))) 
(unwind-protect (progn (message "Running %s...done" cmd) (let 
((process-connection-type nil)) (start-process-shell-command cmd nil cmd)) (and 
(boundp 'org-wait) (numberp org-wait) (sit-for org-wait))) 
(set-window-configuration wconfig ((or (stringp cmd) (eq cmd 'emacs)) 
(funcall (cdr (assq 'file org-link-frame-setup)) file) (widen) (cond (line 
(org-goto-line line) (if (derived-mode-p 'org-mode) (progn (org-fold-reveal 
(search (condition-case err (org-link-search search) (error (funcall 
save-position-maybe) (error (nth 1 err))) ((functionp cmd) (let 
((save-match-data-internal (match-data))) (unwind-protect (progn 
(set-match-data link-match-data) (condition-case nil (funcall cmd file link) 
((debug wrong-number-of-arguments wrong-type-argument invalid-function) 
(user-error "Please see Org News for version 9.0 about `org-fil..." cmd 
(set-match-data save-match-data-internal 'evaporate ((consp cmd) 
(user-error "Please see Org News for version 9.0 about `org-fil..." cmd)) (t 
(funcall (cdr (assq 'file org-link-frame-setup)) file)))
  (let* ((file (if (equal path "") buffer-file-name (substitute-in-file-name 
(expand-file-name path (file-apps (append org-file-apps 
(org--file-default-apps))) (apps (cl-remove-if #'org--file-apps-entry-locator-p 
file-apps)) (apps-locator (cl-remove-if-not #'org--file-apps-entry-locator-p 
file-apps)) 

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

2024-02-24 Thread Matt


  On Sat, 24 Feb 2024 17:42:54 +0100  Bruno Barbier 

 > I'll publish a branch soon; it will be a major rewrite of my current
 > proposal.  It should be less confusing and, I hope, address some of your
 > comments.
 > 
 > Thanks again for your questions and feedbacks,

You're welcome and thanks for sharing your ideas.

Any lack of comments from me recently is just limited time and trying to focus 
on maintenance.

--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode





Re: [PATCH] Handle block-type when checking `org-src-fontify-natively'

2024-02-24 Thread Nathaniel Nicandro


Ihor Radchenko  writes:

> Nathaniel, is there any particular problem you encountered that your
> patch was aiming to solve? If no, we should probably re-add fontifying
> example blocks as undocumented feature people rely on in practice.

No there wasn't any particular problem, I was just browsing the code and
saw that it was undocumented behavior.

-- 
Nathaniel



Re: [BUG] FAQ asnwer for "How can I use arbitrary colors for words/sentences in HTML export?" is outdated

2024-02-24 Thread Ihor Radchenko
Bastien Guerry  writes:

>> Bastien, could you, please, have a look at the CI configuration. I do
>> not see recent builds in
>> https://builds.sr.ht/~bzg/worg
>
> I just triggered a new build myself.
>
> The secret key needed to launch the build has been shared with other
> users, including Ihor and you: can you (or Ihor) tell me if you see a
> shared key somewhere in your sr.ht profile?

I am seeing 7a38e4c8-2b08-446e-a478-2a114a50db86 key shared by you at
https://builds.sr.ht/secrets

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [BUG] org clock wants to resolve clocks every time a clock in, occurs [9.7 (9.7-??-0dd2c5e @, /home/aayush/.config/emacs/.local/straight/build-29.2/org/)]

2024-02-24 Thread Ihor Radchenko
Sau P  writes:

> What should happen?
> When I clock in, the clock should continue
> until I clock out (or go idle).
>
> What actually happens?
> Every minute I will get a popup requesting me to resolve a clock.
>
> This has been happening for a number of days now and I thought I had
> dangling clocks but I don't think this is the case.

> Even after "resolving" the clock (I have exhausted every option the
> popup gives), the resolve popup comes back a minute later.

Sounds like your `org-clock-idle-time' is customized to a small number
(1 minute).

> I believe I have seen someone with a similar issue on stackexchange,
> here is the link:
> https://emacs.stackexchange.com/questions/70084/resolving-idle-time-after-forced-closing-crash

That sounds different and that is not a bug - org-clock-out does not
trigger clock resolution. Only attempting to clock-in will do it.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [BUG] org-contrib/org-static-mathjax is not operational [9.7-pre (release_9.6.18-1153-gee395b.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

2024-02-24 Thread Ihor Radchenko
Bastien Guerry  writes:

>> Should we obsolete the library?
>
> I removed org-static-mathjax.el from org-contrib and released 0.5.

Fixed.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: When closing an org file, if the file contains Chinese characters, it always prompts me to choose an encoding system.

2024-02-24 Thread Ihor Radchenko
fang yu  writes:

> I encountered an issue while using org-mode. Whenever the file contains 
> Chinese characters, it always prompts me to choose an encoding system.
>
> My emacs version is 29.2 and my org-mode version is 9.6.15, and  I have 
> language environment setting below 
>
> ;; set language environment
> (set-language-environment 'UTF-8)
> (set-locale-environment "UTF-8”)
> ...
> Can anyone tell me if there is a way to solve this problem? Thank you in 
> advance.

This is unlikely anything related to Org mode. Something about Emacs
language config.

I personally have
(set-language-environment "English")
(prefer-coding-system 'utf-8)
(add-to-list 'file-coding-system-alist '("\\.org" utf-8))
in my config.
Although, it is copy-pasted from somewhere.

It may help to study the output of M-x describe-language-environment
while inside Org buffer.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [BUG] Invalid search bound (wrong side of point) [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]

2024-02-24 Thread Ihor Radchenko
Diego Sánchez  writes:

> Emacs : GNU Emacs 29.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
> 3.24.40, cairo version 1.18.0)
> Package: Org mode version 9.6.15 (release_9.6.15 @ 
> /usr/share/emacs/29.2/lisp/org/)

 Thanks for reporting!
 May you try the development version of Org mode and let us know if you
 still see the warning?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [BUG] wrong side of point error in org-element-cache [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]

2024-02-24 Thread Ihor Radchenko
Robert Place  writes:

> When opening an org file I received this warning.
>
> Emacs  : GNU Emacs 29.2 (build 1, aarch64-apple-darwin21.6.0, NS 
> appkit-2113.60 Version 12.6.6 (Build 21G646))
>  of 2024-01-18
> Package: Org mode version 9.6.15 (release_9.6.15 @ 
> /Applications/Emacs.app/Contents/Resources/lisp/org/)

Thanks for reporting!
May you try the development version of Org mode and let us know if you
still see the warning?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

2024-02-24 Thread Bruno Barbier



Ihor Radchenko  writes:

> Bruno Barbier  writes:
>
>>> May you please clarify if adding the new code block parameter that
>>> defines custom execute function is something you want to add to Org mode
>>> or just a helper code to demo you main patch?
>>
>> Yes. (I thought about adding it in a separate request;  but that would be
>> simpler to include it.)
>
> I have doubts about how useful such parameter would be for _users_. It
> is certainly useful for developers of new babel backends, but I do not
> see how users will use it.
>
> I'd prefer to discuss this in a separate thread.

Sure. I'll keep it for an other thread.


>>> Error buffer does not necessarily appear on failure. When the code leads
>>> to process writing to stderr, we also display error buffer. Even if the
>>> process exits with 0 code.
>>
>> Got it.  The current design adds the popup on failure; I should make it
>> more flexible to allow to configure a popup on success too.
>
> By popup, do you mean an overlay where clicking on it will raise the
> usual `org-babel-eval-error-notify' buffer?
> If yes, what happens if a user executes a code block, it fails, and the
> user executes it again without looking at the error? (Second execution
> may be triggered from a different place, indirectly, via noweb ref or
> similar).

Current behavior is to remove the error, and, then re-execute: the
previous errors are gone.  My guess is that this could be improve later,
without breaking the API.


>> But if the execution fails, I guess I'll need to provide some feedbacks
>> anyway, but I don't know yet how (asynchronous popups are not an option,
>> modifying the file neither).
>
> We need something more than just an overlay. Maybe some kind of babel
> execute history (in tabulated-list-mode buffer), keeping information
> about execution stats and stderr data.
>
> We may provide a mode-line or fringe indicator that will warn user if
> something went wrong with recent executions. Something akin compile-mode
> mode line indicator listing errors and warnings during compilation.

I was thinking about using a fringe indicator, for warnings on success (as I'm
removing all overlays on success).

Keeping a buffer of all asynchronous executions looks like a good idea.
I'll think about it.


> (Handling asynchronous messages is actually a complex topic. It has been
> previously discussed on emacs-devel as well. See
> )

I'll look at this.  Thanks!

I'll publish a branch soon; it will be a major rewrite of my current
proposal.  It should be less confusing and, I hope, address some of your
comments.

Thanks again for your questions and feedbacks,

Bruno

>
> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 



Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

2024-02-24 Thread Rick Lupton
Thanks for your help with it!

On Sat, 24 Feb 2024, at 1:02 PM, Ihor Radchenko wrote:
> Bastien Guerry  writes:
>
>>> "Rick Lupton"  writes:
>>>
 On Fri, 9 Feb 2024, at 12:09 PM, Ihor Radchenko wrote:
> May you please update on your FSF copyright assignment status?

 I believe the agreement is all signed and completed. 
>>>
>>> Bastien, may your please check FSF records?
>>
>> Done, and it is well in order.
>
> Thanks for checking!
> Applied, onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6e7e0b2cd
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=95554543b
>
> and added a record to the contributor list.
> https://git.sr.ht/~bzg/worg/commit/0ccaf58a
>
> Rick, thanks for your contribution!
>
> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 



[BUG] wrong side of point error in org-element-cache [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]

2024-02-24 Thread Robert Place


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


When opening an org file I received this warning.

Emacs  : GNU Emacs 29.2 (build 1, aarch64-apple-darwin21.6.0, NS appkit-2113.60 
Version 12.6.6 (Build 21G646))
 of 2024-01-18
Package: Org mode version 9.6.15 (release_9.6.15 @ 
/Applications/Emacs.app/Contents/Resources/lisp/org/)

current state:
==
(setq
 org-link-elisp-confirm-function 'yes-or-no-p
 org-hide-emphasis-markers t
 org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-log-done 'time
 org-agenda-files '("~/iCloudDrive/Notes/fiserv/ctlm/fiserv.bmc.notes.org"

"/Users/rplace/iCloudDrive/Notes/fiserv/ad-cleanup/fiserv.db.project.org")
 org-persist-after-read-hook '(org-element--cache-persist-after-read)
 org-export-before-parsing-hook '(org-attach-expand-links)
 org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
 org-ascii-format-drawer-function #[771 ".\207" [] 4 "\n\n(fn NAME CONTENTS 
WIDTH)"]
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines
  org-cycle-optimize-window-after-visibility-change 
org-cycle-display-inline-images)
 org-persist-before-read-hook '(org-element--cache-persist-before-read)
 org-link-from-user-regexp "|\\"
 org-mode-hook '(org-bullets-mode
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-fold-show-all append 
local] 5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all 
append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
 #[0 "\301\211.\207" [imenu-create-index-function 
org-imenu-get-tree] 2]
 visual-line-mode company-mode yas-minor-mode flyspell-mode)
 org-babel-load-languages '((python . t))
 org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 outline-isearch-open-invisible-function 'outline-isearch-open-invisible
 org-startup-indented t
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-tangle-lang-exts '(("python" . "py") ("emacs-lisp" . "el") ("elisp" 
. "el"))
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-hide-leading-stars t
 org-mime-src-mode-hook '(org-mime-src-mode-configure-edit-buffer)
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 org-fold-core-isearch-open-function 'org-fold-core--isearch-reveal
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-persist-before-write-hook '(org-element--cache-persist-before-write)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-link-shell-confirm-function 'yes-or-no-p
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-loop-over-headlines-in-active-region nil
 org-occur-hook '(org-first-headline-recenter)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-link-parameters '(("attachment" :follow org-attach-follow :complete 
org-attach-complete-link)
   ("eww" :follow org-eww-open :store org-eww-store-link)
   ("rmail" :follow org-rmail-open :store 
org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow org-irc-visit :store org-irc-store-link 
:export org-irc-export)
   ("info" :follow org-info-open :export org-info-export 
:store org-info-store-link
:insert-description org-info-description-as-command)
   ("gnus" :follow org-gnus-open :store org-gnus-store-link)
   ("docview" :follow org-docview-open :export 
org-docview-export :store
org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store 
org-bibtex-store-link)
  

Re: Warn about shell-expansion in the docstring of org-latex-to-html-convert-command

2024-02-24 Thread Martin Edström
Ah yes. My custom Node script (which I hope it's OK to paste below) strips
the beginnings and ends of the input. I suppose that it could be done
already on the Elisp side, which would take care of interpreting the
$-signs as envvars too.

const katex = require('katex')
let input = process.argv[2].trim()
let disp = true
if (input.slice(0, 2) === '\\[' || input.slice(0, 2) === '$$') {
  input = input.slice(2, -2)
}
else if (input.slice(0, 2) === '\\(') {
  input = input.slice(2, -2)
  disp = false
}
else if (input.slice(0, 1) === '$') {
  input = input.slice(1, -1)
  disp = false
}
else {
  console.error("Did you quote the input correctly?")
  process.exit(1)
}
console.log(katex.renderToString(
  input, {
displayMode: disp,
output: 'mathml',
trust: true,
strict: false,
throwOnError: false,
  }
))

On Wed, Feb 21, 2024 at 15:38 Max Nikulin  wrote:

> On 19/02/2024 02:36, Martin Edström wrote:
> > +Since this is a shell-command, remember to use single-quotes
> > +around \\='%i\\=', not double-quotes!  Else a math fragment such
> > +as \"$y = 200$\" gets butchered into only \" = 200\"."
>
> I am afraid, the code, not the docstring must be fixed. I have not tried
> it, but I expect an issue with
>
>  Test \(f' = df/dx\)
>
> So `shell-quote-argument' is necessary and quotes around %i must be
> stripped similar to %s in mailcap entries in `org-open-file'.
>
> Notice that dollar-math $x = y$ is not recommended and considered as
> obsolete syntax. Use \(x = y\) or \[x = y\] (the latter for display math).
>


Re: Help: How to change faces of words between parenthesis

2024-02-24 Thread Kepa

Thanks, William

I'm not writing citation. I am studying a text, and it has citations. To 
delete them all, generates friction, while to let them all be, generates 
distraction. So with the help of Ihor (and chatgpt) I have added this 
code to my init file, so they are shadowed:


(defun yant/apply-custom-faces ()
  (add-to-list 'org-font-lock-extra-keywords 
'("(\\([A-Z][a-zA-Z]*[^)]*[0-9]\\{4\\}[^)]*\\))" . (0 'shadow prepend)) 
'append))

(add-hook 'org-font-lock-set-keywords-hook #'yant/apply-custom-faces)


About citations: A time ago I learned to use org-ref, but my PC is not 
very powerful, so Emacs turned to be too slow. Then I stopped working 
with citations.


By now I am adding bibtex properties to my headlines, so in the future I 
can use org-bibtex and probably I will learn about citation with your 
tutorials: https://www.miskatonic.org/2024/01/08/org-citations-basic/


Best regards


On 14/02/2024 0:33, William Denton wrote:

On Sunday, February 11th, 2024 at 08:57, Ypo  wrote:


Could it be possible to change the color of words between parentheses?

For example, in:

"mejorar su bienestar psicológico (Cronin et al., 2012; Molero, Fuster, Jetten y 
Moriano, 2011; Outten, Schmitt, García y Branscombe, 2009; Pérez-Garín et al., 
2016)."

For citations in brackets, another approach might be to use Org's citation 
system with the CSL export processor, and then use András Simonyi's 
org-cite-csl-activate and customize the face:

https://github.com/andras-simonyi/org-cite-csl-activate

That might involve changing your whole citation process, which is a big step, 
but citations are on my mind so I thought I'd mention it.

Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada





Best regards

[BUG] org clock wants to resolve clocks every time a clock in, occurs [9.7 (9.7-??-0dd2c5e @, /home/aayush/.config/emacs/.local/straight/build-29.2/org/)]

2024-02-24 Thread Sau P

What should happen?
When I clock in, the clock should continue
until I clock out (or go idle).

What actually happens?
Every minute I will get a popup requesting me to resolve a clock.

This has been happening for a number of days now and I thought I had
dangling clocks but I don't think this is the case.

Even after "resolving" the clock (I have exhausted every option the
popup gives), the resolve popup comes back a minute later.

I believe I have seen someone with a similar issue on stackexchange,
here is the link:
https://emacs.stackexchange.com/questions/70084/resolving-idle-time-after-forced-closing-crash


Thank you,


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.




Emacs  : GNU Emacs 29.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.40, cairo version 1.18.0)
Package: Org mode version 9.7 (9.7-??-0dd2c5e @ 
/home/aayush/.config/emacs/.local/straight/build-29.2/org/)


current state:
==
(setq
 org-agenda-prefix-format '((agenda . " %-4e %-12:c%?-12t % s ") (todo 
. " %-2i %-4e %-12:c")

    (tags . " %i %-12:c") (search . " %i %-12:c"))
 org-archive-location "/home/aayush/org/.archive/%s::"
 org-link-elisp-confirm-function nil
 org-appear-autokeywords t
 org-agenda-category-icon-alist '(("uni"
   (#("" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 0.8)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 0.8)
   display (raise 0.0) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  ("todo"
   (#("" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 1.0)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 1.0)
   display (raise 0.005) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  ("note"
   (#("๕" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 0.9)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 0.9)
   display (raise 0.0) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  ("project"
   (#("ಶ" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 0.9)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 0.9)
   display (raise 0.0) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  ("Knowledge"
   (#("ᙋ" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 0.8)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 0.8)
   display (raise 0.0) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  ("Personal"
   (#("ฐ" 0 1
  (face (:family "Symbols Nerd Font 
Mono" :height 0.9)
   font-lock-face (:family "Symbols 
Nerd Font Mono" :height 0.9)
   display (raise 0.0) 
rear-nonsticky t)

  )
    )
   nil nil :ascent center)
  )
 org-directory "~/org/"
 org-cite-insert-processor 'citar
 org-after-refile-insert-hook '(save-buffer)
 org-indirect-buffer-display 'current-window
 org-hide-emphasis-markers t
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-export-with-sub-superscripts '{}
 org-agenda-todo-keyword-format "%-6s"
 org-yank-adjusted-subtrees t
 org-log-done 'time
 org-pomodoro-long-break-sound 

Re: Warn about shell-expansion in the docstring of org-latex-to-html-convert-command

2024-02-24 Thread Martin Edström
And ignore my suggestion about stripping input on the Elisp side.
Didn't think that through.

On Wed, 21 Feb 2024 at 16:04, Martin Edström  wrote:
>
> Actually, I agree about your test case, that looks like it'd cause a problem.
>
> So we patch the function to use `shell-quote-argument'?
>
> On Wed, 21 Feb 2024 at 15:38, Max Nikulin  wrote:
> >
> > On 19/02/2024 02:36, Martin Edström wrote:
> > > +Since this is a shell-command, remember to use single-quotes
> > > +around \\='%i\\=', not double-quotes!  Else a math fragment such
> > > +as \"$y = 200$\" gets butchered into only \" = 200\"."
> >
> > I am afraid, the code, not the docstring must be fixed. I have not tried
> > it, but I expect an issue with
> >
> >  Test \(f' = df/dx\)
> >
> > So `shell-quote-argument' is necessary and quotes around %i must be
> > stripped similar to %s in mailcap entries in `org-open-file'.
> >
> > Notice that dollar-math $x = y$ is not recommended and considered as
> > obsolete syntax. Use \(x = y\) or \[x = y\] (the latter for display math).



[BUG] Invalid search bound (wrong side of point) [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]

2024-02-24 Thread Diego Sánchez




Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See

https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.




Emacs : GNU Emacs 29.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.40, cairo version 1.18.0)
Package: Org mode version 9.6.15 (release_9.6.15 @ 
/usr/share/emacs/29.2/lisp/org/)


current state:
==
(setq
org-link-elisp-confirm-function 'yes-or-no-p
org-agenda-diary-file "~/Documentos/diary.org"
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 
"\n\n(fn ENTRY)"]

org-agenda-files '("~/Documentos/ToDo.org")
org-persist-after-read-hook '(org-element--cache-persist-after-read)
org-export-before-parsing-hook '(org-attach-expand-links)
org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)

org-archive-hook '(org-attach-archive-delete-maybe)
org-odt-format-inlinetask-function 
'org-odt-format-inlinetask-default-function
org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME 
CONTENTS WIDTH)"]
org-cycle-hook '(org-cycle-hide-archived-subtrees 
org-cycle-show-empty-lines

org-cycle-optimize-window-after-visibility-change
org-cycle-display-inline-images)
org-persist-before-read-hook '(org-element--cache-persist-before-read)
org-mode-hook '(activate-default-input-method (lambda nil (texfrag-mode))
org-fragtog-mode
#[0 "\301\211\207" [imenu-create-index-function
org-imenu-get-tree] 2] org-modern-mode
#[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-fold-show-all append local] 5]
#[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-babel-load-languages '((latex . t))
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-ellipsis "…"
org-agenda-tags-column 0
org-latex-format-headline-function 
'org-latex-format-headline-default-function

org-confirm-shell-link-function 'yes-or-no-p
org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
outline-isearch-open-invisible-function 'outline-isearch-open-invisible
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-auto-align-tags nil
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-latex-packages-alist '(("" "tikz" t))
org-babel-tangle-lang-exts '(("latex" . "tex") ("emacs-lisp" . "el") 
("elisp" . "el"))
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)

org-confirm-elisp-link-function 'yes-or-no-p
org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function

org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-modern-mode-hook '(org-modern-mode-set-explicitly)
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-fold-core-isearch-open-function 'org-fold-core--isearch-reveal
org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function

org-persist-before-write-hook '(org-element--cache-persist-before-write)
org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)

org-link-shell-confirm-function 'yes-or-no-p
org-agenda-finalize-hook '(org-modern-agenda 
org-agenda-property-add-properties)

org-babel-pre-tangle-hook '(save-buffer)
org-agenda-loop-over-headlines-in-active-region nil
org-occur-hook '(org-first-headline-recenter)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-link-parameters '(("eww" :follow org-eww-open :store 
org-eww-store-link)

("rmail" :follow org-rmail-open :store
org-rmail-store-link)
("mhe" :follow org-mhe-open :store org-mhe-store-link)
("irc" :follow org-irc-visit :store org-irc-store-link
:export org-irc-export)
("info" :follow org-info-open :export org-info-export
:store org-info-store-link :insert-description
org-info-description-as-command)
("gnus" :follow org-gnus-open :store org-gnus-store-link)
("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
("w3m" :store org-w3m-store-link) ("doi" :follow
org-link-doi-open :export org-link-doi-export)
("attachment" :follow org-attach-follow :complete
org-attach-complete-link) ("id" :follow org-id-open)
("file+sys") ("file+emacs") ("shell" :follow
org-link--open-shell)
("news" :follow #[514 "\301\300\302Q\"\207" ["news"
browse-url ":"] 6 "\n\n(fn URL ARG)"])
("mailto" :follow #[514 "\301\300\302Q\"\207"
["mailto" browse-url ":"] 6 "\n\n(fn URL ARG)"])
("https" :follow #[514 "\301\300\302Q\"\207" ["https"

Re: Warn about shell-expansion in the docstring of org-latex-to-html-convert-command

2024-02-24 Thread Martin Edström
Actually, I agree about your test case, that looks like it'd cause a problem.

So we patch the function to use `shell-quote-argument'?

On Wed, 21 Feb 2024 at 15:38, Max Nikulin  wrote:
>
> On 19/02/2024 02:36, Martin Edström wrote:
> > +Since this is a shell-command, remember to use single-quotes
> > +around \\='%i\\=', not double-quotes!  Else a math fragment such
> > +as \"$y = 200$\" gets butchered into only \" = 200\"."
>
> I am afraid, the code, not the docstring must be fixed. I have not tried
> it, but I expect an issue with
>
>  Test \(f' = df/dx\)
>
> So `shell-quote-argument' is necessary and quotes around %i must be
> stripped similar to %s in mailcap entries in `org-open-file'.
>
> Notice that dollar-math $x = y$ is not recommended and considered as
> obsolete syntax. Use \(x = y\) or \[x = y\] (the latter for display math).



Re: [BUG] FAQ asnwer for "How can I use arbitrary colors for words/sentences in HTML export?" is outdated

2024-02-24 Thread Bastien Guerry
Max Nikulin  writes:

> Bastien, could you, please, have a look at the CI configuration. I do
> not see recent builds in
> https://builds.sr.ht/~bzg/worg

I just triggered a new build myself.

The secret key needed to launch the build has been shared with other
users, including Ihor and you: can you (or Ihor) tell me if you see a
shared key somewhere in your sr.ht profile?

There has been a change in builds.sr.ht: now only pushes by the owner
trigger a build, *unless* the owner shared the secret key with other
users. So far I don't understand why users with whom I've shared the
key cannot trigger a build.

-- 
 Bastien Guerry



Re: [DISCUSSION] Add "Recent News" to orgmode.org

2024-02-24 Thread Bastien Guerry
I'm all for any experiment that will help interesting Org post get
more traction.

If someone wants to play with https://git.sr.ht/~bzg/orgweb so that 
it includes latest Org posts from Sacha's URL, please go ahead!

A complementary suggestion: let's activate the "Blog" tab on Woof (at
https://tracker.orgmode.org) so that when people send an email to the
list prefixed with [BLOG], it is referenced on this tab. Then, a RSS
feed is available from https://tracker.orgmode.org/blog.rss that we
can parse on orgmode.org.

Let me know if activating the detection of BLOG posts on the mailing
list sounds useful.

-- 
 Bastien Guerry



Re: org-contrib: Remove org-eval-light.el and org-evel.el

2024-02-24 Thread Bastien Guerry
Ihor Radchenko  writes:

> According to https://orgmode.org/worg/org-contrib/#org4b339dd,
> org-eval-lite "... is a reworking of Carsten's org-eval with the goals
> of a more uniform syntax, safer default execution rules, and increased
> ease of execution. Written by Eric Schulte. Link to raw file. This
> modules has been superseded by the Org Babel functionality, which is
> ^^
> part of the Org core and documented in the manual."
>
> The same for org-eval.
>
> Considering how long Org Babel is a part of Org core, it is probably the
> time to remove org-eval-light and org-eval from org-contrib - they are
> of no use.

Done in 0.5 too, thanks!

-- 
 Bastien Guerry



Re: [BUG] org-contrib/org-static-mathjax is not operational [9.7-pre (release_9.6.18-1153-gee395b.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

2024-02-24 Thread Bastien Guerry
Hi Ihor,

Ihor Radchenko  writes:

> Since we observe no bug reports about org-static-mathjax, it does not
> look like anyone at all is using it.
>
> Should we obsolete the library?

I removed org-static-mathjax.el from org-contrib and released 0.5.

Thanks!

-- 
 Bastien Guerry



Re: [FR] Org mode sr.ht project page: add familiar links for newcomers

2024-02-24 Thread Bastien Guerry
Hi Ihor,

Ihor Radchenko  writes:

> Sourcehut is known for unusual interface that looks foreign for users
> coming from GitHub background.
>
> Some SourceHut projects employ an approach to use Github-compatible
> terminology and link to the corresponding Sourcehut pages:
>
> [Issues] [Pull requests] [Discussions] [Wiki]
>
> I suggest doing the same, with the following mapping:
>
> [[orgmode.org/][Home page]]
> [[https://tracker.orgmode.org/][Issues]]
> [[mailto:emacs-orgmode@gnu.org][New issue]]
> [[https://tracker.orgmode.org/patches][Pull requests]]
> [[https://list.orgmode.org/][Discussions]]
> [[https://orgmode.org/worg/][Wiki]]

Done here: https://git.sr.ht/~bzg/org/commit/b6234e0

Feel free to enhance it!

> It would also be nice to have "New issue" button in
> https://tracker.orgmode.org/

Noted here:
https://lists.sr.ht/~bzg/woof/%3C87wmqulzne.fsf%40bzg.fr%3E

-- 
 Bastien Guerry



Re: bug#66291: [Leo Vivier] [PATCH] orgalist: Update bug:31361 workaround for new upstream signature

2024-02-24 Thread Bastien Guerry
Ihor Radchenko  writes:

> Nicolas Goaziou  writes:
>
>> To answer Ihor's question : I'm out of touch concerning Org development,
>> so maintaining a package such as Orgalist may be problematic at some
>> point, indeed.
>
> Then, may we need to ask someone to help maintaining orgalist?
> Similar question about a number of Org mode libraries where you are
> listed as a maintainer.

Yes, we definitely need to do this!

-- 
 Bastien Guerry



Re: Ada/SPARK support in Babel

2024-02-24 Thread Bastien Guerry
Ihor Radchenko  writes:

> My initial assessment is that we might include babel support for Ada if
> it is accompanied by good set of tests, so that we do not need to worry
> too much about things breaking even if there is no ob-ada maintainer.
>
> ... and let's see if the original author is still interested to continue
> with his request.

FWIW +1

-- 
 Bastien Guerry



Re: [PATCH] org-ctags: Fix regexp to not break radio targets

2024-02-24 Thread Ihor Radchenko
Bastien Guerry  writes:

>> Bastien, may you please check FSF records?
>
> Yes, Martin's FSF record is okay.  Thanks!

Updated our records.
https://git.sr.ht/~bzg/worg/commit/a93fa90a

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

2024-02-24 Thread Ihor Radchenko
Bastien Guerry  writes:

>> "Rick Lupton"  writes:
>>
>>> On Fri, 9 Feb 2024, at 12:09 PM, Ihor Radchenko wrote:
 May you please update on your FSF copyright assignment status?
>>>
>>> I believe the agreement is all signed and completed. 
>>
>> Bastien, may your please check FSF records?
>
> Done, and it is well in order.

Thanks for checking!
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6e7e0b2cd
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=95554543b

and added a record to the contributor list.
https://git.sr.ht/~bzg/worg/commit/0ccaf58a

Rick, thanks for your contribution!

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

2024-02-24 Thread Ihor Radchenko
Bruno Barbier  writes:

>> May you please clarify if adding the new code block parameter that
>> defines custom execute function is something you want to add to Org mode
>> or just a helper code to demo you main patch?
>
> Yes. (I thought about adding it in a separate request;  but that would be
> simpler to include it.)

I have doubts about how useful such parameter would be for _users_. It
is certainly useful for developers of new babel backends, but I do not
see how users will use it.

I'd prefer to discuss this in a separate thread.

>> Error buffer does not necessarily appear on failure. When the code leads
>> to process writing to stderr, we also display error buffer. Even if the
>> process exits with 0 code.
>
> Got it.  The current design adds the popup on failure; I should make it
> more flexible to allow to configure a popup on success too.

By popup, do you mean an overlay where clicking on it will raise the
usual `org-babel-eval-error-notify' buffer?
If yes, what happens if a user executes a code block, it fails, and the
user executes it again without looking at the error? (Second execution
may be triggered from a different place, indirectly, via noweb ref or
similar).

> But if the execution fails, I guess I'll need to provide some feedbacks
> anyway, but I don't know yet how (asynchronous popups are not an option,
> modifying the file neither).

We need something more than just an overlay. Maybe some kind of babel
execute history (in tabulated-list-mode buffer), keeping information
about execution stats and stderr data.

We may provide a mode-line or fringe indicator that will warn user if
something went wrong with recent executions. Something akin compile-mode
mode line indicator listing errors and warnings during compilation.

(Handling asynchronous messages is actually a complex topic. It has been
previously discussed on emacs-devel as well. See
)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: [PATCH] org-ctags: Fix regexp to not break radio targets

2024-02-24 Thread Bastien Guerry
Ihor Radchenko  writes:

> Martin Marshall  writes:
>
>> Ihor Radchenko  writes:
>>> I also see that you submitted a number of patches recently.
>>> For now, your contribution size is fairly small, but if you plan to
>>> contribute a lot more, please consider signing FSF copyright assignment.
>>> See https://orgmode.org/worg/org-contribute.html#copyright
>>
>> Thanks, I submitted a copyright assignment a year or two ago with
>> respect to a pull-request submitted for the which-key package.  Not sure
>> if it's project-specific, or if I'll need to submit a separate one
>> (which I'm happy to do of course).
>
> If your assignment has "GNU Emacs" in it, you are good to go.
>
> Bastien, may you please check FSF records?

Yes, Martin's FSF record is okay.  Thanks!

-- 
 Bastien Guerry



Re: [PATCH v2] org-id: allow using parent's existing id in links to headlines

2024-02-24 Thread Bastien Guerry
Hi,

Ihor Radchenko  writes:

> "Rick Lupton"  writes:
>
>> On Fri, 9 Feb 2024, at 12:09 PM, Ihor Radchenko wrote:
>>> May you please update on your FSF copyright assignment status?
>>
>> I believe the agreement is all signed and completed. 
>
> Bastien, may your please check FSF records?

Done, and it is well in order.

-- 
 Bastien Guerry



Re: [BUG] ox-texinfo can't export example blocks [9.6.9 (release_9.6.9 @ /usr/local/share/emacs/30.0.50/lisp/org/)]

2024-02-24 Thread Ihor Radchenko
[ Adding Org mailing list back to CC for public record ]

pva-outd...@yandex.ru writes:

>> Please describe your problem in more details. What do you mean by "can't
>> export"? See https://orgmode.org/manual/Feedback.html#Feedback
>
> To reproduce my problem you can write create an org-mode buffer (C-x b
> 1.org M-x org-mode) with the following content:
>
> #+begin_src lua :tangle yes  :noweb yes
>   aaa
>   <>
> #+end_src
>
> #+name: second
> #+begin_src 
>  bbb
> #+end_src
>
> Then enable exporting to texinfo and export the buffer:
>   M-: (require 'ox-texinfo)
>   C-c C-e i t
>
> The folllowing backtrace appears (providing you already enabled
> debugging on errors):

Thanks!
I fixed this and similar problems on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f90322377
Fixed.

> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   apply(debug error (wrong-type-argument stringp nil))
>   edebug(error (wrong-type-argument stringp nil))
>   signal(wrong-type-argument (stringp nil))
>   edebug-signal(wrong-type-argument (stringp nil))
>   string-match("lisp" nil nil t)
>   string-match-p("lisp" nil)
> ...

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: org-agenda-filter-by-category not working in block agendas due to inconsistent truncation

2024-02-24 Thread Ihor Radchenko
John Mathena  writes:

> The category of items in an "agenda" block view as returned by
> org-agenda-get-category are truncated based on the value of the prefix
> format; this isn't the case for e.g. the tags-todo view. For instance,
> if an item has a category "marathon training", and your agenda and
> tags-todo views both have prefix formats of " %8.8:c ", calling
> org-agenda-get-category on that item while it's being displayed in the
> agenda will yield a category of "marathon", while calling it on the
> same item in the tags-todo view will yield "marathon training".

Thanks for reporting!
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=19db45f2c

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: org-goto bug

2024-02-24 Thread Ihor Radchenko
Pan Xie  writes:

> Just found a minor issue about the org-goto interface. When I set 
> `org-goto-auto-isearch' as `t', the number keys should also be part of 
> isearch, not treated as "digit argument". However, the current version 
> (9.7-pre) of OrgMode I am using treat the number keys as digit argument 
> in auto isearch mode.
>
> I also find the solution: just pass `t' as second argument to 
> `suppress-keymap', to make all number keys unbound in the keymap:

Thanks for reporting!
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4b1399fb2

Unconditionally passing t would break things when
`org-goto-auto-isearch' is nil. So, I went with slightly different
approach.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at