Re: [BUG?] in pcomplete???

[PATCH]: add #+latex... and #+beamer... Just in case, I'm adding a small patch to add the missing keywords I miss when editing org to export to latex and beamer. Best, /PA On Sat, 5 Apr 2025 at 07:35, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Hi, > > when working on the font s

Re: Search tools for Org (Re: Graph of writing)

In addition to the various search packages suggested by others upthread, there are also the built-in org-agenda tools, `M-x org-agenda' (or C-c a with the suggested global keybinding) followed by either `/' (org-occur-in-agenda-files) - the search term is a regular expression, the view is a c

Re: Re

Hi, answers inline... On Mon, 31 Mar 2025 at 19:12, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > Hmmm... > > I'd have to sleep over it. This is more a "user taste" issue IMvvHO. > > > > I have a snippet for that including: > > #+LATEX_HEADER: \setmainfont{FreeSerif} > > #

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

Thanks for the feedback. I’d be interested in seeing what happened. Could you please send me the offending file? It can be of help when determining What we need on org-mode. BTW, do you have any org file that you export to PDF where you could export using #+LATEX_COMPILER: lualatex And see what

Re: [DISCUSSION] Automatically setting unicode fonts in latex export

Answer inline On Wed, 2 Apr 2025 at 20:20, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > Actually, what I would do after looking around is > > * short term (even as a bug fix in 9.7): modifying the error message and > > say that unsupported Unicode characters can only be d

Re: Feature discussion: Search field and local search engine

Hi, It has been a while since the last message in this thread. May I know if you need any help? -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at

Re: [PATCH v2] ox-texinfo: Preserve source block language fields during export

Richard Sent writes: > I added org-texinfo-listings-langs. I'm not super familiar with the Org > codebase so I might've missed something, but as far as I can tell it's > functionally correct. In the case of `org-latex-listings-langs', the word "listings" refers to the LaTeX package with the same

[PATCH] Capitalize JavaScript correctly

* doc/org-manual.org (Exporting to minimal HTML): * etc/ORG-NEWS (Add ~:session~ support of ob-js for js-comint): * lisp/ob-js.el (org-babel-js-function-wrapper): (org-babel-execute:js): (org-babel-variable-assignments:js): (org-babel-js-initiate-session): * lisp/ox-html.el (org-html-style-default)

Re: [PATCH] Preview LaTeX recursively

Rudolf Adamkovič writes: > Ihor Radchenko writes: > >> This will be a breaking change that will surprise users familiar with >> current behavior of image previews and latex previews. > > But will it be a pleasant surprise? :) Or not, when the number of previews is huge. I'd rather be conservati

Re: org-persist-write:index takes minutes to run

>I feel that it is too long and weird, so I restart my Emacs daemon, and the >results do not change. Just moments ago, I test it in other way. I stay the buffer view in the end of my org file, where there are many fragments. When I execute (my-org-latex-preview-benchmark), it only takes 0.5s-1s,

Re: Inline previewing of .rnote files

Hello, I'm aware of this new enhancement and am eager to see this released, however i think this does not fit well my use case as it requires defining a new link type whereas link types' semantic is - in my view - that of defining a type of URI, not the type of identified element. An .rnote fi

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

Pedro Andres Aranda Gutierrez writes: BTW, what about changing the default LaTeX compiler to lualatex in 9.8? Context: I am a user that knows very very little about Latex, everytime I try to use it I spend a lot of time installing packages that in my mind should be the default. The user expe

[SOLVED] Re: [PATCH] The function `org-link-preview-region` should detect whether already has overlay.

Karthik, thanks, I disabled org-link-beautify-mode, then re-verify your patch, confirmed it works as expected. Then I will fix org-link-beautify preview logic. Thanks for your reviewing my package code to find out reason. I forget to notice message body after applied mail patch. my fault. Ihor, th

org-element is stymied by non-nil field properties

I've been using org-element to identify blocks in org buffers[1]. It's working great in both before & after change functions. It can readily identify newly formed blocks as well as blocks which get "damaged" (header/footer edited). So much better than scanning the buffer yourself, especially

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

> Do you have any ideas about how we could improve the handling of utf-8 > without sacrificing the speed of the preview system? I'm afraid this is beyond my understanding. We'd have to approach David Carlisle or others with the problem and work on improving mylatexformat, or help develop a new in

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

Colin Baxter writes: > I have my org-latex-compiler set to xetex. However, I find this push to > change the default bizarre, especially since advanced users can select > their own settings at will. In my opinion a default ought to be the > "simplest" option and unchanged. Those who want something

Re: Generating the filename from name and file-ext for blocks with side-effects

Ihor Radchenko writes: > Rudolf Adamkovič writes: > (image-type "...-59b9176e65c9.svg") => svg >>> >>> Why do you think that the output file is always an image? It may not >>> be. It can be anything. >> >> I do not think that. I specifically addressed the non-image case: the >> file woul

Re: [SOLVED] Re: [PATCH] The function `org-link-preview-region` should detect whether already has overlay.

stardiviner writes: > Karthik, thanks, I disabled org-link-beautify-mode, then re-verify your > patch, confirmed it works as expected. > Then I will fix org-link-beautify preview logic. Thanks for your reviewing > my package code to find out reason. > I forget to notice message body after applied

Re: [FR] org-babel-n-tangle

Lei Zhe writes: >>> you can simply return multiple (file-name src-lang start-line file link >>> source-name params body comment) items. >>> (file-name1 ... link1 ...) >>> (file-name2 ... link2 ...) > > I don't get it, shouldn't it be as shown below? Then the returned > results got changed. > ((f

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

On Wed, Apr 02 2025, "Rohit Patnaik" wrote: > I'm against moving to `luatex' as the default compiler. I'm decently familiar > with LaTeX, having used it to write papers and even my resume. I just tried > to compile a relatively simple LaTeX file using `luatex' on my Fedora Linux > machine with

Re: File mode specification fails when org-startup-shrink-all-tables is t and file contains table.el tables

libreville writes: > this looks like it might be a bug. > > As the subject line says, set-auto-mode fails when > org-startup-shrink-all-tables is t and file contains table.el tables. > > If my org file has a table.el table in it, like this > > +--+ > | | > +--+ > > then on finding the file I see

Re: Use of #+include: inside list with breaking change?

Jens Lechtenboerger writes: > I want to use the keyword #+include: inside lists to embed source > code for HTML export (`C-c C-e h h'), like so: > > * foo > - A list > #+include: bar.txt src text > > Previously, that worked. On Org main, the list now gets closed > before the source code contai

Re: [DISCUSSION] Setting LuaLaTeX as default when exporting to LaTeX/PDF

> Ihor Radchenko writes: > Karthik Chikmagalur writes: >> For org-latex-preview, one of the other things we tried was to >> keep all utf-8 font-related settings out of the header that is >> precompiled. If we manage this precompilation can work (somewhat >> unreliably) w

Re: Image inlining patch

Hi, after giving ox-html a second (and a third read), there are too many dependencies to make a clean move a simple task. It will take me more time than I have right now. So why not fixing the bug now and doing the factoring out later? Best, /PA On Fri, 28 Mar 2025 at 19:31, Ihor Radchenko wrot

Re: inconsistency for the affiliated keyword of a dynamic block

On 2025-03-27 17:13, pinmacs wrote: Maybe we can use similar idea and allow users to list the affiliated keywords (or regexps matching the keyword names) to keep. Then, after updating the dynamic block, if some affiliated keywords have been removed, they are re-added. WDYT? 3/5 I think that's bet

Re: Optional weekday in Org mode timestamps

On Fri, Mar 21, 2025 at 10:42:54PM +0100, Jens Schmidt wrote: > [Moving to emacs-orgmode - I hope it is OK to keep tomás on CC.] > > Hi Ihor, > > the following statement of yours on emacs-devel caught my eye: > > On 2025-03-03 19:31, Ihor Radchenko wrote: > > > FYI, weekday is optional. It als

Re: [BUG] Org-babel inline overwriting src block outputs when using async + session

Ihor Radchenko writes: > 1. Probably better make it internal function for more flexibility in >future > 2. You need to consult `org-element-context' to make sure that we are >really at inline src block, but not inside some kind of verbatim >markup. > 3. Rather than copying regexps aro

Re: `org-indent-line' docstring is inaccurate for org-src-tab-acts-natively = nil (was: [BUG] Unintuitive indentation behavior when editing org-src blocks)

> According to > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f58201b1e1b0788098b1bbca45e06e015f5b0b7b > the current behavior is intentional. So, I believe that the bug is in > the docstring that has not been updated in that commit. That would explain it. > Note that indentin