Another low-hanging fruit

Hi, This is another low hanging fruit. I was a bit annoyed to have to leave an empty label for inlined footnotes (à la LaTeX)... I don't know if this qualifies as a TINYCHANGE... Best, /PA -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler

Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

Bruno Barbier writes: > Hi Ihor, > > Ihor Radchenko writes: > >> >> This is most likely something about my current system setup - I can >> reproduce with other Org mode and Emacs versions. But I have no clue >> what is the cause. > > I'm getting the same as you with your MWE. > > The tag,

Re: Async Python src block behavior with :dir header property

Ihor Radchenko writes: > The patch generally looks reasonable, although I am slightly concerned > about interaction between :dir and session we describe in the manual: > > When ‘dir’ is used with ‘session’, Org sets the starting directory > for a new session. But Org does not alter the

Re: Exporting multiple #+AUTHOR keywords

Ihor Radchenko writes: > Juan Manuel Macías writes: > >> Sorry if this is off topic, but something like this: >> >> #+AUTHOR: Fred Astaire >> #+AUTHOR: Ginger Rogers >> >> is exported to LaTeX as: >> >> \author{Fred Astaire Ginger Rogers} >> >> Shouldn't there be some separation? In LaTeX the

Re: [BUG] No result exporting combined org-agenda files to icalendar [9.6.15 (release_9.6.15 @ z:/emacs-i686/share/emacs/29.2/lisp/org/)]. It was: org-icalendar export problems

Ypo writes: > I am sharing a bug report from emacs -q. I don't know how to use a > different org-version that the built-in (or if I should). Sorry for not being clear. Let me elaborate what I expect. 1. Create example Org file or a set of Org files, open them with emacs -Q, and try to

[BUG] No result exporting combined org-agenda files to icalendar [9.6.15 (release_9.6.15 @ z:/emacs-i686/share/emacs/29.2/lisp/org/)]. It was: org-icalendar export problems

I am sharing a bug report from emacs -q. I don't know how to use a different org-version that the built-in (or if I should). Emacs  : GNU Emacs 29.2 (build 2, x86_64-w64-mingw32)  of 2024-01-18 Package: Org mode version 9.6.15 (release_9.6.15 @ ./emacs-i686/share/emacs/29.2/lisp/org/)

Exporting multiple #+AUTHOR keywords (was: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc))

Juan Manuel Macías writes: > Sorry if this is off topic, but something like this: > > #+AUTHOR: Fred Astaire > #+AUTHOR: Ginger Rogers > > is exported to LaTeX as: > > \author{Fred Astaire Ginger Rogers} > > Shouldn't there be some separation? In LaTeX the usual thing is: > > \author{Fred

Re: [BUG]: contradictory requirements between resolving links and noweb result block

gerard.vermeu...@posteo.net writes: > I want to have a kind of dynamic RESULTS: noweb block to select what > other block to put in the LaTeX preamble on LaTeX export. > I can get it working, but in this case links to the RESULTS: noweb block > are not resolved. I found no way to get the links

Re: [BUG] Unsolicited download of remote resources

Max Nikulin writes: > --- 8< --- > #+setupfile: http://localhost:8000/setup-1234567890.org > > test > --- >8 --- > > I am trying to decline attempts to download the remote resource by > hitting "n" (skip), but Org still tries to fetch that file and does it > twice. I see in the *Messages*

Re: [BUG] Unsolicited download of remote resources

On Fri, Feb 02 2024, Max Nikulin wrote: > Hi, > > Org git main HEAD, try to open the following file: > > --- 8< --- > > #+setupfile: http://localhost:8000/setup-1234567890.org > > test > --- >8 --- > > I am trying to decline attempts to download the remote resource by > hitting "n" (skip), but

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Ihor Radchenko writes: > #+AUTHOR: author1 > #+FN_AUTHOR: footnote for author 1 > > #+AUTHOR: author2 > #+FN_AUTHOR: footnote for author 2 Sorry if this is off topic, but something like this: #+AUTHOR: Fred Astaire #+AUTHOR: Ginger Rogers is exported to LaTeX as: \author{Fred Astaire Ginger

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Marvin Gülker writes: > Am Freitag, dem 02. Februar 2024 schrieb Ihor Radchenko: >> What if you have multiple authors? > > At least in my discipline, we only have one footnote even in such a > case, which then is a little longer and describes each author > individually in a separate sentence.

[BUG]: contradictory requirements between resolving links and noweb result block

Hi, I want to have a kind of dynamic RESULTS: noweb block to select what other block to put in the LaTeX preamble on LaTeX export. I can get it working, but in this case links to the RESULTS: noweb block are not resolved. I found no way to get the links resolved without breaking Noweb. See my

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Am Freitag, dem 02. Februar 2024 schrieb Ihor Radchenko: > What if you have multiple authors? At least in my discipline, we only have one footnote even in such a case, which then is a little longer and describes each author individually in a separate sentence. So, one AUTHOR_FN keyword would be

[BUG] Unsolicited download of remote resources

Hi, Org git main HEAD, try to open the following file: --- 8< --- #+setupfile: http://localhost:8000/setup-1234567890.org test --- >8 --- I am trying to decline attempts to download the remote resource by hitting "n" (skip), but Org still tries to fetch that file and does it twice. I see in

Re: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)

Juan Manuel Macías writes: >> #+AUTHOR: John Doe[fn::935 Pennsylvania Avenue, NW Washington, D.C. >> 20535-0001] >> it is probably not exported as expected anyway. > > How about using dedicated keywords? Something like: > > #+FN_AUTHOR: footnote text > #+FN_TITLE: footnote text What if you

Re: org-icalendar export problems

Ypo writes: > If I were able to fulfill a good process to export from agenda to > icalendar, maybe we could share an easy process, useful for a lot of > users that miss a good android calendar visualization. Do you think it > could be possible to export, in an async way, a calendar file every

Re: problems with templates and ID in properties

Uwe Brauer via "General discussions about Org-mode." writes: >> Uwe Brauer writes: > > Thanks for you answer >> This is expected. As per `org-capture-templates' docstring, "entry" >> capture type inserts top-level entries into files: > >>entry an Org node, with a headline.

Re: [RFC] LaTeX - automatically configure encoding when exporting non-Latin languages

Hi, I’m just trying to cover the “legacy” latex. I’ve finally migrated to lualatex for my stuff, and it has really been worthwhile. But who knows what a conference might want me to use ;-P Differentiating between pdflatex and lualatex was what my last patch was for. I also sent a PoC for the

Re: [BUG] Newlines after links are fontified with the org-link face after an incremental search

> Fixed, on main; for Emacs >=29. Will not be fixed for earlier Emacs versions. I've confirmed that it's fixed. Thanks so much for the fast turnaround! Rohit Patnaik

bug#68687: [PATCH v2] Use text/org media type

I am sending an updated version of the patch, earlier I missed one occurrence of text/org. I am leaving it up to you the decision concerning mailcap.el. On 02/02/2024 14:09, Stefan Kangas wrote: So why not: 1. Add support for _receiving_ "text/org" in Emacs 30 2. Wait with _sending_

Re: [RFC] LaTeX - automatically configure encoding when exporting non-Latin languages

Ihor Radchenko writes: > #+LANGUAGE: fa > #+LaTeX_Header: \usepackage[AUTO]{polyglossia} > > #+latex_header: \usepackage[AUTO]{fontspec} I think Pedro is referring to fontenc not fontspec. fontenc cannot be used in either lualatex or XelaTeX. fontspec is for advanced selection of truetype and

Re: bug#68687: Org mode code evaluation (was: bug#68687: [PATCH] Use text/org media type)

[ dropping debbugs from the loop ] Richard Stallman writes: > > I did not imply that Org mode is safe. I directly said that there are > > security issues and that they are known. > > Could you plesae post a pointer to a desciption of them?

Re: Should org-link-parser add type "file" when link has no "file:" prefix?

jos...@ushin.org writes: >> I did not make any changes to Org mode. And I will not, unless we need >> >> to pass this extra information to :follow functions. > > Thank you! I think we can close this issue. Can I close the issue myself? Sure. Handled. -- Ihor Radchenko // yantar92, Org mode

[RFC] LaTeX - automatically configure encoding when exporting non-Latin languages

Pedro Andres Aranda Gutierrez writes: > some days ago I sent a proof-of-concept for customising the coding for the > fontenc package. Before continuing with this, I'd like to know what other > people think and/or need. > > The simplest approach was in the PoC: a custom variable you can set in

Re: [BUG] org-insert-heading changed behavior with Emacs 29.2 [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.2/lisp/org/)]

On 02/02/2024 01:46, gusbrs wrote: That is an unfortunate change of behavior since those who like to keep some breathing space at the end of entries now have to deal with it manually after the heading is inserted. So the handy "C-RET" becomes something like "C-RET RET C-b SPC". C-o

Re: problems with templates and ID in properties

> Thanks for you answer > So that cannot be changed, do I understand correctly. > Thanks for trying it out, I suspect it is then my setting, I just looked > up the org-mode-hook > And I can't find any suspicious. I will try to eyeball my org-add-ons > files. > What command/variable could

Re: problems with templates and ID in properties

> Uwe Brauer writes: Thanks for you answer > This is expected. As per `org-capture-templates' docstring, "entry" > capture type inserts top-level entries into files: >entry an Org node, with a headline. Will be filed >as the child of the

Re: [PATCH] lisp/ox-latex.el: make org-latex-prefer-user-labels safe file local

gerard.vermeu...@posteo.net writes: > I think that it is inconsistent that `org-latex-reference-command' > is a safe file local variable while `org-latex-prefer-user-labels' is > not (it makes no sense to set the first at file scope, while the second > is nil at global scope). Furthermore,

Re: problems with templates and ID in properties

Uwe Brauer writes: > I have the following setting > > (setq org-capture-templates > ... > "** TODO ... > > and I am facing two problems. > When I call org-capture and select this template the corresponding buffer > 1) the corresponding CAPTURE buffer looks like > ... > * TODO G13

Re: [BUG] Newlines after links are fontified with the org-link face after an incremental search

"Rohit Patnaik" writes: > I've noticed a potential regression in the way that org-mode fontifies links > in > the latest git main branch version of org-mode. When the user conducts an > incremental search that matches a link that runs to the end of the line, for > some reason the =org-link=

[PATCH] lisp/ox-latex.el: make org-latex-prefer-user-labels safe file local

Hi, I think that it is inconsistent that `org-latex-reference-command' is a safe file local variable while `org-latex-prefer-user-labels' is not (it makes no sense to set the first at file scope, while the second is nil at global scope). Furthermore, `org-html-prefer-user-labels' is also a safe

Re: figures not exported properly by ox-latex

mahmood sheikh writes: > im on tecosaur's dev branch (version 9.7-pre) > i have the following in an org file: >... CCing Timothy and Karhik. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at

figures not exported properly by ox-latex

im on tecosaur's dev branch (version 9.7-pre) i have the following in an org file: ```org #+name: fig-switching-circuit-1 #+caption: implementation of \(p\) [[attachment:circuit.svg]] ``` it gets turned into this ```

problems with templates and ID in properties

Hi I have the following setting --8<---cut here---start->8--- (setq org-capture-templates '( ("mk" "Grupos Ejercicios" entry (file "~/grupos2024.org") "** TODO %^{Grupo} %T %^g %(org-contacts-template-name) :Link: %a