Re: New try at multi-lingual export to latex/pdf using pdflatex and babel

Hi, Attached is a _proof of concept_ for supporting AUTO in \usepackage{fontenc}. Just an idea of how things could evolve. This only uses a variable you can define as directory or file local to control what is generated in the LaTeX file. Could be expanded in the future to check #+language:

Re: Inconsistent handling of multi-line properties

Ihor Radchenko writes: > Ihor Radchenko writes: > >>> I have noticed that properties that stretch over multiple lines using >>> the :value+: syntax are ignored by org-element-property and therefore >>> also by e.g. org-export-get-node-property when exporting to ics via >>> ox-icalendar.el

Possible LaTeX export bug: Footnotes in items

Hi All, I'm new to the developers' mailing list, so I hope this is the right place to post potential bugs. I don't claim to know exactly why, but at least for certain TOC options, the LaTeX exporter produces invalid code for item titles containing footnotes. I've attached a minimal (non)working

Re: Slowness of org-agenda-redo in org 9.7 vs 9.6.7

dark.key8...@151e.ai writes: > make repro still can't load the correct org because make apparently > launches emacs from my $HOME instead of the repo directory (I tested > manually that `default-directory' is correct when calling emacs -Q) so > I'm think make is reverting to $HOME when launching

Re: [BUG] org-lint tells to move #+name to wrong place in results block

gerard.vermeu...@posteo.net writes: >>> FR: would it be possible to resolve such links? >> >> What is the purpose? Why not simply leaving the result name same as the >> source block? > > I have Python "IN" blocks generating Python "OUT" blocks that may end up > on different pages after exporting

Re: [BUG] org-lint tells to move #+name to wrong place in results block

On 22.01.2024 19:15, Ihor Radchenko wrote: gerard.vermeu...@posteo.net writes: For the listings below org-lint tells me to move "#+name: OUT" downwards: Line Trust Warning 17 high #+name: in results of evaluation will be replaced by re-evaluating the src block. Use

Re: [BUG] org-lint tells to move #+name to wrong place in results block

gerard.vermeu...@posteo.net writes: > For the listings below org-lint tells me to move "#+name: OUT" > downwards: > > Line Trust Warning > 17 high #+name: in results of evaluation will be replaced by > re-evaluating the src block. Use #+name in the block instead. > > This is

[BUG] org-lint tells to move #+name to wrong place in results block

For the listings below org-lint tells me to move "#+name: OUT" downwards: Line Trust Warning 17 high #+name: in results of evaluation will be replaced by re-evaluating the src block. Use #+name in the block instead. This is not true, and after I move it below "#+RESULTS: IN"

Re: Org mode MIME type

On 21/01/2024 22:11, Timothy wrote: However shouldn’t it be “text/x-org”, not just “text/org”? (I am against “application/*” variants since it is a text based format). As per the de-facto mime type for Org is `text/org'. Why not `text/x-org'? Among other reasons,

Re: Slowness of org-agenda-redo in org 9.7 vs 9.6.7

On Mon, Jan 22, 2024, at 20:05, Ihor Radchenko wrote: > This is very strange. We try hard to use only GNU make machinery + Emacs > there. May it help to remove local.mk from org git folder? Ok, I didn't do that but recloned the repo manually (I was working from a clone made by straight.el)

Re: New try at multi-lingual export to latex/pdf using pdflatex and babel

Ihor Radchenko writes: > Juan Manuel Macías writes: > >> Pedro Andres Aranda Gutierrez writes: >> >>> +#+begin_example >>> +,#+latex_class_options: [greek,spanish,oneside] >>> +,#+language: es >>> +,#+latex_header: \PassOptionsToPackage{main=spanish}{babel} >>> +,#+latex_header:

Re: [PATCH] Re: [feature request] startup variable for link display

Ihor Radchenko writes: > See the attached patch. Applied, onto main; after changing the terms to literallinks/descriptivelinks as suggested. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=dd4fd0299 Done. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about

Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer)

"Sparapani, Rodney" writes: > I’ve test that and it works for me per your prescription below. > And, I have committed it to the ESS git repo. Thank you! May I know which version of ESS will have this commit? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: New try at multi-lingual export to latex/pdf using pdflatex and babel

Juan Manuel Macías writes: > Pedro Andres Aranda Gutierrez writes: > >> +#+begin_example >> +,#+latex_class_options: [greek,spanish,oneside] >> +,#+language: es >> +,#+latex_header: \PassOptionsToPackage{main=spanish}{babel} >> +,#+latex_header: \usepackage{alphabeta} % to support greek script

Re: Slowness of org-agenda-redo in org 9.7 vs 9.6.7

dark.key8...@151e.ai writes: > Side note about "make repro": it wouldn't load org from the repo. > Trying to understand why, running "make autoloads", I was expecting > (perhaps wrongly) that `org-version.el' and `org-loaddefs.el' would be > generated in the repo directory/sub-directories but

Re: org-publish-sitemap-file-entry-format documented despite being obsolete

Stefan Kangas writes: > BTW, I see the following symbols that are only mentioned once in > emacs.git, so I suspect some of them might be typos. > > I fixed a few typos on master in emacs.git already (9364c28959a): > > org-col-cookies > org-export--populate-ignore-list >

Re: Inconsistent handling of multi-line properties

Ihor Radchenko writes: >> I have noticed that properties that stretch over multiple lines using >> the :value+: syntax are ignored by org-element-property and therefore >> also by e.g. org-export-get-node-property when exporting to ics via >> ox-icalendar.el (see example below). I was

Re: Patch to allow adjusting latex fragment display scale factor

Matt Huszagh writes: > Yep, we can close/cancel this patch. I had been using that feature to > permit rescaling latex fragments for font size changes, but that's > already handled by the current implementation. Canceled. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about