Re: Requesting a new release of org-contrib.

Malcolm Purvis writes: > Emacs 29 and the new main branch (emacs-30) require the 't' > condition in a cl-case to be the last entry. This breaks > org-checklist in version 0.4 of org-contrib. > > The fix has already been applied >

Re: bug#59882: Multiple versions of Org in load-path problem

Stefan Monnier writes: >> Though I believe that org mixed version issue happens due to transitional >> dependency of some third party package on org or something like (require >> 'org-protocol) that can not be loaded on demand. > > Hmm... indeed the "Subject:" talks about mixed versions, yet I

Re: [BUG] Documentation fix needed in "4.4 External Links" [9.6 ( @ /home/dsmasterson/.emacs.d/elpa/org-9.6/)]

David Masterson writes: >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=edd000f3b > > Possibly good, but should the docstrings for org-open-at-point, > org-open-at-mouse and org-open-file be unified in way so that they track > each other for changes in one of them?

Re: bug#59882: Multiple versions of Org in load-path problem

Max Nikulin [2022-12-14 23:02:53] wrote: > On 14/12/2022 21:35, Stefan Monnier wrote: >>> Like I said in another message that I sent just before receiving yours >>> my conclusion came from the fact that hitting 'C-h v' with the cursor >>> on 'org-goto-interface' provided nothing.

Re: [BUG] Documentation fix needed in "4.4 External Links" [9.6 ( @ /home/dsmasterson/.emacs.d/elpa/org-9.6/)]

Ihor Radchenko writes: > David Masterson writes: > >> Do you think (some part of) this (semi-)paragraph should be mentioned in >> the docstring for 'org-open-at-point' (and 'org-open-at-mouse')? I'm of >> the opinion that, if you walk-thru the docstring links, you would get >> all the info

Re: [BUG] ox-html does not export captions of source blocks without language

On Wed, Dec 14, 2022, at 22:51, Kaushal Modi wrote: > On Wed, Dec 14, 2022, 4:44 PM Johan Bolmsjö > wrote: >> The caption "Caption 1" is not exported by ox-html in the following >> source block. >> >> #+caption: Caption 1 >> #+begin_src >> foo bar baz >> #+end_src > > The begin_src block

Re: [BUG] ox-html does not export captions of source blocks without language

On Wed, Dec 14, 2022, 4:44 PM Johan Bolmsjö wrote: > ** Description > > The caption "Caption 1" is not exported by ox-html in the following > source block. > > #+caption: Caption 1 > #+begin_src > foo bar baz > #+end_src > The begin_src block always requires a "language" as far as I know. If

RE: bug#59882: Multiple versions of Org in load-path problem

>On a related note, is it normal that package like org-mouse.el gets >loaded upon calling C-h f org-mouse- completion prompt? >org-mouse.el does not contain a single autoload cookie. There need not be which is apparently by design: The autoload happens as a consequence of emacs' documented

[BUG] ox-html does not export captions of source blocks without language

** Description The caption "Caption 1" is not exported by ox-html in the following source block. #+caption: Caption 1 #+begin_src foo bar baz #+end_src The caption "Caption 2" is exported by ox-html in the following source block. #+caption: Caption 2 #+begin_src sh echo foo bar baz #+end_src

[BUG] org-element--cache: (org-agenda) Cached element is incorrect [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

While trying to reproduce the "Org parser error" error issue (see other thread), I got multiple "Cached element is incorrect" warnings (backtrace excerpt below). Here is one that appeared when trying to loading the =t= agenda: -- quote -- Warning (org-element-cache): org-element--cache:

Re: org-agenda-dim-blocked-tasks don't use org-todo face

On Tue, Dec 13, 2022 at 2:51 AM Ihor Radchenko wrote: > > Mark Kerr writes: > > > Thank you. I may have been unclear but the result seems to be the > > opposite of what I was hoping for. > > > > I was hoping to be able to gain the ability to use the org-todo face > > with blocked tasks, while

Re: Is org-show-all obsolete?

Ypo writes: > Has org-show-all changed in the version 9.6? > > Now, org-show-all doesn't appear in the "vertico > " > completion candidates. > > Is org-show-all obsolete? Is there an alternative? org-show-all is a function

Is org-show-all obsolete?

Has org-show-all changed in the version 9.6? Now, org-show-all doesn't appear in the "vertico " completion candidates. Is org-show-all obsolete? Is there an alternative? Best regards

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

Stefan writes: > (plain-list (:type unordered :begin 712169 :end 712176 :contents-begin 712169 > :contents-end 712175 :structure ((712169 0 "- " nil "[ ]" nil 712175)) ...)) Curious. What about (org-element-at-point 712029)? (like in your backtrace) If no error is thrown in this way as well,

Re: Completely hide properties drawer in 9.6

Sterling Hooten writes: > (let* ((block (org-get-property-block)) > ;; Extremely hacky way to get the whole property drawer > (beg (- (car block) 14)) > (end (+ (cdr block) 5))) > (with-silent-modifications > (org-fold-region beg end t

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

(plain-list (:type unordered :begin 712169 :end 712176 :contents-begin 712169 :contents-end 712175 :structure ((712169 0 "- " nil "[ ]" nil 712175)) ...)) For the record, the last heading in Stefan.org looks like this: -- quote -- ** DONE [#A] Set alarm clock for presentation CLOSED:

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

Stefan writes: > thanks for the fast reaction. > > Here is the backtrace, again from the =a= agenda: > > https://gist.githubusercontent.com/stefan2904/0bb5d9db84664a4f4225cd809c294964/raw/e0ac2ec53d4b1d2fed57e440b8fb23157ecbab3d/redacted-backtrace.log Thanks! What happens if you run M-:

Re: Completely hide properties drawer in 9.6

I was able to get a very rough version working to fold and hide the properties drawer completely at point. #+begin_src emacs-lisp (defun swh-org-hide-properties-drawer () "Completely hide the property drawer in heading at point." (org-fold-add-folding-spec 'org-hide-property-drawer

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

Hi Ihor, all, thanks for the fast reaction. Here is the backtrace, again from the =a= agenda: https://gist.githubusercontent.com/stefan2904/0bb5d9db84664a4f4225cd809c294964/raw/e0ac2ec53d4b1d2fed57e440b8fb23157ecbab3d/redacted-backtrace.log Best, Stefan On Wed, Dec 14, 2022, at 16:17, Ihor

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

Interestingly, as I was looking through my notes in orgstrap, I see my past self had found a macro org-babel-one-header-arg-safe-p which pointed to defconst org-babel-safe-header-args, but that is a const and not really user configurable. Of course the user could cl-setf on it, but it also only

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

Tom, does not the following allow to achieve the same without your patch? #+begin_src elisp :results none (setq-local org-confirm-babel-evaluate (lambda (lang body) (not (and (member lang '("elisp" "emacs-lisp")) (let ((rb (read body))) (or

Re: Radio links work only in small numbers

Max Nikulin writes: > On 14/12/2022 06:10, Rudolf Adamkovič wrote: >> >> All [[link]]s in my notes perfectly match LEVEL-1 headings, so I figured >> that I may as well ask Org to make links for me. So, I replaced all the >> ~4000 headings in my notes with radio <<>>. However, Org now >>

Re: bug#59882: Multiple versions of Org in load-path problem

On 14/12/2022 21:35, Stefan Monnier wrote: Like I said in another message that I sent just before receiving yours my conclusion came from the fact that hitting 'C-h v' with the cursor on 'org-goto-interface' provided nothing. It was the first time this ever happened to me.

Re: Radio links work only in small numbers

On 14/12/2022 06:10, Rudolf Adamkovič wrote: All [[link]]s in my notes perfectly match LEVEL-1 headings, so I figured that I may as well ask Org to make links for me. So, I replaced all the ~4000 headings in my notes with radio <<>>. However, Org now errors out with "Regular expression too

Re: For your consideration: Extending org-info-js with additional hooks

At Ihor's invitation, I'd like to mention that I can help maintain org-info-js going forward. I'm not a JavaScript expert but I seem to be doing fine with adding my hooks and figuring out how the code works. Please let me know what I can do to help out with maintenance. I already have copyright

Re: Radio links work only in small numbers

Ihor Radchenko writes: > Can you try the attached patch? No luck: "Regular expression too big" Still too large: (length org-target-link-regexp) => 33219 :-( Rudy -- "Programming reliably -- must be an activity of an undeniably mathematical nature […] You see, mathematics is about

Re: [PATCH] Merge loaded org-persist index with index file contents

Hi All, Since there have been no further comments, I’ve just pushed a tweaked version of this patch (with Max’s comments addressed and with a minor oversight fixed) as 555dacfa8. All the best, Timothy -- Timothy (‘tecosaur’/‘TEC’), Org mode contributor. Learn more about Org mode at

Re: [BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

Stefan writes: > I recently upgraded to Org 9.6 via Git (and to Emacs 28 with nativecomp), and > since then I get this kind of warnings all the time. They appear at different > spots in my org files and there is nothing special with the headings in > question. > > This specific warning

Re: Does variable 'org-goto-interface' exist?

On 14/12/2022 17:20, Alain.Cochard wrote: my conclusion came from the fact that hitting 'C-h v' with the cursor on 'org-goto-interface' provided nothing. It was the first time this ever happened to me. I did try to explicitly enter the variable's name by entering 'org-goto', which (like

Re: Completely hide properties drawer in 9.6

Sterling Hooten writes: >> On 2022-12-14, at 06:15, Ihor Radchenko wrote: >> >> I do have this implemented in local branch. Just did not push it >> upstream as it was rejected. > > Could you share that here so I could test it? https://github.com/yantar92/org/tree/feature/org-font-lock-element

Re: bug#59882: Multiple versions of Org in load-path problem

> similar issues with several important Org components (ol-* and ob-*). In > particular, ob-*.el packages affect Org simply by defining function > symbols with specific name patters (by ob-core.el design). > Achieving no side effects is difficult in practice. That's true. It can be a balancing

[BUG] org-element--cache: Org parser error [9.6 (release_9.6-90-gf49ee9 @ /home/stefan/.emacs.d/contrib/org-mode/lisp/)]

Hello everyone, I recently upgraded to Org 9.6 via Git (and to Emacs 28 with nativecomp), and since then I get this kind of warnings all the time. They appear at different spots in my org files and there is nothing special with the headings in question. This specific warning appears when I

Re: Completely hide properties drawer in 9.6

> On 2022-12-14, at 06:15, Ihor Radchenko wrote: > > I do have this implemented in local branch. Just did not push it > upstream as it was rejected. Could you share that here so I could test it? > Note that Emacs 29 does not have issues with large numbers of overlays. I’m using the MacOS

Re: bug#59882: Multiple versions of Org in load-path problem

>> On a related note, is it normal that package like org-mouse.el gets >> loaded upon calling C-h f org-mouse- completion prompt? Yes. See `help-enable-completion-autoload`. >> I am asking because org-mouse.el advises some functions and its loading >> may cause unexpected consequences. See >>

Re: Does variable 'org-goto-interface' exist?

On 14/12/2022 14:55, Ihor Radchenko wrote: Max Nikulin writes: Perhaps it is better to introduce some more concise notation to specify the package where a custom option or variable is defined like ~org-goto-interface~ (=org-goto.el=). ... Note, however, that org-goto is probably not the

Re: bug#59882: Multiple versions of Org in load-path problem

Eli Zaretskii writes: >> I am asking because org-mouse.el advises some functions and its loading >> may cause unexpected consequences. See >> https://orgmode.org/list/87r0x6sju1@fastmail.fm > > I think org-mouse.el should be fixed not to cause such effects just by > loading it. It should do

[HELP] Things to help Org that do not involve programming

Esteban Ordóñez writes: >> More things also require translation in `org-export-dictionary'. > > That sounds long Is there something concrete which is important to > help with? I can destinate about 2 hours per week. Maybe a little > more. `org-export-dictionary' is not really that long.

Re: bug#59882: Multiple versions of Org in load-path problem

> From: Ihor Radchenko > Cc: David Masterson , emacs-orgmode@gnu.org, > mic...@schi.nz, 59...@debbugs.gnu.org > Date: Wed, 14 Dec 2022 09:51:01 + > > On a related note, is it normal that package like org-mouse.el gets > loaded upon calling C-h f org-mouse- completion prompt? > org-mouse.el

Re: Does variable 'org-goto-interface' exist?

alain.coch...@unistra.fr writes: > > Note, however, that org-goto is probably not the only place where we > > refer to a customization that is not loaded by default. I am unsure how > > many places like this exist > > I am not taking any side regarding the point Max brought up, but your >

Re: Does variable 'org-goto-interface' exist?

Ihor Radchenko writes on Wed 14 Dec 2022 07:55: > This particular note is largely aiming at new users not too > familiar with Emacs system. > [...] > Note, however, that org-goto is probably not the only place where we > refer to a customization that is not loaded by default. I am unsure

Re: Does variable 'org-goto-interface' exist?

Max Nikulin writes on Wed 14 Dec 2022 17:01: > On 13/12/2022 15:54, Alain.Cochard wrote: > > At the end of section 2.3 (Motion) of the manual: > > > > See also the variable ‘org-goto-interface’. > > > > But this variable does not seem to exist. > > Alain, could you, please,

Re: 2a529ee57 org-element: Autoload org-element-use-cache

Kyle Meyer writes: > Ihor Radchenko writes: > >> You wrote in the commit message that autoload.el is deprecated in Emacs >> 29. Do we need to do anything about it in Org make system? > > Yes, though I don't consider it urgent given the deprecation hasn't even > made it into a release. I was

Re: Does variable 'org-goto-interface' exist?

On 13/12/2022 15:54, Alain.Cochard wrote: At the end of section 2.3 (Motion) of the manual: See also the variable ‘org-goto-interface’. But this variable does not seem to exist. Alain, could you, please, clarify, what you was trying to do when you came to conclusion that

Re: [BUG] org-mouse is activated without explicit require

Max Nikulin writes: > On 13/12/2022 16:52, Ihor Radchenko wrote: >> Max Nikulin writes: >> We have `org-modules' that can handle calling `org-link-set-parameters'. > ...> We can simply process 'ol-* in `org-modules' specially. > > I do not consider it is a good idea. Third party packages

Re: bug#59882: Multiple versions of Org in load-path problem

Eli Zaretskii writes: >> So, 'describe-variable' on org-version causes Org to be loaded?!? > > Why is it so surprising? Is this the first time you see that a Help > command loads something to do its job? On a related note, is it normal that package like org-mouse.el gets loaded upon calling

Re: PATCH: include controlling language= in my previous patch

Pedro Andres Aranda Gutierrez writes: > Next try... I'm learning a lot :-) Then, next set of comments. (Note that I can hand-fix the patches at this point for you. Let me know if you want to keep going) > From dabdc3026e32ec674e22698de6257d724f60c4af Mon Sep 17 00:00:00 2001 > From: "Pedro A.

Re: Completely hide properties drawer in 9.6

Sterling Hooten writes: > In Ihor suggested > adding `org-custom-properties-hide-emptied-drawers', this was > rejected, but is pretty close to the desired behavior, except it's > still global. I was unable to get this working in release 9.6.

Re: Timestamps being changed in exporting to HTML ?

David Masterson writes: > I just noticed that Org timestamps of the following form: > > <2006-11-02 Thu 20:00-22:00> > > are being changed to this form in HTML export: > > <2006-11-02 Thu 20:00>-<2006-11-02 Thu 22:00> # note single '-' > > Is this proper? Transformation from 20:00-22:00 to

Re: [BUG] Documentation fix needed in "4.4 External Links" [9.6 ( @ /home/dsmasterson/.emacs.d/elpa/org-9.6/)]

David Masterson writes: > Do you think (some part of) this (semi-)paragraph should be mentioned in > the docstring for 'org-open-at-point' (and 'org-open-at-mouse')? I'm of > the opinion that, if you walk-thru the docstring links, you would get > all the info you'd get in the manual (and more),

Re: Radio links work only in small numbers

Rudolf Adamkovič writes: > Greetings smart people! > > All [[link]]s in my notes perfectly match LEVEL-1 headings, so I figured > that I may as well ask Org to make links for me. So, I replaced all the > ~4000 headings in my notes with radio <<>>. However, Org now > errors out with "Regular

Re: [BUG] issue with texmathp [9.6 (release_9.6-22-g78d283 @ /home/jds6696/.emacs.d/straight/build/org-mode/)]

Justin Silverman writes: > Thanks for the quick response. I just had a chance to check it out. > Unfortunately (unless I am mistaken), with the change, `texmathp' is now > always returning t... which is not very helpful. Not exactly. I just tried to follow the docstring (defun

Re: [BUG] org-mouse.el breaks org-open-at-point

Matt Lundin writes: >> Patches welcome! >> >> I think we need to modify `org-open-at-mouse' directly instead of >> using advice. > > I can give this a try. > > The advice in org-mouse.el currently does the following: > > - cycles when on headline > - toggles checkbox when on checkbox > -

Re: Does variable 'org-goto-interface' exist?

Max Nikulin writes: > On 13/12/2022 18:43, Ihor Radchenko wrote: >> + Note: ~org-goto-*~ variables are only accessible when =org-goto= >> + library is loaded using ~require~ statement in the config or >> + auto-loaded by calling ~org-goto~ interactively. > > Perhaps it is better to introduce