Re: Help request ... was Re: [PATCH]: Add font specifications when exporting to LaTeX

Hi Calling out to the list to see if someone can help more scripts integrate and show. I have currently running the Latin-x, Greek, Cyrillics, some UTF-8 (see my original file in this thread) and Emoticons. The file attached by Ihor is actually and org file and not a tex file ;-). > El 14 abr

Re: [PATCH]: add BEAMER_CLASS_OPTIONS

Pedro Andres Aranda Gutierrez writes: > I have a couple of lectures and I was looking (once again) at the way to > intersperse them with text to create a small volume of lecture notes. > So I was trying to get the LaTeX part correctly and I found that the latex > class options needed to be differ

Re: org-latex-preview and font-locking

> Due to various conveniences, it means typing about 2/3 less. Consider > > C-c C-, l ;; insert a latex export block > C-c C-' ;; open an editing buffer > C-c C-e ;; select an environment > al TAB * RET > > versus > > \begin{align*};; insert literal text > > \end{align*} ;;

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

On Sun, Apr 13 2025, Max Nikulin wrote: > On 12/04/2025 21:11, Leo Butler wrote: >> I use a lot of >> utf-8 in my org documents. Pdflatex just cannot compete for typesetting, >> even in preview. > > Certainly PdfTeX has enough limitations. I am curious however what > specific issues you have face

Re: [BUG] Replace a string while narrowing is active => Error. [9.7.20 (N/A @ /gnu/store/nbqz4xh45yvlpw9dqqfpxp82v0f82vk4-emacs-org-9.7.20/share/emacs/site-lisp/org-9.7.20/)]

Ihor Radchenko writes: >> Thanks for reporting! >> May I know if you observe this problem frequently? >> >> quite often, yes > > As the first step to investigate, please enable backtraces on error via > M-x toggle-debug-on-error. > > Then, next time you encounter the problem, Emacs will stop a

Re: Parsing of incomplete LaTeX environments

On Sun, Apr 13 2025, Ihor Radchenko wrote: > 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-fragme

RE: [BUG] Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer # (org-agenda-mode) [9.7.11 (release_9.7.11 @ /Applications/Emacs.app/Contents/Resources/l

FYI I still get this "cannot be used in a non-Org buffer" error displayed whenever a new release of Org comes out. Then I have to "fix" it by swapping display-warning with message in org-element.el l.8477. I'm willing to try to help track down the code that's calling org-element-at-point incor

Re: [BUG] Org report [9.7.19 (9.7.19-??-5a4686915 @ /Users/butlerlocal/.emacs.d/.local/straight/build-29.4/org/)]

"Butler,Kevin" writes: > Apologies. I haven’t seen any recent errors so I assume there was a fix in > some intermediate component that has prevented the hanging. Thanks for the update! Feel free to follow up if the problem re-surfaces. Meanwhile, fingers crossed. -- Ihor Radchenko // yantar92

Re: [BUG] Org report [9.7.19 (9.7.19-??-5a4686915 @ /Users/butlerlocal/.emacs.d/.local/straight/build-29.4/org/)]

Apologies. I haven’t seen any recent errors so I assume there was a fix in some intermediate component that has prevented the hanging. Regards, Kevin From: Ihor Radchenko Date: Monday, April 14, 2025 at 2:41 PM To: Butler,Kevin Cc: emacs-orgmode@gnu.org Subject: Re: [BUG] Org report [9.7.19 (

Re: lex-bind frenzy

Pedro Andres Aranda Gutierrez writes: > 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

Re: [BUG] [9.7.22 (9.7.22-??-2f5add4 @ /home/kazure/.config/emacs/.local/straight/build-29.4/org/)]

Ihor Radchenko writes: > Do you see this frequently? > If yes, may you do M-x toggle-debug-on-error and report a full backtrace > next time you see the error? Since no extra information has been provided for over a month, this bug report is not actionable. Canceled. -- Ihor Radchenko // yantar

Re: [BUG] Org report [9.7.19 (9.7.19-??-5a4686915 @ /Users/butlerlocal/.emacs.d/.local/straight/build-29.4/org/)]

Ihor Radchenko writes: > May I know if you see the warnings regularly? If yes, may you do M-x > toggle-debug-on-error and share the backtrace next time the problem > triggers? M-x toggle-debug-on-error will make emacs stop and produce > backtrace window instead of displaying this warning. It has

Re: Bug Report: Invalid Function Error after Natively Compiling =org-element=

Ihor Radchenko writes: > Vitus Schäfftlein writes: > >> After updating to emacs version 30.1 from version 29.4.4, I experience >> issues with =org-element-with-disabled-cache=. Specifically, creating an >> =org-roam= node with a template that sets a =#+category= yields the error >> =invalid-f

Re: agenda-custom-commands: tags-todo resetting sorting-strategy?

Ihor Radchenko writes: > mailingli...@xgm.de writes: > >> I have noticed, that the sorting of custom agenda views, does not work >> as expected. >> >> (setq org-agenda-custom-commands >>'(("n" "Agenda and all TODOs" >> ((tags-todo "LAST_REVIEW<>{.+}") >>(alltodo)) >

Re: [BUG] Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer # (org-agenda-mode) [9.7.11 (release_9.7.11 @ /Applications/Emacs.app/Contents/Resources/l

Ihor Radchenko writes: > Ihor Radchenko writes: > >> There is a reason why I asked to debug display-warning rather than >> org-element-at-point itself. What you need to catch is what is calling >> org-element-at-point in inappropriate place. > > It has been a month. > May I know if you managed t

Re: A micro-addition to the manual

Pedro Andres Aranda Gutierrez writes: > I often refer people to the reference added by this micro patch. > > We strongly recommend familiarizing yourself with Beamer terminology > before reading the rest of this chapter. See > + or >

Semantic Linking saves tedious work

Semantic Linking saves tedious work Here is video how it works: https://www.youtube.com/watch?v=xk2VGnLYAkA No more tedious choosing of "files" and "headings", kill here, yank there, remember. Just mark the text, generate link on the semantics and point out to the next most relevant place. Tool

Re: Language support for C# in org-babel

poverobuosodonati writes: >> Next step will be writing tests. > > The project now contains the file test-ob-csharp.el [1] along with a > test org-file ob-csharp-test.org [2]. I tried to follow the examples of > the test files under /testing/lisp/ and /testing/examples /of the > org-mode reposi

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

Billy Lei writes: > When using themes with background color set to #00, and > org-preview-default-process is set to dvisvgm, the LaTeX fragments are > displayed incorrectly. > > To reduplicate: > > 1. Switch to a theme with background color set to #00 (like Modus > Vivendi) > 2. Create

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

stardiviner writes: > I checked the `org-next-link` function source code, don't know how to patch > it. You will need an additional check on CONTEXT value and consider it not just being a link, but also node-property. See how `org-open-at-point' handles the situation - it contains special handli

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

I’ve been playing with old-style search engine suggestions and the Noto fonts (which seem to be installed with TexLive) and have come up with a MWE with “challenging” UTF-8 and emojis… WDTY? Additional code to generate by org-mode is limited in size: —— cut here —— #+OPTIONS: num:nil toc:nil #+

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

Pedro Andres Aranda Gutierrez writes: > I’ve been playing with old-style search engine suggestions and the > Noto fonts (which seem to be installed with TexLive) and have come up > with a MWE with “challenging” UTF-8 and emojis… WDTY? Additional code > to generate by org-mode is limited in size:

Re: org-latex-preview and font-locking

On Sun, Apr 13 2025, Karthik Chikmagalur wrote: >>> 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 >>>

Re: Problem with finding css file with orgmode blogging setup

Hi Christian, Thanks for pointing that out! It was not super obvious (to me atleast) from Rohit's email but I see your point. Kind regards, Ashish On 4/12/25 19:14, Christian Moe wrote: But is your local stylesheet uploaded to the server, as it has to be for the stylesheet link in your HTML

Re: Is there any existing function in the org mode API...

* Jean Louis [2025-04-14 14:20]: > Is there any existing function in the org mode API which would give > me all the org headings of a single file in a list? > > In particular, I would like to get the heading title separate with > the content in a cons. > > For example > > org-heading-list => '(

Is there any existing function in the org mode API...

Is there any existing function in the org mode API which would give me all the org headings of a single file in a list? In particular, I would like to get the heading title separate with the content in a cons. For example org-heading-list => '(("* Heading #1" "My text #1") ("* Heading #2") ("My

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

When using themes with background color set to #00, and org-preview-default-process is set to dvisvgm, the LaTeX fragments are displayed incorrectly. To reduplicate: 1. Switch to a theme with background color set to #00 (like Modus Vivendi) 2. Create an org-mode document. Write some L