[BUG] Org parser error when removing latex preview [9.6.15 (release_9.6.15 @ /gnu/store/gnvv2a1nxfbibkm1wdxdv6bd6mhk4cf8-emacs-29.3/share/emacs/29.3/lisp/org/)]

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.

Re: [FR] :noweb-wrap header arg

Ihor Radchenko writes: > Amy Grinn writes: > >> +(insert raw) >> +(goto-char (point-min)) >> +(while (< (point) (point-max)) >> + (unless (looking-at " *\"\\([^\"]+\\)\" *") >> +(looking-at " *\\([^ ]+\\)")) > > May you please explain the rationale

Re: [BUG] Customizing org-emphasis-alist does not work as expected [9.6.15 (release_9.6.15 @ d:/emacs_home/program/emacs/share/emacs/29.2/lisp/org/)]

Max Nikulin writes: >> I have updated the docstring to explain this. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=42cdf2a90 > > Have you decided to discard another variant that warns users? > > Ihor Radchenko… [PATCH v5] org.el: Warning for unsupported markers in >

[PATCH] lisp/org-clock.el (org-clock-sum): Rewrite regex using rx

Hello! See two attached patches. All tests pass on my computer. Every once in a while I feel obligated to go back to org-clock-sum to try and optimize it. I have a file with 8 clocktables in it and it takes forever to update. This time I decided instead of trying to optimize, I'm just going

Re: [BUG] Customizing org-emphasis-alist does not work as expected [9.6.15 (release_9.6.15 @ d:/emacs_home/program/emacs/share/emacs/29.2/lisp/org/)]

On 10/04/2024 15:19, Ihor Radchenko wrote: Chang Xiaoduan writes: I am trying to customizing `org-emphasis-alist` so that ` can replace ~ as the code marker. I use the following code in my configuration file: Custom markup markers are not supported. This customization is only useful to

Re: [Q] startup hook: How do I detect if the current buffer has been opened programmatically?

On 09/04/2024 00:31, Rudi C wrote: I want to automatically preview all LaTeX fragments if the buffer was opened by the user Be careful and limit automatic preview to files you created yourself. Doing so for an arbitrary file downloaded from net might cause huge amount of garbage files in

[no subject]

Sébastien Gendre writes: > When I try to execute a block of PlantUML in an Org document, I get an > error message: > > "org-babel-execute-src-block: No org-babel-execute function for plantuml!" > ... > (add-to-list > 'org-babel-load-languages > '(plantuml . t)) Just use (require

Re: none

On Thursday, 11 Apr 2024 at 16:43, Sébastien Gendre wrote: > When I try to execute a block of PlantUML in an Org document, I get an > error message: > [...] > (setq plantuml-default-exec-mode 'executable) > (setq org-plantuml-exec-mode 'plantuml) I don't have either of these setq lines but I do

[no subject]

Hello, When I try to execute a block of PlantUML in an Org document, I get an error message: "org-babel-execute-src-block: No org-babel-execute function for plantuml!" I have configured Org mode to enable execution of plantUML source block by adding this in my init.el: (setq

Re: org-clone-subtree-with-time-shift with reverse order

Christian Barthel writes: > I'd like to suggest adding a new prefix arg i.e. > `C-u C-u org-clone-subtree-with-item-shift' to reverse > the order of newly created / cloned siblings. Would > that be of interest for other orgmode users? May you explain your use case a bit more? -- Ihor

Re: [FR] :noweb-wrap header arg

Amy Grinn writes: > First of all, I would like to change (defalias) the function name > org-babel-noweb-wrap to org-babel-noweb-make-regexp. I think this in > more in line with other functions which create regular expressions. +1 You may even use obsolete alias (add it to lisp/org-compat.el) >

Re: Experimental public branch for inline special blocks

Ihor Radchenko writes: > Juan Manuel Macías writes: > >> The latest added to the branch are Maxim's proposals (and code) for >> backend control. See this thread: >> >> https://list.orgmode.org/?t=20240321102752 >> >> And this other thread, continuation of the previous one: >> >>

Re: columnview dynamic block - different time summing behaviour for EFFORT and CLOCKSUM

Alexander Adolf writes: > it seems that the time summing behaviour of columnview dynamic blocks is > different for CLOCKSUM than for EFFORT columns with respect to how the > contributions from sub-headlines are handled. When summing up CLOCKSUM > columns, a parent headline can have its own

Re: [PATCH] lisp/org-element.el: Add repeater-deadline support to org-element

Morgan Smith writes: > See two patches attached again. All tests pass on my computer. Thanks! Applied, onto main, with amendments (see the attached diffs). https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=66e307b41 https://git.sr.ht/~bzg/worg/commit/f1486f42 diff --git

Re: Verbatim content (inline-special-block)

Max Nikulin writes: >> - We should be able to define special markup for code, where the >> contents is not parsed. Something like >> >> @code{ unlike =code=, we can have leading and trailing spaces } >> @code{ @foo{is not interpreted inside}} > > I think, it should be

Re: Experimental public branch for inline special blocks

Juan Manuel Macías writes: > The latest added to the branch are Maxim's proposals (and code) for > backend control. See this thread: > > https://list.orgmode.org/?t=20240321102752 > > And this other thread, continuation of the previous one: > >

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

Bruno Barbier writes: >> I have a further request on interaction with penreg objects. >> I feel that it is not ideal that overlays associated with penreg objects >> cannot be fully controlled by the callers. > > I'm trying to limit the public API surface. I don't think we should > leak that we

Link to the repository (Re: inline-special-block: part2)

On 11/04/2024 17:49, Max Nikulin wrote: I think, it is better to create a new thread to discuss next bunch of questions related to the inline special block feature. I have realized that I forgot to add the link for those who wish to try the new feature in action: Juan Manuel Macías.

Re: Experimental public branch for inline special blocks

On 02/03/2024 03:34, Juan Manuel Macías wrote: Finally, I have made public on GitLab my experimental branch for the new (possible) inline-special-block element: Next part of this thread: Max Nikulin. inline-special-block: part2. Thu, 11 Apr 2024

Verbatim content (inline-special-block)

Ihor Radchenko. Re: Experimental public branch for inline special blocks. Tue, 09 Apr 2024 08:52:38 +. https://list.orgmode.org/875xwqj4tl.fsf@localhost - We should be able to define special markup for code, where the contents is not parsed. Something like @code{ unlike

inline-special-block: part2

I think, it is better to create a new thread to discuss next bunch of questions related to the inline special block feature. Previous thread is rather huge: Juan Manuel Macías. Experimental public branch for inline special blocks. Fri, 01 Mar 2024 20:34:35 +.

Re: [DISCUSSION] "quick-help" popup for org-columns (column view)

Philip Kaludercic writes: > I tried out using your `org-columns-help-quick-sections' variable, but > it seems that `where-is' didn't find all the commands you wanted: > Are commands like `org-columns-move-up' part of the next release of Org? > I am using whatever is currently on master. Yes

Re: Update contact info

Ihor Radchenko writes: > Bastien, may you check which name is used in the FSF records? I've taken this offlist. -- Bastien Guerry

Re: [DISCUSSION] "quick-help" popup for org-columns (column view)

Philip Kaludercic writes: > Sławomir Grochowski writes: > >> Thank you Philip for the explanation and preparing the code snippet. >> >> So what are the next steps? >> Can you merge your patch? > > If this is everything, I can push the change. But I'll test it first. I tried out using your

Re: [DISCUSSION] "quick-help" popup for org-columns (column view)

Sławomir Grochowski writes: > Thank you Philip for the explanation and preparing the code snippet. > > So what are the next steps? > Can you merge your patch? If this is everything, I can push the change. But I'll test it first. -- Philip Kaludercic on peregrine