[BUG] ob-python hangs on second start [9.5.4 (release_9.5.4-763-g06373a @ ~/emacs/org-mode/lisp/)]

Expectation: When running ob-python code blocks, I should be able to kill the python session in the *Python* buffer and run another code block (or the same one). Problem: ob-python works fine on the first execution, but after `exit()`ing the python session, it hangs without executing the code.

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: > … > E.g. perhaps allowing a :noheadingexport: tag to prevent the export of > a heading would fit 90% of what is expected from inline tasks in the > example you gave. > … There is functionality for a `:noexport:' tag already built in. Do you intend `:noheadingexport:'

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: > On Thu, Aug 24, 2023 at 01:44:03PM +, Ihor Radchenko wrote: >> Russell Adams writes: >> >> >> What do you mean? >> > >> > I think Markdown has different levels? >> >> Do you mean # title vs. ## title? > > > > look at the

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

another idea, at the cost of 3 dumb messages in a row there are annotation packages. i wonder if integration of those is relevant. On 8/24/23, Samuel Wales wrote: > [p.s. not saying this will satisfy ardent users, just bringing up the > idea in case it is of use.] > > > On 8/24/23, Samuel

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

[p.s. not saying this will satisfy ardent users, just bringing up the idea in case it is of use.] On 8/24/23, Samuel Wales wrote: > iiuc bastien brought up the use of a no export this heading tag as an > alternative to inline tasks. we have much or all of this capability > in faq. > > i was

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

iiuc bastien brought up the use of a no export this heading tag as an alternative to inline tasks. we have much or all of this capability in faq. i was thinking the same thing. perhaps many use cases could have inline tasks as siblings below the document heading, and undesired headers could be

Unclear where ob-spice.el is being maintained

In 2022 I changed Melpa to get ob-spice.el from https://repo.or.cz/ob-spice.git in response to https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112. But org-contrib still contains that file and the README at the new location still contains > This source code is from

Re: Clarification on blank lines following list items

Thanks! -- Tom Alexander On Tue, Aug 22, 2023, at 4:26 AM, Ihor Radchenko wrote: > Ihor Radchenko writes: > >>> I am seeing dual-ownership of the post-blank in the examples below, but at >>> the same time if I put a plain-list inside a footnote definition, the >>> footnote definition ends up

Re: [MAINTENANCE] Org orphanage?

Jonas Bernoulli writes: > Please make your "membership" public at > https://github.com/orgs/emacsorphanage/people. Done, thanks! -- Bastien Guerry

Re: [MAINTENANCE] Org orphanage?

Thanks for offering to help out Corwin! >> Speaking for myself, I can help: >> [...] >> - review the bonafides (experience/involvement and, via Eli/SM, >> assignment status ) for prospective adopting maintainers > > Not sure about emacsorphanage side, but for things we decide to manage > on

Re: org-cite: how to force a reparsing of the .bib file

On Thu, Aug 24 2023, Ihor Radchenko wrote: > Leo Butler writes: > >>> Does the attached patch fix the problem? >> >> ... >> To avoid an unneeded setq, I applied the patch: >> >> (dolist (file (mapcar #'file-truename >> (org-cite-list-bibliography-files))) > > This would create an extra

Re: [MAINTENANCE] Org orphanage?

Bastien Guerry writes: > Sounds good to me too, I'm "bzg" on GitHub. Thanks! Invitation sent. Please make your "membership" public at https://github.com/orgs/emacsorphanage/people. Welcome! :D

[BUG] When calling org-tree-to-indirect-buffer: (wrong-type-argument listp org-fold-outline) in org-fold-core-get-folding-spec-from-alias [9.6.6 (release_9.6.6 @ /gnu/store/c7vqk20kf6zw73klr8bacnh0gqa

Hi, Since upgrading to Emacs 29.1 and Org 9.6.6, I am getting an error when opening a bookmark to an Org subtree buffer created with burly.el. When opening the bookmark, burly calls org-tree-to-indirect-buffer to make a new indirect buffer showing the subtree in question. This worked fine in

[BUG] org-cite-insert fails to open json format bibliographies that contain entries for books with editors but no authors [9.6.6 (release_9.6.6 @ /snap/emacs/current/usr/share/emacs/29.1/lisp/org/)]

Since upgrading to emacs 29.1 org-cite-insert no longer copes with bibliography files in json format where there is an entry for a book that has only editors and no author. Expected behaviour: Running org-cite-insert opens the bibliography file and allows me to search for a citation and

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On 24/08/2023 19:21, Ihor Radchenko wrote: As I described, I often want inlinetasks to be exported and to be displayed in my agenda/sparse tree views It sounds like that if agenda had hooks allowing to gather either :inlinetask:...:end: drawers or #+begin_inlinetask...#+end_inlinetask custom

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:41:39PM +, Ihor Radchenko wrote: > > Regressions are not the end of the world. Org does too much and grew > > very fast, which is not sustainable. > > But they should not be taken lightly either. > https://bzg.fr/en/the-software-maintainers-pledge/ I wouldn't

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: > org-inlinetask.el cannot exist outside Org core without all the extra > support for inlinetasks across Org codebase. I'm aware of this. > So, what you are suggesting will completely remove inlinetasks > feature. I suggest removing the support for inline tasks *as they

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:44:03PM +, Ihor Radchenko wrote: > Russell Adams writes: > > >> What do you mean? > > > > I think Markdown has different levels? > > Do you mean # title vs. ## title? https://www.markdownguide.org/basic-syntax look at the alternate syntax where they under line

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:29:22PM +, Ihor Radchenko wrote: > writes: > > >> > >><...> > > > > Ah... it would be nice if Org could "go up one level", > > wouldn't it? > > What do you mean? Not proposing to change anything, Org is what it is. Org's "sections" are somewhat

Org mode version 9.7-pre (9.7-pre-n/a-g63e8ca @ /home/n/.emacs.d/elpaca/builds/org/); [PATCH] refactor org-babel-lilypond-compile-lilyfile

The attached patch: - Improves the compilation message. (The target is the file, not LilyPond itself). - Refactors the body of the function to remove the many nondescript arg-n local variables. - Removes the optional TEST parameter, which is unused and better served through debugging

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:41:39PM +, Ihor Radchenko wrote: > Russell Adams writes: > > >> * [#inline] Inlinetask > >> * [#inline] END > > > > I think the multiline aspect is where the concept breaks down. > > > > "I want a special invisible heading inside the content of a heading, > > that

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: >> It will. And it will also break some of my workflows :( > > I think that's unfortunate, but perhaps it would improve the health of > the codebase? Removing most features would improve health of the codebase. Like getting rid of agenda with its horrible code. But it does

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: >> What do you mean? > > I think Markdown has different levels? Do you mean # title vs. ## title? > Has there ever been a reason to diversify the heading syntax to allow > levels or changes in visibility? > > ** TODO > > === TODO Inline item under todo > > --- DONE

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:36:39PM +, Ihor Radchenko wrote: > > And that's part of the confusion: inline tasks _look like_ normal > > tasks while behaving differently. > > Yup. That's why I think that we need to make inlinetasks have distinct > syntax. Do we have a concrete summary of

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: >> * [#inline] Inlinetask >> * [#inline] END > > I think the multiline aspect is where the concept breaks down. > > "I want a special invisible heading inside the content of a heading, > that also supports optional multiline contents". Sounds horrible to code. It is not.

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:33:01PM +, Ihor Radchenko wrote: > Russell Adams writes: > > > I hear "we have a bunch of extra complex code for an ill defined > > special case". Org's designed around headings, and this special case > > was a hack to abuse the threshold for heading detection to

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:29:22PM +, Ihor Radchenko wrote: > writes: > > >> > >><...> > > > > Ah... it would be nice if Org could "go up one level", > > wouldn't it? > > What do you mean? I think Markdown has different levels? It is interesting to think that Org has only one kind

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: >> I do not think that it would be possible. In order to support >> inlinetasks in agenda/sparse trees/todo setting/tag setting, we need to >> modify the internals. I see no way around that. > > Maybe we are miscommunicating: my suggestion is to _remove_ >

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: > I hear "we have a bunch of extra complex code for an ill defined > special case". Org's designed around headings, and this special case > was a hack to abuse the threshold for heading detection to support a > nonstandard heading. It was a hack to reduce the amount of

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

writes: >> >><...> > > Ah... it would be nice if Org could "go up one level", > wouldn't it? What do you mean? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 02:36:31PM +0200, Bastien Guerry wrote: > Ihor Radchenko writes: > > > ** Section X > > > > > > > > > > <...> > > > > <...> > > > > <...> > > > > *** TODO Task for paragraph N > > > > Then, if I jump to the TODO, for example, from agenda view, I still need > > to

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 01:04:10PM +, Ihor Radchenko wrote: > Russell Adams writes: > We might. Adding gazillion of stars is not conceptually different from > adding a spacial cookie. True. Just cleaner. > The only extra thing required is some way to mark inlinetask ending, > because we

Re: Org mode version 9.7-pre (9.7-pre-n/a-g63e8ca @ /home/n/.emacs.d/elpaca/builds/org/); [PATCH]: fix ob-lilypond docstrings

Ihor Radchenko writes: No Wayman writes: The attached patch satisfies all but two checkdoc warnings. I left those two for someone more familiar with the package. Thanks! Subject: [PATCH] * lisp/ob-lilypond.el: satisfy checkdoc _S_atisfy. (org-babel-lilypond-compile-post-tangle):

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: >> I see. So not only inline tasks are ugly syntactic-wise, but they >> also have a specific behavior when exporting. All this pleas for an >> external module, not for something we support in Org's core IMHO. > > I do not think that it would be possible. In order to

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 12:56:01PM +, Ihor Radchenko wrote: > Bastien Guerry writes: > > > Ihor Radchenko writes: > > > >> This will break export and folding. > >> Also, I often simply archive inlinetasks once they are done. The above > >> will archive too much. > > > > I see. So not only

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: > So just to be clear, we want a method to make a heading with all the > features of headings, but that isn't a heading or treated like a > heading? > Isn't the key feature that the inline task is a heading except it is > exempt from the folding logic (ie: sparse tree)? >

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: > Ihor Radchenko writes: > >> This will break export and folding. >> Also, I often simply archive inlinetasks once they are done. The above >> will archive too much. > > I see. So not only inline tasks are ugly syntactic-wise, but they > also have a specific behavior

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 12:40:50PM +, Ihor Radchenko wrote: > Bastien Guerry writes: > This will break export and folding. > Also, I often simply archive inlinetasks once they are done. The above > will archive too much. So just to be clear, we want a method to make a heading with all the

Re: [BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

On 2023-08-24 14:24, Ihor Radchenko wrote: > Jens Schmidt writes: > >> Would you mind if I added a test that explicitly and with some nice >> error message tests for that condition? I.e. if some unwary user >> strips off trailing whitespace in test-org.el, that test would fail >> with a

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: > This will break export and folding. > Also, I often simply archive inlinetasks once they are done. The above > will archive too much. I see. So not only inline tasks are ugly syntactic-wise, but they also have a specific behavior when exporting. All this pleas for an

Re: Org mode version 9.7-pre (9.7-pre-n/a-g63e8ca @ /home/n/.emacs.d/elpaca/builds/org/); [PATCH]: fix ob-lilypond docstrings

No Wayman writes: > The attached patch satisfies all but two checkdoc warnings. > I left those two for someone more familiar with the package. Thanks! > Subject: [PATCH] * lisp/ob-lilypond.el: satisfy checkdoc _S_atisfy. > (org-babel-lilypond-compile-post-tangle): fix docstring >

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: >> Then, if I jump to the TODO, for example, from agenda view, I still need >> to somehow find location, which is awkward when the >> section has multiple screens of text. > > And what about this? > >** Section X > > > > ><...> > >*** TODO

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: > ** Section X > > > > > <...> > > <...> > > <...> > > *** TODO Task for paragraph N > > Then, if I jump to the TODO, for example, from agenda view, I still need > to somehow find location, which is awkward when the > section has multiple screens of text. And what

Re: [BUG] Failing tests for ob-clojure

Hi! Ihor Radchenko writes: > I am now going through all the babel tests that are disabled by default. > > ob-clojure tests appear to be completely broken: > > 1. (org-test-for-executable "cider") assertion is strange as cider >package does not have any executable. > > 2. All the tests seems

Org mode version 9.7-pre (9.7-pre-n/a-g63e8ca @ /home/n/.emacs.d/elpaca/builds/org/); [PATCH]: fix ob-lilypond docstrings

The attached patch satisfies all but two checkdoc warnings. I left those two for someone more familiar with the package. >From ecd5fe22458db64d86650a1a7a1e697d9ccff020 Mon Sep 17 00:00:00 2001 From: Nicholas Vollmer Date: Thu, 24 Aug 2023 08:20:22 -0400 Subject: [PATCH] * lisp/ob-lilypond.el:

Re: [BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

Ihor Radchenko writes: > What we can do is setting `delete-trailing-lines' to nil in tests - via > directory-local variable. Never mind. This will not affect deleting empty lines that are not at the end of buffer.

Re: [BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

Jens Schmidt writes: > Would you mind if I added a test that explicitly and with some nice > error message tests for that condition? I.e. if some unwary user > strips off trailing whitespace in test-org.el, that test would fail > with a reasonable message. There is no universal rule when and

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Russell Adams writes: > * Item > > Wubba lubba ding dong. > > # TODO fix this to pig latin > > Arff!! > > * Other stuff > > > Doesn't this really come down to a use case for having headings which > are excluded from operations like comments are? Nope. As I described, I often want inlinetasks to

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: > Ihor Radchenko writes: > >> The benefit is that I do not need to search for that "paragraph N" when >> I want to work on the task. I simply jump to the task location and can >> immediately see the paragraph it refers to. > > But this would be the same with a non-inlined

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

On Thu, Aug 24, 2023 at 11:44:29AM +, Ihor Radchenko wrote: > Bastien Guerry writes: > > >> * TODO Consider explaining more about X > >> > >> > >> <...> > >> > >> Then, I can easily review the manuscript status using sparse tree or > >> agenda view. > > > > I see --

Re: C-RET and empty lines

On 22/08/2023 16:52, Ihor Radchenko wrote: Max Nikulin writes: Yes, it is intentional. Org follows the blank lines of the current heading when you press C-RET, by default. This behaviour is customizable. See `org-blank-before-new-entry'. Thank you for explanation. Frankly speaking, I missed

Re: [BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

On 2023-08-24 13:41, Ihor Radchenko wrote: > Jens Schmidt writes: > >> Seems the insert-heading-issue is still struggling, this time during >> a "make check" @ d5ee33fed8dd80d3f9f9811d86a73827fde80780 using Emacs 29: >> ... >>FAILED 998/1094 test-org/insert-heading (0.018306 sec) at >>

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: > The benefit is that I do not need to search for that "paragraph N" when > I want to work on the task. I simply jump to the task location and can > immediately see the paragraph it refers to. But this would be the same with a non-inlined task, right? > Also, pdf export

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Bastien Guerry writes: >> * TODO Consider explaining more about X >> >> >> <...> >> >> Then, I can easily review the manuscript status using sparse tree or >> agenda view. > > I see -- but what is the real benefit of inline tasks here over normal > tasks? I understand

Re: [BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

Jens Schmidt writes: > Seems the insert-heading-issue is still struggling, this time during > a "make check" @ d5ee33fed8dd80d3f9f9811d86a73827fde80780 using Emacs 29: > ... >FAILED 998/1094 test-org/insert-heading (0.018306 sec) at > ../lisp/test-org.el:1845 I cannot reproduce on my

Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?

Ihor Radchenko writes: > My personal use case is when using Org for authoring long texts. > I often leave inline tasks around the specific paragraph I need to > revise in future: > > * Section XX > > > > > <...> > > * TODO Consider explaining more about X > > > <...> >

Re: [patch] Fix inner smart quotes in French

Ihor Radchenko writes: > Agree. We can factor out the language names into a separate constant and > then use that constant as a source of "canonical" language names in > :type definitions of defcustom. Then, we can turn all the other > dictionary variables into defcustoms. Yes, sounds good! --

[BUG] "make check" reports a failure on test-org/insert-heading @ d5ee33f (this time with Emacs 29)

Seems the insert-heading-issue is still struggling, this time during a "make check" @ d5ee33fed8dd80d3f9f9811d86a73827fde80780 using Emacs 29: Test test-org/insert-heading condition: (ert-test-failed ((should (equal "* 1\n** 1.1\n** 1.2\n*\n* 2"

Re: [BUG] Compilation warnings when making main @ d5ee33fed8dd80d3f9f9811d86a73827fde80780

Jens Schmidt writes: >>> In org-element--properties-mapc: >>> org-element-ast.el:628:25:Warning: ‘not’ called with 3 args, but requires 1 >>> org-element-ast.el:628:30:Warning: reference to free variable ‘eq’ >> >> I also saw them. They do not make any sense. And they do not appear in >> Emacs

Re: [BUG] Compilation warnings when making main @ d5ee33fed8dd80d3f9f9811d86a73827fde80780

On 2023-08-24 13:18, Ihor Radchenko wrote: > Jens Schmidt writes: > >> Compiling /home/jschmidt/work/org-mode/lisp/org-element-ast.el... >> >> In org-element--properties-mapc: >> org-element-ast.el:628:25:Warning: ‘not’ called with 3 args, but requires 1 >> org-element-ast.el:628:30:Warning:

Re: [BUG] Compilation warnings when making main @ d5ee33fed8dd80d3f9f9811d86a73827fde80780

Jens Schmidt writes: > Compiling /home/jschmidt/work/org-mode/lisp/org-element-ast.el... > > In org-element--properties-mapc: > org-element-ast.el:628:25:Warning: ‘not’ called with 3 args, but requires 1 > org-element-ast.el:628:30:Warning: reference to free variable ‘eq’ I also saw them. They

[BUG] Compilation warnings when making main @ d5ee33fed8dd80d3f9f9811d86a73827fde80780

Compiling /home/jschmidt/work/org-mode/lisp/org-cycle.el... Compiling /home/jschmidt/work/org-mode/lisp/org-datetree.el... Compiling /home/jschmidt/work/org-mode/lisp/org-duration.el... Compiling /home/jschmidt/work/org-mode/lisp/org-element-ast.el... In org-element--properties-mapc:

[BUG] Failing tests for ob-clojure

Hi, I am now going through all the babel tests that are disabled by default. ob-clojure tests appear to be completely broken: 1. (org-test-for-executable "cider") assertion is strange as cider package does not have any executable. 2. All the tests seems to assert that ob-clojure supports

Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

On 2023-08-24 09:32, Ihor Radchenko wrote: > Jens Schmidt writes: >> Some obvious choice would be a simpler single backslash >> >> (B) "\-" => "-" > > I prefer (B). And we will need to allow escaping of the "\" itself. Like > \\. OK. Since backslash is not used yet in the rest of the

Re: Programmable deadline repeater

gus...@riseup.net writes: > Is it possible to configure a TODO item with a repeating deadline or > schedule to use a function to set the new timestamp when completed, > instead of just increasing of a fixed number of hours, days, weeks, > etc.? See `org-todo-repeat-hook'. -- Ihor Radchenko //

Re: plantuml tikz format support

Nan JunJie writes: > I'd like to add a patch to support plantuml tikz format. We can use it > like this: > > #+begin_src plantuml :file file.tikz > ... > #+end_src > > #+results: > [[file.tikz]] > > So that file.tikz will be treat as tikz picture and input. Thanks! This looks reasonable. May

Re: [BUG] HTML export locale problem [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

em...@supporter.mailer.me writes: > Today I was exporting my org file to HTML and I have run into an issue > with #+LANGUAGE. > I have set it to to "pl" and the Table of Contents name has changed, but > the figure names did not. > > Can somebody guide me on how could I fix it? This

Re: [BUG] emergency exit [9.6.6 (release_9.6.6 @ /opt/homebrew/Cellar/emacs-mac/emacs-29.1-mac-10.0/share/emacs/29.1/lisp/org/)]

Jay Dixit writes: > ⛔ Warning (org-element-cache): org-element--cache: Got empty parent while > parsing. Please report it to Org mode mailing list (M-x > org-submit-bug-report). > Backtrace: > nil May you update Org to the latest stable Org 9.6.8 version and let us know if the error persists?

Re: [BUG] org-element--cache: Org parser error (error "rx '**' range error") [9.7 (9.7-??-d6f3aed7b @ /Users/fbartik/.config/emacs/.local/straight/build-29.1/org/)]

fb--- via "General discussions about Org-mode." writes: > I'm very new to Emacs and org and I'm running into this issue when I > start Emacs from scratch and reload my last session. > > The error I get looks like this and there are multiples on each start: > > Warning (org-element-cache):

Re: How to solve "Warning (emacs): Please update the LaTeX src-block-backend to listings"

Guillaume MULLER writes: > I'm trying to create a code block with some latex code to be interpreted > inside. I only knew lstlistings until now. Page > https://orgmode.org/manual/Source-blocks-in-LaTeX-export.html lists Engraved > and Minted as possible backend. >

Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

Jens Schmidt writes: >> When "TAG1-TAG2" is an actual tag name with dash, we may allow escaping. > > But I'd like to clarify that. From the Org syntax > > https://orgmode.org/worg/org-syntax.html#Headings > > I understood that tag names cannot contain minus characters, > and `org-tag-re' does

Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]

Jens Schmidt writes: > Yet another edge-case: In the Org syntax definition a property > name is really delimited by a "colon-whitespace" sequence. This > takes out the ambiguity whether a property name is defined > non-greedily > > :[^[:space:]]+?: > > or greedily > > :[^[:space:]]+: > >

Re: org-cite: how to force a reparsing of the .bib file

Leo Butler writes: >> Does the attached patch fix the problem? > > ... > To avoid an unneeded setq, I applied the patch: > > (dolist (file (mapcar #'file-truename > (org-cite-list-bibliography-files))) This would create an extra list and increase GC pressure. So, I prefer setq. > This

Re: [PATCH] Fix docstring of `org-at-timestamp-p'

Liu Hui writes: > I find that the doc string of `org-at-timestamp-p' about match groups > is not consistent with the behavior. The doc string says > > ... > but for timestamps like <2023-08-23 Wed>, (when (org-at-timestamp-p) > (match-string 2)) will return the year 2023 instead of the month.

[BUG] org-element--cache: Org parser error (error "rx '**' range error") [9.7 (9.7-??-d6f3aed7b @ /Users/fbartik/.config/emacs/.local/straight/build-29.1/org/)]

Hi, I'm very new to Emacs and org and I'm running into this issue when I start Emacs from scratch and reload my last session. The error I get looks like this and there are multiples on each start: Warning (org-element-cache): org-element--cache: Org parser error in config.el::5943.

Programmable deadline repeater

Good day, Is it possible to configure a TODO item with a repeating deadline or schedule to use a function to set the new timestamp when completed, instead of just increasing of a fixed number of hours, days, weeks, etc.? Regards, Gustek

plantuml tikz format support

I'd like to add a patch to support plantuml tikz format. We can use it like this: #+begin_src plantuml :file file.tikz ... #+end_src #+results: [[file.tikz]] So that file.tikz will be treat as tikz picture and input. Here the patch: >From c97e5f421202ac2bfd16174c2d4be4059b0aa4c8 Mon Sep 17

[BUG] HTML export locale problem [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Hello everyone, Today I was exporting my org file to HTML and I have run into an issue with #+LANGUAGE. I have set it to to "pl" and the Table of Contents name has changed, but the figure names did not. Can somebody guide me on how could I fix it? Kind regards Emacs User Info: