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

Max Nikulin writes: >> \directlua{ >> luaotfload.add_fallback("global_fallback", { >> "Noto Serif:mode=harf;", % 1st: Broad Unicode coverage >> "DejaVu Serif:mode=harf;", % 2nd: Common Linux/Windows font >> "FreeSerif:mode=harf;",% 3rd: Common TeX Live font >>

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

l...@phdk.org writes: >> 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 expla

Re: org-indent-line on the first line of src blocks when org-edit-src-content-indentation is non-zero (was: [BUG] Unintuitive indentation behavior when editing org-src blocks)

l...@phdk.org writes: >> 1. Rename org-edit-src-content-indentation to >>    org-src-content-indentation and update the docstring >>    clarifying that the variable affects inedntation, editing, and >>    printing the AST. >>  >> 2. Update `org--get-expected-indentation' to treat blank lines at th

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

Pedro Andres Aranda Gutierrez writes: > New version of the patch (will test your suggestions right after this) Thanks! > +*** New class options keyword for exporting to Beamer > + > +When exporting to beamer, =#+BEAMER_CLASS_OPTIONS:= should be used > +instead of =#+LATEX_CLASS_OPTIONS:=. If yo

Re: [BUG] C-c C-c doesn't update checkbox after making ready-only file read-write [9.7.11 (release_9.7.11 @ /usr/new/share/emacs/31.0.50/lisp/org/)]

Ihor Radchenko wrote: > May you try the attached patch? Will do, though it might be a few days before I can get to it. Thanks! mike

Re: Fontification errors with recent Emacs updates?

William Denton writes: > I freshened up the Emacs and Org source trees tonight and made everything > fresh, and it broke my Org documents. I was getting lots of fontification > errors, and source blocks were showing as normal text. I did a "git checkout > HEAD~25 ; make" on the Emacs source

Re: "Tab width in Org files must be 8, not 2. Please adjust your ‘tab-width’ settings for Org mode"

Jorge Cuellar writes: > I have updated emacs to the latest version: > GNU Emacs 30.1 (build 2, x86_64-w64-mingw32) of 2025-02-23 > and org too: > Org mode version 9.7.27 > > Customization says: > Operate on all settings in this buffer: > Hide Tab Width: Integer: 8 > State : SAVED and set. > >

Re: Feature discussion: Search field and local search engine

Ihor Radchenko writes: > It may be something users want to choose (user option). It could be an option. I think a large portion of code made for one option could be done for the other option. So, I can start with the search on each page and then, in the future, add search on a dedicated page.

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

Arsen Arsenović writes: > * lisp/org/org-clock.el (org-clock-save): Insert a lexical-binding > cookie into org-clock-persist files. > --- > Emacs recently started warning about loading files without a lexical-binding > cookie. This was getting triggered on my org-clock persistence file. This >

Re: [RFC] Insert reference to Org table cell or cell range from region selection (w/without mouse)

Ihor Radchenko writes: > Ihor Radchenko writes: > >> Charles Choi writes: >> ... > > Charles, any update on this? Looks like there is no interest. Canceled. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at

Re: Sorting a TODO agenda across multiple files

Kuba Orlik writes: > It turns out that the timestamp-down sorting function ignores the > hours/minutes in the timestamp and only looks at the date. > > It took me a lot of time to figure that out! Do you think it'd be good > to add this information to the documentation? Currently docs for > ts

Re: Optional weekday in Org mode timestamps

Jens Schmidt writes: >> FYI, weekday is optional. It also adapts to the language settings. > > What exactly do you mean by "optional" here? It means that you can type in [2025-04-13] or [2025-04-13 8:24] and they will be valid timestamps recognized by Org mode. > - Do you mean one can configure

Re: [PATCH] Capitalize JavaScript correctly

Max Nikulin writes: > On 21/03/2025 20:54, Rudolf Adamkovič wrote: >> Re-capitalize "Javascript" to JavaScript. > > Are there potential legal issues with the registered trademark owned by > Oracle? E.g. organizers of JSConf avoid "JavaScript" in the conference title > https://www.trevorlasn.com/

Re: whether org-mode should ignore links in properties drawer?

stardiviner writes: > I use org-mode to manage bookmarks, contacts, and ebook library etc. So > offten insert URL or other > link types as property value in the properties drawer. > ... > The commands like ~org-next-link~ etc will ignore links in properties > drawer. I think links in > properties

Re: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark?

Hi again! I have been making slow progress, but also run into problems with arbitrary argument lists for the menus - making the !citation and !prefix things customizable. There is clearly something about elisp evaluation that I don't understand. I have problems in two places: The first is in set

Seconds in timestamps (was: time formats in org-timestamp-formats)

Yue Yi writes: > I'm currently working on a modified HTML export backend and noticed that > `org-timestamp-formats` is a constant that defines two timestamp > formats—one without time and one with time (but only up to minutes): > ... > I plan to add seconds support in my backend, but I see that f

Re: Borrowing the syntax highlighter from an a other mode

Phil Estival writes: > I've been working with SQL Procedural Languages lately and I would like > to known if it's possible to distinguish, inside of source blocks, the > syntax coloring from the interpreter the source is to be run with. > > For instance, pl/python is run in sql-mode, what it is,

Re: Seconds in timestamps (was: time formats in org-timestamp-formats)

Ihor Radchenko 2025.04.14 01:07 writes: > > Parsing these timestamps manually isn’t a big deal, but I’m > > curious — has there ever been discussion about extending this to a > > triplet structure (date, date+time, date+time+seconds) for more > > flexibility? > > I do not recall any requests about

Re: Parsing of incomplete LaTeX environments

Karthik Chikmagalur writes: > If I delete the last line, so it looks like > > \begin{align} > x = 1 > > And now place the cursor anywhere on the first line (with the \begin...) > and call (org-element-context), it parses it as a `latex-fragment'. > > This make sense too, since any text of the for

Re: Fold persistence for org and others

Jacob Fong writes: > Hello friends. I've created a small package that persists folds made > by a number of different modes, including org-mode. It supports > overlay-based folding as well as the newer text prop style. It may be > of interest here. > > https://github.com/jcfk/savefold.el Thanks f

Re: Question about getting properties of org entry

Doerthous writes: > Ihor Radchenko writes: >> May you show profiler report detailing what exactly is slow? >> You can save the profile with M-x profiler-report-write-profile from the >> report buffer. > > Hi Ihor, > > Sorry for the late reply. > > I actually done a performance test that day with

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

Leo Butler writes: >> I am wondering if the current design with many previews generated using >> the same latex process can be extended. May we somehow add a Lua code to >> preview.sty that will not exit at all and watch for new .tex fragments >> to appear and preview them. The idea is to avoid s

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

Pedro Andres Aranda Gutierrez writes: > Thanks a lot. Really cool. My only concern is that it means adding a > non-standard package to the TeX. > I had no problems, but some people may struggle with the instructions ;-) It would be a nice article on WORG I think. We cannot use custom tex packag

Re: [PATCH] lisp/org-collector.el: Add support for TBLFM

Charles Millar writes: > In response to his original proposal in 2021 I forwarded some of my > personal code for his consideration. see > > https://lists.gnu.org/archive/html/emacs-orgmode/2021-08/msg00431.html > > It not only added a #+TBLFM but also a table name, etc. > > My use case is I may

Re: [PATCH] Re: Q: Documentation question on beamer and org

David Masterson writes: >> Maybe we can just reference wiki + official manual. >> https://en.wikipedia.org/wiki/Beamer_(LaTeX) > > Actually, I think that would be good. I assume that the Beamer people > will update the the wiki page, so we don't have to update the Org manual > (provided Wikipedi

Re: whether org-mode should ignore links in properties drawer?

Ihor, thanks for your detailed answer. I checked the `org-next-link` function source code, don't know how to patch it. Is there other people want to contribute this patch? If no, this thread could be closed. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner

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

Max Nikulin writes: >>> P.S. In some cases it may be easier to get PDF from ODT or HTML >>> intermediate format. >> No please! I've gone that path and then you need to install loads of extra >> and sometimes redundant software to get something decent. > > I do not suggest to make it the default o

Re: org-latex-preview and font-locking

Leo Butler writes: > Q: Why does `org-latex-preview' not work on blocks like: > > #+begin_export latex > \begin{equation} > x^2 + y^2 = z^2 > \end{equation} > #+end_export > > I use these blocks to take advantage of syntax highlighting (and it is > quicker to write than not including the export b

Re: Language support for C# in org-babel

Someone™ should do it and produce patches ;) I will raise my hand once the discussion proceeded in such a direction 🙂 Nitpick: readme still mentions them. I did not yet adapt this with the last iteration as I wanted the code to be somewhat "stable" first. It is updated now and should reflect

lex-bind frenzy

HI, Just an insignificance, caused by lexical binding hysteria in master: diff --git a/mk/org-fixup.el b/mk/org-fixup.el index efb9fb299..451da335b 100644 --- a/mk/org-fixup.el +++ b/mk/org-fixup.el @@ -1,4 +1,4 @@ -;;; org-fixup.el --- make life easier for folks without GNU make +;;; org-fixup.e

A micro-addition to the manual

HI, I often refer people to the reference added by this micro patch. diff --git a/doc/org-manual.org b/doc/org-manual.org index 360260149..8a345ce79 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -13027,6 +13027,7 @@ popular display formats. We strongly recommend familiarizing yours

Re: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark?

I just found intern. The problem was using make-symbol, which makes an uninterned symbol. I'll polish the patch a bit and get back, sorry for using the list as a rubber duck... Cheers, /Torbjörn Den sön 13 apr. 2025 20.00Tor-björn Claesson skrev: > Hi again! > > I have been making slow progres

Re: org-get-x-clipboard code may be outdated

Max Nikulin writes: > Notice that code of `gui--selection-value-internal' and > `org-get-x-clipboard' uses different set of targets and `window-system' > variants. I have no idea if it affects many users. I am in doubts if > there ones running haiku or using SECONDARY selection. However some m

Re: Field constraints?

Daniel Colascione writes: > Might it be possible to have the C-a and C-e commands obey Emacs fields using > constrain-to-field? Fields are useful when using gptel in org-mode to > separate LLMs prompts from their responses. Sure, why not. We generally aim to support standard Emacs features whe

Re: org-latex-preview and font-locking

>> Q: Why does `org-latex-preview' not work on blocks like: >> >> #+begin_export latex >> \begin{equation} >> x^2 + y^2 = z^2 >> \end{equation} >> #+end_export >> >> I use these blocks to take advantage of syntax highlighting (and it is >> quicker to write than not including the export block around

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

PS: Free* means the Free* _fonts_ On Sun, 13 Apr 2025 at 10:49, Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > A bit more info > > With lualatex, I get > > luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File > not found: > "/usr/lib/firefox/fonts/TwemojiMozilla.tt

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

A bit more info With lualatex, I get luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File not found: "/usr/lib/firefox/fonts/TwemojiMozilla.ttf"texmf-dist/tex/luatex/luaotfload/luaotfload-fallback.lua:50: attempt to inde x a nil value (local 'f'). relax l.19 ... Serif}[Raw

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

Lei Zhe writes: >> I'd rather avoid such non-deterministic return value. >> Having different return values depending on the :tangle parameter is, >> IMHO, not the best design. I'd rather go with my idea of adding a new >> optional argument that will turn on the new return value convention and >>

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

"Dwarshuis, Nathan J" writes: > Sorry, I'm apparently not used to reading issue threads outside of Github. I > read too fast and missed everything after this. You may refer to https://orgmode.org/worg/org-contribute.html and https://orgmode.org/worg/org-mailing-list.html for our conventions. T

Re: Feature discussion: Search field and local search engine

Hello, Thank you for your replies and your time. So, I go with solution number 1: * A HTML search engine is defined with a function, in a similar way to what we have with export backend definition. * To enable the search engine in an Org publication to HTML pages, a user only have to set th

Re: [BUG?] in pcomplete???

Pedro Andres Aranda Gutierrez writes: > An alternative is to advise the user who uses org as a high-level > alternative for LaTeX to include > (require 'ox-latex) > in the init.el file if (s)he uses an autocompletion framework. > > Maybe it might be worth adding a word in the manual. WDYT? Hmm.

Re: Feature discussion: Search field and local search engine

Yes, you are right. Maintaining a JS on org-mode could be a bad idea. My main concerns with this third solution was more about: * What if we also add a search capability in Org-mode and not only in HTML exported pages ? * Do we have a search on the whole site directly from each page, or on a

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

New version of the patch (will test your suggestions right after this) Best, /PA On Sat, 12 Apr 2025 at 19:50, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > > > A new version of the patch, including a test for the new > > #+BEAMER_CLASS_OPTIONS > > Thanks! > I have no objecti

Re: Feature discussion: Search field and local search engine

Sébastien Gendre writes: > My main concerns with this third solution was more about: > > * What if we also add a search capability in Org-mode and not only in > HTML exported pages ? org-ql does it. So, there is already search capability in Org-mode. Moreover, org-agenda does it. And columnvie

Re: [BUG?] in pcomplete???

Hi With you patch in org.mode, remove the (require ox-latex). Then I reopen Emacs and go to the scratch buffer: (require 'org) org org-export-backends (ascii html icalendar latex odt) Then I open an org document which I intend to export to LATEX and try to autocomplete #+LAT but get no completi

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

Hi Ihor, thanks for the review. > In org-babel-tangle-collect-blocks: > ob-tangle.el:494:10: Warning: Unused lexical variable ‘buffer-fn’ > In org-babel-tangle--concat-targets: > ob-tangle.el:572:6: Warning: value from call to ‘remove’ is unused Fixed, thanks for pointing those out. > Please add

Re: [BUG] C-c C-c doesn't update checkbox after making ready-only file read-write [9.7.11 (release_9.7.11 @ /usr/new/share/emacs/31.0.50/lisp/org/)]

Mike Kupfer writes: > But I can still reproduce the problem, by using a slightly different > recipe than the original one. > ... > #rm -rf ~/.cache/org-persist > ... > But, if I uncomment the 'rm' command in the test script and then try to > reproduce the problem using the modified recipe, I cann