Re: [RFC PATCH] Re: [bug] Macro in citation not expanded

[Ihor Radchenko]

Ihor Radchenko  writes:

> Subject: [PATCH] org-element: Allow more objects inside citations

Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9ef18956b

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[BUG] Footnotes in section titles

[Ihor Radchenko]

Eric Anderson  writes:

> The resulting LaTeX code (also attached) uses \footnote inside \section and
> \paragraph macros, producing compiler errors.  A little googling turns up
> the following comp.text.tex usenet post
> https://comp.text.tex.narkive.com/lkZWQYaS/using-footnotes-in-paragraph,
> explaining that \footnote is fragile and cannot be used in those contexts
> without \protect.  Manually adding \protect before \footnote in the
> automatically-generated tex file appears to produce correct results.
>
> I don't know if the best fix is to always \protect \footnotes in LaTeX
> export, or if more contextual smarts are required, but this seems like an
> issue worth addressing.

Confirmed.

\protect is not a good idea. There is a reason why LaTeX refuses
footnotes in titles - titles can appear in multiple places in the
document (TOC, page footer, etc) and thus references to the footnotes
are non-deterministic.

https://texfaq.org/FAQ-ftnsect suggests to use
\usepackage[stable]{footmisc}
or to pass optional argument to \section without footnote
\section[title]{title\footnote{title ftnt}}

The footmisc package is a nice solution, but it has certain requirements
about loading order. In particular, it must be loaded after certain
packages (setspace, memoir). We cannot yet control the \usepackage
ordering in LaTeX preamble and always place default LaTeX packages first
- something we cannot do for footmisc.

The \section[...]{...} approach may work, but it is tricky - it is
completely up to the `org-latex-classes'. So, we may have to use regexp
replacement, which might be fragile.

So, I prefer the first approach with footmisc. But we can only do it
after Timothy's patch introducing more flexible templating system is
landed.

CCing Timothy.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] FAQ asnwer for "How can I use arbitrary colors for words/sentences in HTML export?" is outdated

[Ihor Radchenko]

Max Nikulin  writes:

> Juan Manuel Macías to emacs-orgmode… Re: how to export red colored TeX 
> to latex. Tue, 30 Nov 2021 16:56:00 +. 
> https://list.orgmode.org/87bl21vazj@posteo.net
>
> Likely should be modified a bit to support derived backends.

Done.
https://git.sr.ht/~bzg/worg/commit/405547ac

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)]

[Ihor Radchenko]

Ihor Radchenko  writes:

> dal-bla...@onenetbeyond.org writes:
>
>> I just inspected the git version.
>>
>> Is the macro 'org-no-popups' setting _'pop-up-windows' to nil_ and is
>> only used by 'org-switch-to-buffer-other-window' that call
>> 'switch-to-buffer-other-window' which in turn, 
>> set _'pop-up-windows' to t_ ?
>>
>> Also 'pop-up-windows', 'pop-up-frame' are announced to be « provided
>> mainly for backward compatibility and should not be used in new code ».
>
> You are right. org-no-popups was more widely used in the past. It is
> probably time to obsolete it and eventually remove it.
>
> AFAIU, org-no-popups is a legacy function introduced very long time ago.
> Is it left there mostly to keep the working code working.

I have reviewed all the uses of `org-switch-to-buffer-other-window' -
the only user of `org-no-popups' and it looks like the only reason we
don't use `switch-to-buffer-other-window' is let-binding `pop-up-frames'
to nil. Let-binding `pop-up-windows' is not effective because
`switch-to-buffer-other-window' binds (pop-up-windows t).

Considering that switching to popup frame is not Emacs default, it can
only happen when users deliberately changed display-buffer-alist in
their config. Disrespecting user settings is not something nice to do on
Org side.

I conclude that `org-no-popups' and `org-switch-to-buffer-other-window'
should not be used in Org mode.

Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=78dc58508

Other issues raised in this thread need more thought.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: bugs in the new release of org

[Ihor Radchenko]

Samuel Wales  writes:

> in emacs25 -Q with recent maint, this code fails to export; it errors
> if there is an org-id link anywhere in the tree.
>
>   (org-export-as 'html 'subtree nil 'body-only nil)

I assume that this no longer happens in the supported versions of Emacs
(currently - Emacs 27).
Let us know if you still see problems.

Canceled.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] Footnotes in section titles

[Max Nikulin]

On 24/01/2024 19:11, Ihor Radchenko wrote:

The \section[...]{...} approach may work, but it is tricky - it is
completely up to the `org-latex-classes'. So, we may have to use regexp
replacement, which might be fragile.


ox supports the ALT_TITLE property and ox-latex already adds it using 
regexp. So it should possible to define this property with stripped 
footnote by an export filter. I have not tested it, but ALT_TITLE and 
@@latex:\protect@@ might be a workaround.


I recall some tricks with \footnotemark and \footnotetext, but I do not 
remember details and whether it may work for section titles. 
Complications may arise if a heading title has several footnotes.


Perhaps it is better to avoid footnotes in titles and to add some phrase 
to the body instead.

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

[Max Nikulin]

Hi,

I suggest to make the media type used for Org mode files consistent with 
the one used by XDG https://gitlab.freedesktop.org/xdg/shared-mime-info
Currently Emacs has text/x-org, however "x-" prefix is not recommended 
by IANA any more, see https://www.rfc-editor.org/rfc/rfc6648 
"Deprecating the "X-" Prefix and Similar Constructs in Application 
Protocols"


Ideally somebody should file a request to IANA to register the text/org 
media type.

https://www.iana.org/assignments/media-types/media-types.xhtml
However I have no idea concerning a conflict due to the .org file name 
suffix. It was used in the past by early versions of Lotus Organizer. 
https://www.iana.org/assignments/media-types/application/vnd.lotus-organizer


I am unsure if gnus-related code should be committed to some other 
repository at first. I am not a gnus user, so I do not mind if an 
alternative change will be committed.


See also
emacs-orgmode: Org mode MIME type. Sun, 21 Jan 2024 20:56:15 +0700.
https://list.orgmode.org/6d94fff4-4d30-4121-bfd1-f267cb5b6...@gmail.com
From 8b71393625f11590e99896808bbd04ed83f7917e Mon Sep 17 00:00:00 2001
From: Max Nikulin 
Date: Wed, 24 Jan 2024 21:16:28 +0700
Subject: [PATCH] Use text/org media type

Avoid "x-" prefix deprecated by rfc6648 for Org mode media type.
* lisp/net/mailcap.el (mailcap-mime-extensions):
* lisp/gnus/mm-uu.el (mm-uu-org-src-code-block-extract): Replace
text/x-org by text/org.
* lisp/gnus/mm-decode.el (mm-inline-media-tests): Allow text/org in
addition to text/x-org.

Make media type defined for Org mode consistent with


See emacs-orgmode: Org mode MIME type. Sun, 21 Jan 2024 20:56:15 +0700.
https://list.orgmode.org/6d94fff4-4d30-4121-bfd1-f267cb5b6...@gmail.com
---
 lisp/gnus/mm-decode.el | 1 +
 lisp/gnus/mm-uu.el | 2 +-
 lisp/net/mailcap.el| 3 ++-
 3 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/lisp/gnus/mm-decode.el b/lisp/gnus/mm-decode.el
index f91755e967b..cae737e5a3e 100644
--- a/lisp/gnus/mm-decode.el
+++ b/lisp/gnus/mm-decode.el
@@ -246,6 +246,7 @@ (defcustom mm-inline-media-tests
 ("text/x-sh" mm-display-shell-script-inline identity)
 ("application/javascript" mm-display-javascript-inline identity)
 ("text/dns" mm-display-dns-inline identity)
+("text/org" mm-display-org-inline identity)
 ("text/x-org" mm-display-org-inline identity)
 ("text/html"
  mm-inline-text-html
diff --git a/lisp/gnus/mm-uu.el b/lisp/gnus/mm-uu.el
index 3c7e3cbdf1a..b10da0c143a 100644
--- a/lisp/gnus/mm-uu.el
+++ b/lisp/gnus/mm-uu.el
@@ -394,7 +394,7 @@ (defun mm-uu-emacs-sources-extract ()
 
 (defun mm-uu-org-src-code-block-extract ()
   (mm-make-handle (mm-uu-copy-to-buffer start-point end-point)
-		  '("text/x-org" (charset . gnus-decoded
+		  '("text/org" (charset . gnus-decoded
 
 (defvar gnus-newsgroup-name)
 
diff --git a/lisp/net/mailcap.el b/lisp/net/mailcap.el
index 5ff75deb4e6..900099433c4 100644
--- a/lisp/net/mailcap.el
+++ b/lisp/net/mailcap.el
@@ -989,7 +989,8 @@ (defvar mailcap-mime-extensions
 (".jpe"   . "image/jpeg")
 (".jpeg"  . "image/jpeg")
 (".webp"  . "image/webp")
-(".org"   . "text/x-org"))
+;; May be overridden by application/vnd.lotus-organizer in /etc/mime.types.
+(".org"   . "text/org"))
   "An alist of file extensions and corresponding MIME content-types.
 This exists for you to customize the information in Lisp.  It is
 merged with values from mailcap files by `mailcap-parse-mimetypes'.")
-- 
2.39.2

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

[Ihor Radchenko]

dark.key8...@151e.ai writes:

> On Tue, Jan 23, 2024, at 03:57, Ihor Radchenko wrote:
>> May you post the output of
>
> There you go, I infer emacs is launched from $HOME since the two evals in the 
> command launching emacs lead to `load-path' being prepended with "~/lisp" and 
> "~/testing".

Thanks!
What is the value of `default-directory' if you run the following from
Org git folder?

emacs  -Q  --eval '(add-to-list '"'"'load-path (concat default-directory 
"lisp"))' --eval '(add-to-list '"'"'load-path (concat default-directory 
"testing"))'  -l org -f org-version --eval "(setq debug-on-error t 
debug-on-signal nil debug-on-quit nil org-element--cache-self-verify 'backtrace 
org-element--cache-self-verify-frequency 1.0 org-element--cache-map-statistics 
t)"  &

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] Footnotes in section titles

[Juan Manuel Macías]

Max Nikulin writes:

> I recall some tricks with \footnotemark and \footnotetext, but I do
> not remember details and whether it may work for section titles.
> Complications may arise if a heading title has several footnotes.

ox-latex has 'org-latex--delayed-footnotes-definitions': "[...] This
function is used within constructs that don't support \footnote{}
command (e.g., an item tag). In that case, \footnotemark is used within
the construct and the function just outside of it."

The \footnotetext/\footnotemark option works well for specific cases,
but in general I don't like to abuse this method.

> Perhaps it is better to avoid footnotes in titles and to add some
> phrase to the body instead.

That is the ideal scenario. I also believe that footnotes should be
avoided in section headings, if possible. Or at least, have another type
of numbering (symbols, letters...). The manyfoot and bigfoot packages
allow constructions of this type, with various footnote apparatus.

Best regards,

Juan Manuel 

-- 
Juan Manuel Macías -- 

Re: [BUG] Footnotes in section titles

[Colin Baxter]

> Juan Manuel Macías  writes:

> Max Nikulin writes:
>> I recall some tricks with \footnotemark and \footnotetext, but I
>> do not remember details and whether it may work for section
>> titles.  Complications may arise if a heading title has several
>> footnotes.

> ox-latex has 'org-latex--delayed-footnotes-definitions': "[...]
> This function is used within constructs that don't support
> \footnote{} command (e.g., an item tag). In that case,
> \footnotemark is used within the construct and the function just
> outside of it."

> The \footnotetext/\footnotemark option works well for specific
> cases, but in general I don't like to abuse this method.

>> Perhaps it is better to avoid footnotes in titles and to add some
>> phrase to the body instead.

> That is the ideal scenario. I also believe that footnotes should
> be avoided in section headings, if possible. Or at least, have
> another type of numbering (symbols, letters...). The manyfoot and
> bigfoot packages allow constructions of this type, with various
> footnote apparatus.

Indeed, but many journals *require* footnotes in titles, especially for
affiliation, email, etc.

Re: [BUG] Footnotes in section titles

[Juan Manuel Macías]

Colin Baxter writes:

> >> Perhaps it is better to avoid footnotes in titles and to add some
> >> phrase to the body instead.
>
> > That is the ideal scenario. I also believe that footnotes should
> > be avoided in section headings, if possible. Or at least, have
> > another type of numbering (symbols, letters...). The manyfoot and
> > bigfoot packages allow constructions of this type, with various
> > footnote apparatus.
>
> Indeed, but many journals *require* footnotes in titles, especially for
> affiliation, email, etc.

Notes on article titles (and even on the author name) are a slightly
different case from notes on section titles. In LaTeX there is the
"\thanks" command, which inserts footnotes for title and author,
numbered with fnsymbol. For example:

...
\title{Lorem ipsum dolor\thanks{blah blah}}
...

Org does not have support for this type of notes in the #+title or
#+author keywords. For LaTeX you can use a macro. For backends like odt
it is trickier. Look at this thread:

https://lists.gnu.org/archive/html/emacs-humanities/2024-01/msg0.html

I think it would be nice if Org had some kind of support for notes in
#+title and #+author...

Best regards,

Juan Manuel 

Re: [PATCH] Make an org-lint warning more helpful

[Ihor Radchenko]

gerard.vermeu...@posteo.net writes:

> Attached patch makes the relevant org-lint warning more helpful for 
> fixing
> user's Org buffers.

Thanks!
I applied an alternative patch.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d2986be07
Handled.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

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

[dark . key8799]

On Wed, Jan 24, 2024, at 23:02, Ihor Radchenko wrote:
> What is the value of `default-directory' if you run the following from
> Org git folder?
>
> emacs  -Q  --eval '(add-to-list '"'"'load-path (concat 
> default-directory "lisp"))' --eval '(add-to-list '"'"'load-path (concat 
> default-directory "testing"))'  -l org -f org-version --eval "(setq 
> debug-on-error t debug-on-signal nil debug-on-quit nil 
> org-element--cache-self-verify 'backtrace 
> org-element--cache-self-verify-frequency 1.0 
> org-element--cache-map-statistics t)"  &

in that case, it works, `default-directory' is the Org git folder, `load-path' 
has been correctly set and the Org that has been loaded is from the git repo.

-- 
Alexandre Avanian

Re: [BUG] beamer export

[Ihor Radchenko]

Leo Butler  writes:

>>> 1. ox-latex export bug for src blocks containing direct LaTeX when
>>>org-latex-src-block-backend is set to its default 'verbatim value
>>
>> This appears to be Beamer-specific problem with verbatim environments:
>> https://tex.stackexchange.com/questions/140719/verbatim-in-beamer-showing-error-file-ended-while-scanning-use-of-xverbatim
>>
>> The solution might be to use [fragile] frame parameter, but that might
>> have its own drawbacks:
>> https://tex.stackexchange.com/questions/136240/drawbacks-of-using-fragile-frames-in-beamer
>
> Yes, an *automatic* solution may create more problems than it solves.
> Although, I do note that ox-beamer does mark some frames as fragile already.
> I wonder how difficult it would be to add a property drawer to frames,
> so (amongst other things), they could be marked fragile?

Hmm. Actually, that frame is already marked fragile.
Yet, it is not enough...
Apparently, LaTeX has really hard time processing verbatim code inside
beamer frames.

>>> 2. ox-beamer export bug as described in the attached org file
>>
>> This is not a bug. When you specify ignoreheading environment, you imply
>> that the contents of the heading is to be included as is.
>> If you want the contents to become a column, you should specify column
>> environment.
>
> I see. That is not now the ignoreheading property is described. It says
> [1]:
>
> ... As the text in the slide says, the left column is a list and the
> right one is an image. The left column's headline text is ignored,
> specified by =C-c C-b i= which tells org to *ignore* the headline
> text completely.
>
> I think the documentation and example needs to be corrected. I have
> attached a patch.

Thanks! Applied.
https://git.sr.ht/~bzg/worg/commit/aedea59f

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

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

[Ihor Radchenko]

dark.key8...@151e.ai writes:

> On Wed, Jan 24, 2024, at 23:02, Ihor Radchenko wrote:
>> What is the value of `default-directory' if you run the following from
>> Org git folder?
> ...
> in that case, it works, `default-directory' is the Org git folder, 
> `load-path' has been correctly set and the Org that has been loaded is from 
> the git repo.

Very strange. Looks like something wrong about your make installation.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org-internal links broken by defaulting org-open-link-functions to org-ctags-find-tag [9.7-pre (release_9.6.14-1020-g80ce61 @ /Users/kevin/emacs_configs/vanilla/.emacs.d/straight/build/org/)

[Ihor Radchenko]

Kevin Safford  writes:

> When either performing a mouse click or pressing RET on an org-mode
> link, instead of navigating to the specified destination, I am prompted
> to specify a ctags file.
>
> This occurs for all variety of links: radio targets, internal links to
> headlines, external links using, e.g. file: and as far as I can tell,
> any sort of link whatsoever.
>
> This seems to be the wrong choice for the default and results in
> confusing behavior that was quite difficult to understand and resolve.

You are indeed right.
This is a known problem.
See
https://list.orgmode.org/orgmode/87o7omg4ie@alphaville.usersys.redhat.com/
Handled.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

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

[Ihor Radchenko]

Pedro Andres Aranda Gutierrez  writes:

> 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:

Thanks!

> +(defcustom org-latex-fontenc "T1"
> +  "The fontenc for the file. Customise to LGR,T1 when including
> +Greek, etc."
> +  :group 'org-export-latex
> +  :type 'string
> +  :safe #'stringp)

Is there a list of available values somewhere?
https://latexref.xyz/fontenc-package.html only lists OT1, OMS, OML, T1,
and TS1. However, many more are clearly available.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] doc/org-manual.org: update Checkboxes and TODO items cookie statistics

[Ihor Radchenko]

Sławomir Grochowski  writes:

> I'm sending you some updates to the ORG manual.
> I'm sorry there's a lot of changes in this one patch.
> If it's too much, I think I could break the changes into two commits:
>
> First, move the 'Checkboxes' section under 'TODO Items' to '2 Document
> Structure' -> '2.6 Plain Lists' -> '2.6.2 Checkboxes' because 'Checkbox'
> can only exist in plain list items.
> Second, all other updates -> about Checkboxes and TODO items cookie
> statistics.
>
> What do you think?

May you please explain more about the motivation of this patch?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] ob-tangle: Add flag to optionally remove files before writing

[Ihor Radchenko]

Olivier Lischer  writes:

> In December last year was a change introduced, that a file should not be
> removed before
> tangling (https://lists.gnu.org/r/emacs-orgmode/2021-05/msg00337.html).
> In an older bug report
> (https://lists.gnu.org/r/emacs-orgmode/2021-05/msg00337.html)
> the decision was to remove the file before writing.
> I added a variable to switch between both behaviors.

Thanks for the patch, but may you please explain why introducing such
variable is useful?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[BUG] Asked to submit bug report: parse error? [9.7-pre (release_9.6.11-935-g6d7c79 @ /Users/apc/.emacs.d/straight/build/org/)]

[Alejandro Pérez Carballo]

I received the following message after trying to follow a search result 
obtained via grep.

⛔ Warning (org-element): org-element--cache: Org parser error in 
gpd.org::14519. Resetting.
 The error was: (error "Invalid search bound (wrong side of point)")
 Backtrace:
"  backtrace-to-string(nil)
  org-element-at-point()
  org-at-item-p()
  org-indent-add-properties(# 464490 (0 2 0))
  org-indent-initialize-buffer(# (0 2 0))
  org-indent-initialize-agent()
  apply(org-indent-initialize-agent nil)
  timer-event-handler([t 0 0 20 t org-indent-initialize-agent nil idle 0 
nil])
"
 Please report this to Org mode mailing list (M-x org-submit-bug-report).






Emacs  : GNU Emacs 29.1 (build 2, aarch64-apple-darwin21.6.0, NS appkit-2113.60 
Version 12.6.2 (Build 21G320))
 of 2023-11-15
Package: Org mode version 9.7-pre (release_9.6.11-935-g6d7c79 @ 
/Users/apc/.emacs.d/straight/build/org/)

current state:
==
(setq
 org-archive-location "~/org/agenda/archives/%s_archive.org::* Misc tasks"
 org-mac-link-brave-app-p nil
 org-roam-db-location "/Users/apc/.emacs.d/var/org/org-roam.db"
 org-link-elisp-confirm-function 'yes-or-no-p
 org-agenda-skip-deadline-prewarning-if-scheduled 2
 org-cite-insert-processor 'citar
 org-after-todo-state-change-hook '(org-checklist)
 org-after-refile-insert-hook '(org-gcal--refile-post)
 org-roam-db-gc-threshold 2305843009213693951
 org-hide-emphasis-markers t
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-download-file-format-function 'org-download-file-format-default
 org-log-done 'time
 org-attach-id-to-path-function-list '(org-attach-id-ts-folder-format 
org-attach-id-uuid-folder-format org-attach-id-fallback-folder-format)
 org-roam-mode-hook '(my/read-mode-indicator
  my/header-line-hack-face-reset)
 org-ql-views '(("First round candidates" :buffers-files # :query
 (property "FIRST_CUT" "t") :sort nil :narrow nil
 :super-groups nil :title "First round candidates")
("Overview: Agenda-like" :buffers-files
 org-agenda-files :query
 (and (not (done))
  (or (habit) (deadline auto)
   (scheduled :to today) (ts-active :on today))
  )
 :sort (todo priority date) :super-groups
 org-super-agenda-groups :title "Agenda-like")
("Overview: NEXT tasks" :buffers-files
 org-agenda-files :query (todo "NEXT") :sort
 (date priority) :super-groups
 org-super-agenda-groups :title
 "Overview: NEXT tasks")
("Calendar: Today" :buffers-files org-agenda-files
 :query (ts-active :on today) :title "Today"
 :super-groups org-super-agenda-groups :sort
 (priority))
("Calendar: This week" .
 #[0
   "\301 \302\303\304\305\304\306\304\307\310\301 
\311%1!>\204%1c\312\313\314%3D\"\210\211\315H\204\232%0\211\315\316\317\320\311%6!>\2048%0\312\313\314%6D\"\210%5\321H\204\223%0\321\311%6!>\210%6\322H%6\323H%6
\324H%6\n\325H%6
\326H%6\f\327H%5\203\215%0\203\215%0\203\215%0\203\215%0
\203\215%0\211\203\215%0\330\331%6%6%6%6%6%6&%6!\266\206\202\221%0\330
 
\266\206I\210%5\321H\"!I\210\211\315H\262%1[%6\n#&\302\303\332\305\333\306\333\307\310\327\301
 
\311%1!>\204\300%0\312\313\314%3D\"\210\211\315H\204>%1\211\315\316\317\320\311%6!>\204\334%0\312\313\314%6D\"\210%5\321H\2047%1\321\311%6!>\210%6\322H%6\323H%6
 \324H%6\n\325H%6
\326H%6\f\327H%5\2031%1\2031%1\2031%1\2031%1
\2031%1\211\2031%1\330\331%6%6%6%6%6%6&%6!\266\206\2025%1\330
 \266\206I\210%5\321H\"!I\210\211\315H\262%1Z%6#&\334\335 
\336\337%5\340%6\257%5\341\342\343\344\345\346&\207"
   [cl-struct-ts-tags












   ts-now

   

Re: [BUG] Asked to submit bug report: parse error? [9.7-pre (release_9.6.11-935-g6d7c79 @ /Users/apc/.emacs.d/straight/build/org/)]

[Ihor Radchenko]

Alejandro Pérez Carballo  writes:

> I received the following message after trying to follow a search result 
> obtained via grep.
>
> ⛔ Warning (org-element): org-element--cache: Org parser error in 
> gpd.org::14519. Resetting.
>  The error was: (error "Invalid search bound (wrong side of point)")
> ...
> Package: Org mode version 9.7-pre (release_9.6.11-935-g6d7c79 @ 
> /Users/apc/.emacs.d/straight/build/org/)

Thanks for reporting!
It looks like you are not using the latest main.
Does the warning disappear if you upgrade Org mode?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: bugs in the new release of org

[Samuel Wales]

works, please cancel

On 1/24/24, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> in emacs25 -Q with recent maint, this code fails to export; it errors
>> if there is an org-id link anywhere in the tree.
>>
>>   (org-export-as 'html 'subtree nil 'body-only nil)
>
> I assume that this no longer happens in the supported versions of Emacs
> (currently - Emacs 27).
> Let us know if you still see problems.
>
> Canceled.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

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

[Pedro A. Aranda]

Hi again

As stated, this was only a PoC. If you find it useful, I would give it a 
go in the free window. I'm also playing with 
org-latex-default-packages-alist, refining it to use fontspec in 
lualatex and xetex and restricting inputenc and fontenc to pdflatex only.


Best, /PA

On 24/1/24 17:25, Ihor Radchenko wrote:

Pedro Andres Aranda Gutierrez  writes:


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:

Thanks!


+(defcustom org-latex-fontenc "T1"
+  "The fontenc for the file. Customise to LGR,T1 when including
+Greek, etc."
+  :group 'org-export-latex
+  :type 'string
+  :safe #'stringp)

Is there a list of available values somewhere?
https://latexref.xyz/fontenc-package.html only lists OT1, OMS, OML, T1,
and TS1. However, many more are clearly available.