Re: Feedback on the new "feature" system in org-export (was: [Pre-PATCH] Overhaul of the LaTeX preview system)

Karthik Chikmagalur writes: > I have a question about addressing byte-compile warnings, explained via > example: > > 1. In the preview branch, org-create-formula-image has been moved to > org-compat.el since it is obsolete. > 2. This function uses org--get-display-dpi, which has also been made >

Re: Feedback on the new "feature" system in org-export (was: [Pre-PATCH] Overhaul of the LaTeX preview system)

>> I would like to submit the org-latex-preview patchset for review and >> merging now. I will be losing my FSF copyright assignment soon, so I'm >> hoping to see it merged before then even if there are some minor issues >> remaining to be addressed. > > Sure. Let's get started. I have a question

Re: [PATCH] org-element.el; significant optimizations for org-element--interpret-affiliated-keywords

> Please use double space between sentences and `quote' like this, not > `like this`. See https://orgmode.org/worg/org-contribute.html#commit-messages fixed >> Second, the loop was much more complex than needed. The loop included >> :standard-properties which should not be necessary here. It als

Re: [BUG] Unable to use dvisvgm to preview LaTeX fragments when using dark theme

> I would say that changing the default :background to transparent is > justified, but such a change would only go on main branch, just to be > immediately canceled by the new preview system. So, I'd rather wait > until we merge the preview branch. > > Also, Karthink, may you please point me to the

Re: Improve documentation of org-reverse-note-order

>>> I think we can leave these methods untouched for compatibility but >>> introduce some consistent aliases? >>> >>> | Action | How to reverse filing order | >>> |-+---| >>> | Refile | Introduce org-refile-prepend | >>> | Capture | Introduce org-capture-pre

Re: ob-octave: improve MATLAB support

Hi I’ve been so busy with work. The last round of feedback was to split matlab support from octave, which I started but didn’t get very far. I’ll try to get back to this soon. Sorry for the delay, John On Tue, Apr 22, 2025 at 1:17 PM Ihor Radchenko wrote: > Ihor Radchenko writes: > > > Maybe

Re: Fwd: [PATCH]: Add font specifications when exporting to LaTeX

Answers inlne On Tue, 22 Apr 2025 at 18:55, Max Nikulin wrote: > On 21/04/2025 18:07, Pedro Andres Aranda Gutierrez wrote: > > I could try to go for something like: > > > > (defvar org-latex-font-fallback-alist > >'(("main . '(("emoji" . "Noto Color Emoji:mode-harf") > > ("ha

Re: [PATCH] Re: Better support optional weekday in Org mode timestamps

Jens Schmidt writes: > [ Readding tomás since this thread got more high-level again ... ] > > On 2025-04-20 13:27, Ihor Radchenko wrote: > >> Looks reasonable. > > Thanks. More or less by chance I let Org's ERT tests run with > `org-timestamp-formats' set to `("%Y-%m-%d" . "%Y-%m-%d %H:%M")'. >

Re: org-publish-cache-get-file-property errors out

reza writes: > Hello Orgers > > I am not sure if it is a bug, but when I call > > (org-publish-find-title "/absolute/path/to/org/file.org" '("")) > ... > in the funtion org-publish-cache-get-file-property where > org-publish-transient-cache is initialized with nil. It is a documentation bug. `

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

Rudolf Adamkovič writes: > I am currently super-duper busy with uni assignments. > ... Then, take your time. > ... Basically, we want the > `graphviz-dot-mode' to be enabled when editing GraphViz Dot code blocks, > while also retaining DWIM executing via Org Babel. If I understand your > advic

Re: [DISCUSSION] Contributing policy for WORG

Bastien Guerry writes: > "Taking care of Worg" means making this community-driven documentation > useful to as many users as possible. > > Maybe it means ... > > I suggest a call for volunteer, I can help drafting the call if needed. That would be welcome. You probably have a more clear picture

Re: Q: org-export-headline-levels doc problem?

Ihor Radchenko writes: > David Masterson writes: > >> Also, I note the use of 'top level' in "2.1 Headlines" and would >> probably replace it with 'first level' to keep with the numbering >> scheme. > > I'd use "Top level (level 1)" because many docstrings use "top level" > terminology. Okay, I

Re: ob-octave: improve MATLAB support

Ihor Radchenko writes: > Maybe you can use `org-require-package'. > ... John, it has been a while since the last update in this thread. May I know if you had a chance to look into my latest comments? -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at

Re: [PATCH] lisp/ox-html.el: Add file level option to manage headlines self link

Sébastien Gendre writes: > I plan to work on the other OPTION/KEYWORD in the next days. > > Do you prefer if I make 1 commit for each of them or 1 for all ? > If I made 1 for each, do I send all of them in 1 e-mail ? I suspect that the changes will be very repetitive. If yes, it will make more s

Re: Q: org-export-headline-levels doc problem?

David Masterson writes: >> ** Is a top level headline when there are no other parent >> headlines > > Whoa. Not said in 2.1. Hmm. I was actually wrong. I think, most of the manual and code refer to top level strictly as to "level 1". > Also, I note the use of 'top level' in "2.1 Headlines"

Re: Fwd: [PATCH]: Add font specifications when exporting to LaTeX

On 21/04/2025 18:07, Pedro Andres Aranda Gutierrez wrote: I could try to go for something like: (defvar org-latex-font-fallback-alist   '(("main . '(("emoji" . "Noto Color Emoji:mode-harf")                ("han"   . "Noto CJK JP:")                ("kana"  . "Noto CJK JP:")))     ("sans". '((

Re: Q: org-export-headline-levels doc problem?

Ihor Radchenko writes: > David Masterson writes: > >> Also, I note the use of 'top level' in "2.1 Headlines" and would >> probably replace it with 'first level' to keep with the numbering >> scheme. > > No, because > > ** Is a top level headline when there are no other parent > headlines Wh

Re: [PATCH] org-clock: insert lexical binding cookie into persisted files

>> Applied, onto bugfix. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix&id=a6bba4832f538a3223a4c8905a9e55be351846ca > > When will this be merged into the Emacs master branch please? When the volunteer who is synchronizing Org with Emacs master gets free time to do it. W

[BLOG] #17 [[bbb:OrgMeetup]] on Wed, Apr 9, 19:00 UTC+3

Dear all, Here are the meeting notes. TL;DR: timezone support; search support in HTML export; proposal to switch to lualatex as default pdf export engine; exporting non-latin documents to pdf without config headache; nested special blocks; parser-based fontification; elisp inspector; inline speci

Re: [PATCH] org-clock: insert lexical binding cookie into persisted files

On Sun, Apr 13 2025, Ihor Radchenko wrote: > Applied, onto bugfix. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix&id=a6bba4832f538a3223a4c8905a9e55be351846ca Hi, When will this be merged into the Emacs master branch please? TIA, -- Peter

Re: Text editing is very slow when org-highlight-latex-and-related is (latex)

I understand that the regular expressions for LaTeX are too complicated, which makes the search slow, and that there are cases where it does not match LaTeX formulas properly when the BOUND argument is specified. While the slow search due to the complexity of regular expressions is a problem, I a

Re: [PATCH] lisp/ox-html.el: Add file level option to manage headlines self link

I plan to work on the other OPTION/KEYWORD in the next days. Do you prefer if I make 1 commit for each of them or 1 for all ? If I made 1 for each, do I send all of them in 1 e-mail ? Best regards --- Gendre Sébastien Ihor Radchenko writes: > Sébastien Gendre writes: > >> I have attac

An error with org-export-to-file 'odt

Hi, Org-export-to-file with the odt backend gives an error when invoked directly (void-variable hfy-user-sheet-assoc). Tested on Org 9.7.28. To reproduce, save a minimal Org file and, from that buffer, evaluate : (org-export-to-file 'odt "testfile.odt") I'm not sure if this is *expected* to work