Re: [POLL] Should we enable or disable automatic tag alignment by default everywhere

[Ihor Radchenko]

Samuel Wales  writes:

> for some reason 9.6.22 says org-auto-align-tags is set to t by default.

Hmm... That's a good reason. And I need to get some sleep.

The default is really t.

The change is still breaking though, but only for people who customized
~org-auto-align-tags~.

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

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Karthik Chikmagalur]

> I've got problem when I use this version of org-latex preview:
>
> RUNNING: dvisvgm --page=1- --optimize --clipjoin --relative --no-fonts 
> --bbox=preview -o c\:/Users/artsi0m/AppData/Local/Temp/org-tex-DAJVTr-%9p.svg 
> c\:/Users/artsi0m/AppData/Local/Temp/org-tex-DAJVTr.dvi
>
> ERROR: can't open file 
> 'c\:/Users/artsi0m/AppData/Local/Temp/org-tex-DAJVTr.dvi' for reading
>
> As you can get from the traceback it is problem with windows. But I
> remember solving simillar problem with org-fc already[1][2]. I just removed
> escaping (quoting) from one of the elisp functions.

Thank you for testing the new LaTeX preview system, we haven't had any
reports yet from Windows.

As a temporary measure, could you try replacing calls to
shell-quote-argument with identity in the following two functions?

org-latex-preview--tex-compile-async
org-latex-preview--image-extract-async

I'd be interested to know if it works as expected otherwise.

> So, the main problem of the problem is that on Windows
> (shell-quote-argument) function will quote c:/ as c\:/ which breaks
> ability to find one or another file. It maybe other function with this
> quoting, but I suppose that it is it.

shell-quote-argument is used all over Emacs, so I'm quite surprised it
mangles file paths on Windows.

Karthik

org-persist-write slowing down kill-buffer

[Karthik Chikmagalur]

Hi,

I've been noticing that kill-buffer blocks Emacs for a noticeable
period when killing org buffers.  Here are elp results obtained by
instrumenting org-persist-* and kill-buffer:

| Function name | Call count | Elapsed time | Average time |
|---++--+--|
| kill-buffer   | 38 | 2.5647546329 | 0.0674935429 |
| org-persist-write-all-buffer  |  1 |  2.562779994 |  2.562779994 |
| org-persist-write-all |  1 |   2.56277329 |   2.56277329 |
| org-persist-write |  1 |  1.627834788 |  1.627834788 |
| org-persist--write-elisp-file |  1 |  0.312172392 |  0.312172392 |
| org-persist--find-index   |   4808 | 0.0480629129 | 9.996...e-06 |
| org-persist--normalize-associated |  4 |  0.007245059 | 0.0018112647 |
| org-persist--normalize-container  |  7 | 0.0001262719 | 1.803...e-05 |
| org-persist--get-collection   |  1 |  0.000113982 |  0.000113982 |
| org-persist-write:elisp   |  2 | 2.647...e-05 | 1.323...e-05 |
| org-persist--display-time |  1 |3.772e-06 |3.772e-06 |
| org-persist-write:version |  1 |1.467e-06 |1.467e-06 |

It blocks Emacs for about 3 seconds each time.  Any Org file with > 500
lines causes this behavior.

I've also attached the sampling profiler output from killing an Org
buffer.

Some facts that might be relevant:

- I'm using the WIP LaTeX preview system fork of Org, but there are no
  LaTeX previews in the Org buffers that I run these tests on.  (There
  aren't even any LaTeX fragments.)

- My org-persist-dir is 627MB in size.

This is Emacs 29.3 (pgtk branch), the Org commit that the LaTeX preview
patches are rebased on is 1ae978f940c0f88473f2232177c63a0de7fb7a1c.

Let me know if I can help with more information.

Karthik


kill-buffer-profiler-report.eld
Description: Binary data

Re: [POLL] Should we enable or disable automatic tag alignment by default everywhere

[Samuel Wales]

for some reason 9.6.22 says org-auto-align-tags is set to t by default.
[btw, i use proportional fonts, so org-tags-column is 0.]



-- 
The Kafka Pandemic

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

Re: Using search options in HTTP-style links

[Joseph Turner]

Ihor Radchenko  writes:

> Joseph Turner  writes:
>
>> ...
>> (eww "https://ushin.org/needs-list.org#%3A%3A%23care;)
>>
>> ...loads the file in eww-mode with point at the top of the file.
>>
>> I think it would be more useful to instead activate org-mode (or a mode
>> which derives from it - "eww-org-mode"?), decode the link fragment, and
>> then jump to the location specified by the search option.
>
> There is a convention for pdfs:
> http://www.example.com/document.pdf#page=5
> But, AFAIK, it is not RFC.
>
> So, there is nothing stopping from creating an ad-hoc convention to
> parse URL locators in links to PDFs or org files or whatnot.

I'll need to dig a little more to see what changes would need to be made
in order for org-store-link to store properly formatted search options
with http: or hyper: links.  Currently, org-create-file-search-functions
is only used when creating a file: link.

> However, the question about activating a major mode on web content is a
> question to Emacs developers. It should be considered carefully, because
> activating major modes may not be safe.

hyperdrive.el activates a major mode with set-auto-mode when content is
loaded over the network.  This behavior is on by default.  Do you have
any advice about this?

Should hyperdrive.el set untrusted-content to t?

Thanks!

Joseph

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[Emmanuel Charpentier]

Le mercredi 17 avril 2024 à 20:18 +, Ihor Radchenko a écrit :
> Emmanuel Charpentier  writes:

[ Snip... ]


> What if you do M-x trace-function  org-compile-file-commands

No such function : I just have  org-compile-file , which I traced.

> 
> and run the preview.
> Then, a buffer should appear listing the command expansions used
> during
> the preview process. May you then share that buffer?

Here it comes :

Buffer "Trace output" :

*
==
1 -> (org-compile-file "/tmp/orgtexD0afvR.tex" ("latex -interaction
nonstopmode -output-directory %o %f") "dvi" "Please adjust `dvipng'
part of `org-preview-latex-process-alist'." #)
1 <- org-compile-file: "/tmp/orgtexD0afvR.dvi"
==
1 -> (org-compile-file "/tmp/orgtexD0afvR.dvi" ("dvipng -D %D -T tight
-bg Transparent -o %O %f") "png" "Please adjust `dvipng' part of `org-
preview-latex-process-alist'." #
((68 . "140.0") (83 . "1.0")))
1 <- org-compile-file: !non-local\ exit!
*

Buffer "*Org Preview LaTeX Output*" :

*
../../../../../tmp/orgtexD0afvR.dvi: No such file or directory
This is dvipng 1.15 Copyright 2002-2015 Jan-Ake Larsson
*

HTH,

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[Ihor Radchenko]

Emmanuel Charpentier  writes:

>> Assuming that your `org-preview-latex-default-process' is using the
>> default value of 'dvipng, does it help if you change the image
>> convertor
>> command to use absolute path?
>
> I didn't know that one could do that : the placeholders are not well
> documented...

Yeah. This particular option is missing from the docstring of
`org-preview-latex-process-alist'.

>> (plist-put (alist-get 'dvipng org-preview-latex-process-alist)
>>     :image-converter
>>    '("dvipng -D %D -T tight -o %O %F"))
>
> Nope, same problem : the *Org Preview LaTeX Output* buffer says :
>
> ../../../../../tmp/orgtexSyy18r.dvi: No such file or directory
> This is dvipng 1.15 Copyright 2002-2015 Jan-Ake Larsson
>
> If I understand it correctly, the %F placeholder should be an
> *absolute* filename. It is not...
>
> Couldn't the output directory of the :latex-compiler element being
> hardcoded to, say, the curerent directory or a subdirectory thereof,
> and ditto for the input directory of :image-converter ?

What if you do M-x trace-function  org-compile-file-commands 
and run the preview.
Then, a buffer should appear listing the command expansions used during
the preview process. May you then share that buffer?

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

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[Emmanuel Charpentier]

Le mercredi 17 avril 2024 à 16:48 +, Ihor Radchenko a écrit :
> Emmanuel Charpentier  writes:
> 
> > I have a case where the current way of forcing the temporary
> > directory
> > to me `/tmp` is wrong. Running emacs on Ubuntu **under WSL2**,,
> > exporting latex snippets to ODT *as images* fails : the `.dvi`
> > files
> > are correctly compiled and placed in `/tmp{, but the convert
> > program
> > tries to read them in `../../../../tmp/`, which is indeed `/tmp` in
> > a
> > "normal" filesystem but **is not** in WSL, where the root (`/`) is
> > in
> > fact a mounted tree.
> > 
> > Admittedly, this is a corner case, but it turned out to be
> > necessary
> > (exporting via mathml gave unsatisfying results).
> 
> It looks like is a different bug. (probably even in Emacs, when
> calculating relative path)

That might also be an idiosyncratic bug of WSL2' implementation of the
virtual machine filesystem...
> 
> Assuming that your `org-preview-latex-default-process' is using the
> default value of 'dvipng, does it help if you change the image
> convertor
> command to use absolute path?

I didn't know that one could do that : the placeholders are not well
documented...

> 
> (plist-put (alist-get 'dvipng org-preview-latex-process-alist)
>      :image-converter
>    '("dvipng -D %D -T tight -o %O %F"))

Nope, same problem : the *Org Preview LaTeX Output* buffer says :

../../../../../tmp/orgtexSyy18r.dvi: No such file or directory
This is dvipng 1.15 Copyright 2002-2015 Jan-Ake Larsson

If I understand it correctly, the %F placeholder should be an
*absolute* filename. It is not...

Couldn't the output directory of the :latex-compiler element being
hardcoded to, say, the curerent directory or a subdirectory thereof,
and ditto for the input directory of :image-converter ?

Sincerely,

Re: [FR] Please add custom command variable to org-latex-footnote-reference

[Alexander Gogl]

Dear Ihor,

thank's for your advice! Here is the updated patch. Now it works.

..
ox-latex: New option to customize LaTeX footnote command

Some LaTeX classes define their own footnote commands. For example,
kaobook
(https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf)
has \footnotes and \sidenotes, whereby sidenotes (notes are put into the
outter margin) are the dominant form of putting notes in kaobook. It
would be great if you could make the footnote command in the footnote
function customizable. My proposal is in the attachment.
..

>From 1c7bee53ac91a8296c144f157ab8646b1a7a6595 Mon Sep 17 00:00:00 2001
From: Alexander Gogl 
Date: Wed, 17 Apr 2024 16:00:41 +0200
Subject: [PATCH 1/2] added option to customize latex footnote command in
 export

---
 etc/ORG-NEWS |  4 
 lisp/ox-latex.el | 14 --
 2 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index e61bd6988..a579260f5 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -999,6 +999,10 @@ even though it does not have its own ID.  By giving files top-level id
 properties, links to headlines in the file can also be made more
 robust by using the file id instead of the file path.
 
+*** New option ~latex-default-footnote-command~
+
+This new option allows you to define the LaTeX command the  org-mode footnotes are converted to (for example ~\\sidenote{%s%s}~).
+
 ** New features
 *** =colview= dynamic block now writes column width specifications
 
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 5c19e1fe7..b45d13ca2 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -135,6 +135,9 @@
 (:latex-default-table-environment nil nil org-latex-default-table-environment)
 (:latex-default-quote-environment nil nil org-latex-default-quote-environment)
 (:latex-default-table-mode nil nil org-latex-default-table-mode)
+;; TODO implement options variable
+(:latex-default-footnote-command "\\footnote{%s%s}" nil org-latex-default-footnote-command)
+;;
 (:latex-diary-timestamp-format nil nil org-latex-diary-timestamp-format)
 (:latex-engraved-options nil nil org-latex-engraved-options)
 (:latex-engraved-preamble nil nil org-latex-engraved-preamble)
@@ -667,6 +670,14 @@ The function result will be used in the section format string."
 
  Footnotes
 
+(defcustom org-latex-default-footnote-command "\\footnote{%s%s}"
+  "Default command used to insert footnotes.
+  Customize this command if the LaTeX class provides a different notation command like `\\sidenote{%s%s}' that you want to use."
+  :group 'org-export-latex
+  :version "24.4"  ;; FIXME enter correct version
+  :package-version '(Org . "9.7")
+  :type 'string)
+
 (defcustom org-latex-footnote-separator "\\textsuperscript{,}\\,"
   "Text used to separate footnotes."
   :group 'org-export-latex
@@ -780,7 +791,6 @@ default we use here encompasses both."
   :group 'org-export-latex
   :type 'string)
 
-
  Tables
 
 (defcustom org-latex-default-table-environment "tabular"
@@ -2239,7 +2249,7 @@ CONTENTS is nil.  INFO is a plist holding contextual information."
   (t
(let ((def (org-export-get-footnote-definition footnote-reference info)))
 	 (concat
-	  (format "\\footnote{%s%s}" (org-trim (org-export-data def info))
+	  (format org-latex-default-footnote-command (org-trim (org-export-data def info))
 		  ;; Only insert a \label if there exist another
 		  ;; reference to def.
 		  (cond ((not label) "")
-- 
2.41.0

>From 12d211a5f0c56faf1b829fef26f788f210a31382 Mon Sep 17 00:00:00 2001
From: Alexander Gogl 
Date: Wed, 17 Apr 2024 21:22:51 +0200
Subject: [PATCH 2/2] ox-latex: New option to customize LaTeX footnote command

* lisp/ox-latex.el (org-export-define-backend): Add option.
(org-latex-default-footnote-command): New custom variable.
(org-latex-footnote-reference): Replace string "\\footnote{%s%s}"
with custom variable.

* etc/ORG-NEWS (New and changed options): Add description to option.

Some LaTeX classes define their own footnote commands. For example,
kaobook (https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf)
has \footnotes and \sidenotes, whereby sidenotes (notes are put into
the outter margin) are the dominant form of putting notes in
kaobook. It would be great if you could make the footnote command in
the footnote function customizable. My proposal is in the attachment.

Modified from a feature request by Alexander Gogl.

TINYCHANGE
---
 etc/ORG-NEWS | 12 ++--
 lisp/ox-latex.el | 12 ++--
 2 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index a579260f5..571ab3c98 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -999,9 +999,17 @@ even though it does not have its own ID.  By giving files top-level id
 properties, links to headlines in the file 

Re: [BUG] Org-Agenda leaves frame around [9.7-pre (release_9.6.8-785-g72bbf8.dirty @ /home/bidar/.local/private/etc/emacs/lib/org/lisp/)]

[Ihor Radchenko]

Björn Bidar  writes:

>>> E.g.:
>>> 1. I capture a link using org-protocol
>>> 2. Switch to the org-buffer
>>> 3. C-c C-l
>>> 4. RET  <- frame closes however links isn't inserted into the target 
>>> org-buffer 
>>
>> May you provide more details about how to reproduce?
>
> What do you miss after the initial details?

1. Did you start from emacs -Q?
2. What kind of protocol did you use?
3. Did you need to switch to specific Org buffer or it gotta be some an
arbitrary org buffer?

In other words, I need detailed steps starting from emacs -Q, if possible.

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

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[Ihor Radchenko]

Emmanuel Charpentier  writes:

> I have a case where the current way of forcing the temporary directory
> to me `/tmp` is wrong. Running emacs on Ubuntu **under WSL2**,,
> exporting latex snippets to ODT *as images* fails : the `.dvi` files
> are correctly compiled and placed in `/tmp{, but the convert program
> tries to read them in `../../../../tmp/`, which is indeed `/tmp` in a
> "normal" filesystem but **is not** in WSL, where the root (`/`) is in
> fact a mounted tree.
>
> Admittedly, this is a corner case, but it turned out to be necessary
> (exporting via mathml gave unsatisfying results).

It looks like is a different bug. (probably even in Emacs, when
calculating relative path)

Assuming that your `org-preview-latex-default-process' is using the
default value of 'dvipng, does it help if you change the image convertor
command to use absolute path?

(plist-put (alist-get 'dvipng org-preview-latex-process-alist)
   :image-converter
   '("dvipng -D %D -T tight -o %O %F"))

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

Re: [POLL] Should we enable or disable automatic tag alignment by default everywhere

[Ihor Radchenko]

William Denton  writes:

> On Wednesday, April 17th, 2024 at 06:21, Ihor Radchenko  
> wrote:
>
>> I'd like to ask you, Org mode users, whether we should flip the default
>> value of ~org-auto-align-tags~ to t or leave it as nil
>
> I use proportional fonts for regular text (with the mixed-pitch package).  In 
> this situation, as far as I know the only way to make tags look at consistent 
> is to set org-tags-column to 0 so they directly follow the text (I make the 
> font size smaller, so there's a large heading then small tag) or to jam them 
> way over as far right as they'll go.  Anything else and they look ragged.

Yes. But this is out of scope of the discussed tag alignment -
`org-auto-align-tags' controls the actual plain text in Org buffers.
`org-tags-column' has no meaning when non-proportional fonts are used.

For non-proportional fonts, the display depends on the specifics of the
fonts used to display various parts of the headline. If we want to
display Org tags right-aligned, for example, it is a job for
fontification and does not need to involve editing the underlying plain text.

> So I suspect people using variable pitches will already have this turned on, 
> and making it the default won't bother them.  

Sure. I'd like to hear from people who do care about the proposed changes.

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

Re: [C-c C-q] org-set-tags-command completed tags does not contains current buffer local tags

[Ihor Radchenko]

"Christopher M. Miles"  writes:

> In the [C-c C-q] org-set-tags-command, I found it does not complete tags in 
> current buffer.
> ...
> Steps to reproduce:
>
> 1. create an empty Org mode file and open it as a Emacs buffer.
> 2. Fill in Org content as bellowing
>
> #+begin_src org
> * headline 1  :tag1:workflow:
>
> * headline 2 :tag2:name:
> #+end_src
>
> 3. save buffer
> 4. Press [C-c C-q] org-set-tag-command
> 5. You can't see buffer local tags "tag1", "tag2", "workflow", "name" in tags 
> completion.

I followed your steps starting from emacs -Q and also starting from make
repro in Org git repo using Emacs master and Emacs 29. In all the cases,
I am seeing all the buffer tags in the completion. I am unable to
reproduce the problem.

May you please provide steps to reproduce starting from emacs -Q using
the latest bugfix or main branch of Org mode?

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

Re: [FR] Please add custom command variable to org-latex-footnote-reference

[Ihor Radchenko]

Alexander Gogl  writes:

> I completed the patch (see attachment). Please let me know if I made any 
> mistake in the patch or if I should send the patch to another E-Mail-Address.

Thanks! We use Org mailing list (public) to send patches and discuss Org
mode development.

I added Org mailing list to CC in this email.
You can simply use "Reply All" to send the next version of the patch.

> Reason for patch
>
> Some LaTeX classes define their own footnote commands. For example, kaobook 
> (https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf)
>  has \footnotes and \sidenotes, whereby sidenotes (notes are put into the 
> outter margin) are the dominant form of putting notes in kaobook. It would be 
> great if you could make the footnote command in the footnote function 
> customizable. My proposal is in the attachment.

You can put this description in the commit message.
Also, if you can, please add changelog entries, as described in
https://orgmode.org/worg/org-contribute.html#commit-messages

> Subject: [PATCH] added option to customize latex footnote command in export

What about

ox-latex: New option to customize LaTeX footnote command

My version (1) clearly states which library the patch is changing; (2)
Uses imperative tone as we usually do in commit messages.

> +*** New option ~latex-default-footnote-command~
> +
> +This new option allows you to define the LaTeX command the  org-mode 
> footnotes are converted to (for example ~\\sidenote{%s%s}~).

We use "Org mode" to name Org mode.
Also, we fill the text to default `fill-column' value of 70.

> diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
> index 5c19e1fe7..b45d13ca2 100644
> --- a/lisp/ox-latex.el
> +++ b/lisp/ox-latex.el
> @@ -135,6 +135,9 @@
>  (:latex-default-table-environment nil nil 
> org-latex-default-table-environment)
>  (:latex-default-quote-environment nil nil 
> org-latex-default-quote-environment)
>  (:latex-default-table-mode nil nil org-latex-default-table-mode)
> +;; TODO implement options variable

May you explain the purpose of this TODO?

> +(:latex-default-footnote-command "\\footnote{%s%s}" nil 
> org-latex-default-footnote-command)

"\\footnote{%s%s}" makes no sense in this context. The format of export
options is described in the docstring of `org-export-options-alist':

The key of the alist is the property name, and the value is a list
like (KEYWORD OPTION DEFAULT BEHAVIOR) where:

KEYWORD is a string representing a buffer keyword, or nil.
OPTION is a string that could be found in an #+OPTIONS: line.
DEFAULT is the default value for the property.
BEHAVIOR determines how Org should handle multiple keywords for

You placed "\\footnote{%s%s}" in KEYWORD slot, which is not right.
KEYWORD slot is what defines how to set the value locally. For example,
"AUTHOR" in (:author "AUTHOR" nil user-full-name parse) means that
:author export option can be set as

#+AUTHOR: value

> +(defcustom org-latex-default-footnote-command "\\footnote{%s%s}"
> +  "Default command used to insert footnotes.
> +  Customize this command if the LaTeX class provides a different notation 
> command like `\\sidenote{%s%s}' that you want to use."

Please explain what is the meaning of each %s in the value in the
docstring.

Also, please re-fill the docstring to avoid long lines.

> +  :group 'org-export-latex
> +  :version "24.4"  ;; FIXME enter correct version

:version is not needed. It is obsolete keyword we no longer use in the
new customizations.

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

Re: PATCH allow explicit style= in #+cite_export: biblatex

[Pedro Andres Aranda Gutierrez]

BTW, I was thinking that maybe "\\`[^=]+=" may be better than matching
style= anywhere in the options string...
Open to discuss it...
/PA

On Wed, 17 Apr 2024 at 09:00, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:

> Stop the press... I discovered a small bug in the last patch.
> Attached is a new version.
>
> /PA
>
> On Wed, 17 Apr 2024 at 08:22, Pedro Andres Aranda Gutierrez <
> paag...@gmail.com> wrote:
>
>> Hi again
>>
>> Rationale of the patch:
>> Currently, when the options to biblatex are _not_ xxx/xxx format, a
>> style= is prepended, because
>> it is assumed that it will be a biblatex options string starting with a
>> style.
>> With the proposed patch, I add the possibility of using a biblatex
>> options string where style= is stated
>> explicitly (anywhere in the string). This adds congruency WRT
>> the ~org-cite-biblatex-options~ variable.
>>
>> Best, /PA
>>
>> On Sun, 14 Apr 2024 at 09:16, Pedro Andres Aranda Gutierrez <
>> paag...@gmail.com> wrote:
>>
>>> HI, full answer...
>>>
>>> In the original code, that section prepends "style=" in some cases. I
>>> have stumbled across
>>> instances where the options started with style= because they were taken
>>> directly from LaTeX
>>> and the generated code ended by like:
>>> \usepackage[style=style=numeric,backend=biber]{biblatex}
>>> for
>>> #+cite_export: biblatex style=numeric,backend=biber
>>> which, BTW, is something someone used the LaTeX may parse as correct.
>>> I was just trying to cater for this case.
>>>
>>> Best, /PA
>>>
>>>
>>> On Sun, 14 Apr 2024 at 07:30, Pedro Andres Aranda Gutierrez <
>>> paag...@gmail.com> wrote:
>>>
 Sorry... I was not right... You are right. I'll take a look at it again.
 /PA

 On Sun, 14 Apr 2024 at 07:22, Pedro Andres Aranda Gutierrez <
 paag...@gmail.com> wrote:

> Hi,
>
> Maybe not... because style= is a keyword for the biblatex package,
> while bibstyle or citestyle aren't.
>
> Best, /PA
>
> On Sat, 13 Apr 2024 at 16:32, Ihor Radchenko 
> wrote:
>
>> Pedro Andres Aranda Gutierrez  writes:
>>
>> > HI,
>> > Attached is a small patch to allow explicitly adding style= in the
>> biblatex export options, to increase consistency with
>> > Customisation variables.
>>
>> Thanks!
>>
>> >  (style-options
>> >   (cond
>> >((null style) nil)
>> > +  ;; allow the user to include "style=" anywhere in the
>> style options
>> > +  ((string-match "\\(^s\\|,s\\)tyle=" style) (list style))
>> >((not (string-match "/" style)) (list (concat "style="
>> style)))
>> >(t
>> > (list (concat "bibstyle=" (substring style nil
>> (match-beginning 0)))
>>
>> If we allow style=..., may as well allow bibstyle= and citestyle=.
>>
>> --
>> Ihor Radchenko // yantar92,
>> Org mode contributor,
>> Learn more about Org mode at .
>> Support Org development at ,
>> or support my work at 
>>
>
>
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Headaches with a Juju log:
> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
> run a leader-deposed hook here, but we can't yet
>
>

 --
 Fragen sind nicht da, um beantwortet zu werden,
 Fragen sind da um gestellt zu werden
 Georg Kreisler

 Headaches with a Juju log:
 unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
 run a leader-deposed hook here, but we can't yet


>>>
>>> --
>>> Fragen sind nicht da, um beantwortet zu werden,
>>> Fragen sind da um gestellt zu werden
>>> Georg Kreisler
>>>
>>> Headaches with a Juju log:
>>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>>> run a leader-deposed hook here, but we can't yet
>>>
>>>
>>
>> --
>> Fragen sind nicht da, um beantwortet zu werden,
>> Fragen sind da um gestellt zu werden
>> Georg Kreisler
>>
>> Headaches with a Juju log:
>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>> run a leader-deposed hook here, but we can't yet
>>
>>
>
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Headaches with a Juju log:
> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
> a leader-deposed hook here, but we can't yet
>
>

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[Emmanuel Charpentier]

On 25/03/2024 19:49, Max Nikulin wrote:

> > (defun org-ensure-tmp-dir (dir-symbol prefix)
> >    (let ((dir (symbol-value dir-symbol)))
> >      ;; Temporary directory has not been cleaned.
> >      (or (and dir (file-directory-p dir) dir)
>
>
>`if' should be used instead of `or' here.
>
>
>
>>
>> (setf (symbol-value dir-symbol)
>>   (make-temp-file (or prefix "orgtmp-") 'dir)
>> 
>> (defvar org-tex-tmpdir nil)
>> 
>> Usage example: (org-ensure-tmp-dir 'org-tex-tmpdir "orgtex-")

> I do not like that the function may be called with
different `temporary-file-directory' and I can not figure out how to
adjust API to handle such case. On the other hand I am unsure if it is
a realistic case when this function is called with
alternating `temporary-file-directory'.  

I have a case where the current way of forcing the temporary directory
to me `/tmp` is wrong. Running emacs on Ubuntu **under WSL2**,,
exporting latex snippets to ODT *as images* fails : the `.dvi` files
are correctly compiled and placed in `/tmp{, but the convert program
tries to read them in `../../../../tmp/`, which is indeed `/tmp` in a
"normal" filesystem but **is not** in WSL, where the root (`/`) is in
fact a mounted tree.

Admittedly, this is a corner case, but it turned out to be necessary
(exporting via mathml gave unsatisfying results).

Re: [BUG] LaTeX preview should use a subdirectory in /tmp

[copropriete27ruemoret]

On 25/03/2024 19:49, Max Nikulin wrote:

> > (defun org-ensure-tmp-dir (dir-symbol prefix)
> >    (let ((dir (symbol-value dir-symbol)))
> >      ;; Temporary directory has not been cleaned.
> >      (or (and dir (file-directory-p dir) dir)
>
>
>`if' should be used instead of `or' here.
>
>
>
>>
>> (setf (symbol-value dir-symbol)
>>   (make-temp-file (or prefix "orgtmp-") 'dir)
>> 
>> (defvar org-tex-tmpdir nil)
>> 
>> Usage example: (org-ensure-tmp-dir 'org-tex-tmpdir "orgtex-")

> I do not like that the function may be called with different `temporary-file-directory' and I can not figure out how to adjust API to handle such case. On the other hand I am unsure if it is a realistic case when this function is called with alternating `temporary-file-directory'.  

I have a case where the current way of forcing the temporary directory to me `/tmp` is wrong. Running emacs on Ubuntu **under WSL2**,, exporting latex snippets to ODT *as images* fails : the `.dvi` files are correctly compiled and placed in `/tmp{, but the convert program tries to read them in `../../../../tmp/`, which is indeed `/tmp` in a "normal" filesystem but **is not** in WSL, where the root (`/`) is in fact a mounted tree.

Admittedly, this is a corner case, but it turned out to be necessary (exporting via mathml gave unsatisfying results).

Re: [POLL] Should we enable or disable automatic tag alignment by default everywhere

[William Denton]

On Wednesday, April 17th, 2024 at 06:21, Ihor Radchenko  
wrote:

> I'd like to ask you, Org mode users, whether we should flip the default
> value of ~org-auto-align-tags~ to t or leave it as nil

I use proportional fonts for regular text (with the mixed-pitch package).  In 
this situation, as far as I know the only way to make tags look at consistent 
is to set org-tags-column to 0 so they directly follow the text (I make the 
font size smaller, so there's a large heading then small tag) or to jam them 
way over as far right as they'll go.  Anything else and they look ragged.

So I suspect people using variable pitches will already have this turned on, 
and making it the default won't bother them.  

Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada

Re: [PATCH v2] org-faq.org: Inline comments

[Max Nikulin]

On 15/04/2024 19:17, Ihor Radchenko wrote:



+#+begin_src org
+The following line may become a patagraph separator.
+@@comment: might give unexpected effect @@
+Put some text before @@comment: a better variant
+@@ and after instread.
+#+end_src


I am no longer able to reproduce the problem with @@comment:...@@
splitting paragraph in the above example.


I see no changes in respect to ox-md on the main branch.

 8< 
The following line may become a paragraph separator.
@@comment: might give unexpected effect @@
Put some text before @@comment: a better variant
@@ and after instead.
 >8 

is exported to

 8< 
The following line may become a paragraph separator.

Put some text before  and after instead.
 >8 

[C-c C-q] org-set-tags-command completed tags does not contains current buffer local tags

[Christopher M. Miles]

In the [C-c C-q] org-set-tags-command, I found it does not complete tags in 
current buffer.

#+begin_src emacs-lisp
(defun org-set-tags-command ( arg)
  ...
  (let* (...
 (local-table (or org-current-tag-alist (org-get-buffer-tags)))
 ;; the `org-current-tag-alist' is from my customized 
`org-tag-persistent-alist'.
 ...)))
#+end_src

Steps to reproduce:

1. create an empty Org mode file and open it as a Emacs buffer.
2. Fill in Org content as bellowing

#+begin_src org
* headline 1  :tag1:workflow:

* headline 2 :tag2:name:
#+end_src

3. save buffer
4. Press [C-c C-q] org-set-tag-command
5. You can't see buffer local tags "tag1", "tag2", "workflow", "name" in tags 
completion.

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature

Re: [BUG] query-replace breaks org-mode [9.6.6 (release_9.6.6 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]

[Ihor Radchenko]

Joe Gilder  writes:

> Noticed this a few times. When I run query-replace, it functions as usual. 
> However, when I’m done with the query-replace, it seems to break org-fold. I 
> can’t fold/unfold headings anymore. 
>
> I had the same issue the other day with replace-string as well. 
>
> Killing buffer and coming back fixes it. 

You can set `org-fold-core-style' to 'overlays (early in your config) to
fix this.

Unfortunately, text-property based folding cannot be reliable because
too many parts of Emacs and third-party packages hard-code certain
implementation details.

The default value of `org-fold-core-style' is changed to 'overlays on
main to avoid this and similar problems.
Handled.

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

Re: [POLL] Should we enable or disable automatic tag alignment by default everywhere

[Gautier Ponsinet]

Hello Ihor,

Ihor Radchenko  [2024-04-17 10:21 +]:
> I'd like to ask you, Org mode users, whether we should flip the default
> value of ~org-auto-align-tags~ to t or leave it as nil.

I am voting for applying the change you propose and setting the default
value of ~org-auto-align-tags~ to t.

(and thank you for all your work!)

All the best,
Gautier.

[POLL] Should we enable or disable automatic tag alignment by default everywhere

[Ihor Radchenko]

Dear all,

We have ~org-auto-align-tags~ option that controls whether editing
commands re-align the tags.  However, this option is only respected by
some editing commands, like changing the headline level.  Many other
editing commands re-align tags unconditionally.  For example, when

* typing right here or deleting inside a heading with   :tag1:tag2:

the :tag1:tag2: automatically remains aligned, regardless of the value
of ~org-auto-align-tags~.

In the attached patch, I am changing all the commands in Org mode,
including "self-insert" and "delete-backwards" to respect this option.

However, because ~org-auto-align-tags~ is disabled by default, this will
cause breaking change - there are many more commands in Org mode that
re-align tags unconditionally compared to the commands that do take it
into account.

I'd like to ask you, Org mode users, whether we should flip the default
value of ~org-auto-align-tags~ to t or leave it as nil - flipping the
default value will preserve the behavior described above, but change the
default behavior of ~org-promote~, ~org-demote~, ~org-todo~,
~org-delete-indentation~, and ~org-return~.  Keeping the value nil, will
change the default behavior when typing/deleting inside headline, in
~org-mobile-edit~, ~org-insert-heading~, ~org-edit-headline~,
~org-priority~, ~org-entry-put~, ~org-kill-line~.

Or maybe should we keep the status quo with ~org-auto-align-tags~
sometimes respected and sometimes not?

>From 6f16612796076077c95176be0929677ffe8e0d3d Mon Sep 17 00:00:00 2001
Message-ID: <6f16612796076077c95176be0929677ffe8e0d3d.1713348551.git.yanta...@posteo.net>
From: Ihor Radchenko 
Date: Wed, 17 Apr 2024 13:04:52 +0300
Subject: [PATCH] Respect `org-auto-align-tags' in all the editing commands

* lisp/org-mobile.el (org-mobile-edit):
* lisp/org.el (org-insert-heading):
(org-edit-headline):
(org-priority):
(org-set-tags):
(org-entry-put):
(org-self-insert-command):
(org-delete-backward-char):
(org-delete-char):
(org-kill-line): Only re-align tags when `org-auto-align-tags' is set
to non-nil.
* etc/ORG-NEWS (~org-auto-align-tags~ is not respected universally):
Announce the breaking change.

Link: https://orgmode.org/list/87msxoc3qp.fsf@localhost
---
 etc/ORG-NEWS   | 10 ++
 lisp/org-mobile.el |  2 +-
 lisp/org.el| 20 ++--
 3 files changed, 21 insertions(+), 11 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index e61bd6988..e6dc35f87 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -13,6 +13,16 @@ Please send Org bug reports to mailto:emacs-orgmode@gnu.org.
 
 * Version 9.7 (not released yet)
 ** Important announcements and breaking changes
+*** ~org-auto-align-tags~ is not respected universally
+
+Previously, only a subset of Org editing commands respected
+~org-auto-align-tags~ option.  Now, it is no longer the case.  All the
+editing commands, including typing (~org-self-insert-command~) and
+deletion respect the option.
+
+~org-auto-align-tags~ is still disabled by default.  Now, none of the
+Org editing commands re-align tags to ~org-tags-column~ by default.
+
 *** Underline syntax now takes priority over subscript when both are applicable
 
 Previously, Org mode interpreted =(_text_)= as subscript.
diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el
index 83e0316fd..b34623686 100644
--- a/lisp/org-mobile.el
+++ b/lisp/org-mobile.el
@@ -1057,7 +1057,7 @@ (defun org-mobile-edit (what old new)
 	  (goto-char (match-beginning 4))
 	  (insert new)
 	  (delete-region (point) (+ (point) (length current)))
-	  (org-align-tags))
+	  (when org-auto-align-tags (org-align-tags)))
 	 (t
 	  (error
 	   "Heading changed in the mobile device and on the computer")))
diff --git a/lisp/org.el b/lisp/org.el
index a53f36d33..c4475cd62 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -6565,7 +6565,7 @@ (defun org-insert-heading ( arg invisible-ok level)
 	 ;; Preserve tags.
 	 (let ((split (delete-and-extract-region (point) (match-end 4
 	   (if (looking-at "[ \t]*$") (replace-match "")
-		 (org-align-tags))
+		 (when org-auto-align-tags (org-align-tags)))
 	   (end-of-line)
 	   (when blank? (insert "\n"))
 	   (insert "\n" stars " ")
@@ -6677,7 +6677,7 @@ (defun org-edit-headline ( heading)
 	   (if old (replace-match new t t nil 4)
 	 (goto-char (or (match-end 3) (match-end 2) (match-end 1)))
 	 (insert " " new))
-	   (org-align-tags)
+	   (when org-auto-align-tags (org-align-tags))
 	   (when (looking-at "[ \t]*$") (replace-match ""
 
 (defun org-insert-heading-after-current ()
@@ -11215,7 +11215,7 @@ (defun org-priority ( action show)
 		  (insert " [#" news "]"))
 	  (goto-char (match-beginning 3))
 	  (insert "[#" news "] "
-	(org-align-tags))
+	(when org-auto-align-tags (org-align-tags)))
   (if remove
 	  (message "Priority removed")
 	(message "Priority of current item set to %s" news)
@@ -12021,7 +12021,7 @@ (defun org-set-tags (tags)
 	  

Re: PATCH allow explicit style= in #+cite_export: biblatex

[Pedro Andres Aranda Gutierrez]

Stop the press... I discovered a small bug in the last patch.
Attached is a new version.

/PA

On Wed, 17 Apr 2024 at 08:22, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:

> Hi again
>
> Rationale of the patch:
> Currently, when the options to biblatex are _not_ xxx/xxx format, a style=
> is prepended, because
> it is assumed that it will be a biblatex options string starting with a
> style.
> With the proposed patch, I add the possibility of using a biblatex options
> string where style= is stated
> explicitly (anywhere in the string). This adds congruency WRT
> the ~org-cite-biblatex-options~ variable.
>
> Best, /PA
>
> On Sun, 14 Apr 2024 at 09:16, Pedro Andres Aranda Gutierrez <
> paag...@gmail.com> wrote:
>
>> HI, full answer...
>>
>> In the original code, that section prepends "style=" in some cases. I
>> have stumbled across
>> instances where the options started with style= because they were taken
>> directly from LaTeX
>> and the generated code ended by like:
>> \usepackage[style=style=numeric,backend=biber]{biblatex}
>> for
>> #+cite_export: biblatex style=numeric,backend=biber
>> which, BTW, is something someone used the LaTeX may parse as correct.
>> I was just trying to cater for this case.
>>
>> Best, /PA
>>
>>
>> On Sun, 14 Apr 2024 at 07:30, Pedro Andres Aranda Gutierrez <
>> paag...@gmail.com> wrote:
>>
>>> Sorry... I was not right... You are right. I'll take a look at it again.
>>> /PA
>>>
>>> On Sun, 14 Apr 2024 at 07:22, Pedro Andres Aranda Gutierrez <
>>> paag...@gmail.com> wrote:
>>>
 Hi,

 Maybe not... because style= is a keyword for the biblatex package,
 while bibstyle or citestyle aren't.

 Best, /PA

 On Sat, 13 Apr 2024 at 16:32, Ihor Radchenko 
 wrote:

> Pedro Andres Aranda Gutierrez  writes:
>
> > HI,
> > Attached is a small patch to allow explicitly adding style= in the
> biblatex export options, to increase consistency with
> > Customisation variables.
>
> Thanks!
>
> >  (style-options
> >   (cond
> >((null style) nil)
> > +  ;; allow the user to include "style=" anywhere in the
> style options
> > +  ((string-match "\\(^s\\|,s\\)tyle=" style) (list style))
> >((not (string-match "/" style)) (list (concat "style="
> style)))
> >(t
> > (list (concat "bibstyle=" (substring style nil
> (match-beginning 0)))
>
> If we allow style=..., may as well allow bibstyle= and citestyle=.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>


 --
 Fragen sind nicht da, um beantwortet zu werden,
 Fragen sind da um gestellt zu werden
 Georg Kreisler

 Headaches with a Juju log:
 unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
 run a leader-deposed hook here, but we can't yet


>>>
>>> --
>>> Fragen sind nicht da, um beantwortet zu werden,
>>> Fragen sind da um gestellt zu werden
>>> Georg Kreisler
>>>
>>> Headaches with a Juju log:
>>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>>> run a leader-deposed hook here, but we can't yet
>>>
>>>
>>
>> --
>> Fragen sind nicht da, um beantwortet zu werden,
>> Fragen sind da um gestellt zu werden
>> Georg Kreisler
>>
>> Headaches with a Juju log:
>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>> run a leader-deposed hook here, but we can't yet
>>
>>
>
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Headaches with a Juju log:
> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
> a leader-deposed hook here, but we can't yet
>
>

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
From 82f1cecaf5c011506c6cc57cb3835b6f8eba0f6d Mon Sep 17 00:00:00 2001
From: "Pedro A. Aranda" 
Date: Wed, 17 Apr 2024 08:19:22 +0200
Subject: [PATCH 1/2] Allow explicit style= in cite_export options

lisp/oc-biblatex.el: Allow explicit style= in biblatex cite-export
doc/org-manual.org: Clarify documentation regarding biblatex cite-export

---
 doc/org-manual.org  | 10 +-
 lisp/oc-biblatex.el | 31 +--
 2 files changed, 26 insertions(+), 15 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 6c699ae1e..2de5df3af 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -17614,7 +17614,15 @@ style and the =bibtex= backend. Always define the style first and then
 the rest of 

Re: PATCH allow explicit style= in #+cite_export: biblatex

[Pedro Andres Aranda Gutierrez]

Hi again

Rationale of the patch:
Currently, when the options to biblatex are _not_ xxx/xxx format, a style=
is prepended, because
it is assumed that it will be a biblatex options string starting with a
style.
With the proposed patch, I add the possibility of using a biblatex options
string where style= is stated
explicitly (anywhere in the string). This adds congruency WRT
the ~org-cite-biblatex-options~ variable.

Best, /PA

On Sun, 14 Apr 2024 at 09:16, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:

> HI, full answer...
>
> In the original code, that section prepends "style=" in some cases. I have
> stumbled across
> instances where the options started with style= because they were taken
> directly from LaTeX
> and the generated code ended by like:
> \usepackage[style=style=numeric,backend=biber]{biblatex}
> for
> #+cite_export: biblatex style=numeric,backend=biber
> which, BTW, is something someone used the LaTeX may parse as correct.
> I was just trying to cater for this case.
>
> Best, /PA
>
>
> On Sun, 14 Apr 2024 at 07:30, Pedro Andres Aranda Gutierrez <
> paag...@gmail.com> wrote:
>
>> Sorry... I was not right... You are right. I'll take a look at it again.
>> /PA
>>
>> On Sun, 14 Apr 2024 at 07:22, Pedro Andres Aranda Gutierrez <
>> paag...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Maybe not... because style= is a keyword for the biblatex package, while
>>> bibstyle or citestyle aren't.
>>>
>>> Best, /PA
>>>
>>> On Sat, 13 Apr 2024 at 16:32, Ihor Radchenko 
>>> wrote:
>>>
 Pedro Andres Aranda Gutierrez  writes:

 > HI,
 > Attached is a small patch to allow explicitly adding style= in the
 biblatex export options, to increase consistency with
 > Customisation variables.

 Thanks!

 >  (style-options
 >   (cond
 >((null style) nil)
 > +  ;; allow the user to include "style=" anywhere in the
 style options
 > +  ((string-match "\\(^s\\|,s\\)tyle=" style) (list style))
 >((not (string-match "/" style)) (list (concat "style="
 style)))
 >(t
 > (list (concat "bibstyle=" (substring style nil
 (match-beginning 0)))

 If we allow style=..., may as well allow bibstyle= and citestyle=.

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

>>>
>>>
>>> --
>>> Fragen sind nicht da, um beantwortet zu werden,
>>> Fragen sind da um gestellt zu werden
>>> Georg Kreisler
>>>
>>> Headaches with a Juju log:
>>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>>> run a leader-deposed hook here, but we can't yet
>>>
>>>
>>
>> --
>> Fragen sind nicht da, um beantwortet zu werden,
>> Fragen sind da um gestellt zu werden
>> Georg Kreisler
>>
>> Headaches with a Juju log:
>> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
>> run a leader-deposed hook here, but we can't yet
>>
>>
>
> --
> Fragen sind nicht da, um beantwortet zu werden,
> Fragen sind da um gestellt zu werden
> Georg Kreisler
>
> Headaches with a Juju log:
> unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
> a leader-deposed hook here, but we can't yet
>
>

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
From 82f1cecaf5c011506c6cc57cb3835b6f8eba0f6d Mon Sep 17 00:00:00 2001
From: "Pedro A. Aranda" 
Date: Wed, 17 Apr 2024 08:19:22 +0200
Subject: [PATCH] Allow explicit style= in cite_export options

lisp/oc-biblatex.el: Ckech whether the biblatex options include style= explicitly.
doc/org-manual.org: Clarify this in the documentation.


---
 doc/org-manual.org  | 10 +-
 lisp/oc-biblatex.el | 31 +--
 2 files changed, 26 insertions(+), 15 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 6c699ae1e..2de5df3af 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -17614,7 +17614,15 @@ style and the =bibtex= backend. Always define the style first and then
 the rest of load-time options for the =biblatex=
 package. Alternatively, use the ~org-cite-biblatex-options~ variable
 in your Emacs configuration. It will only export to PDF, since it
-relies on the ~biblatex~ processor of your LaTeX installation;
+relies on the ~biblatex~ processor of your LaTeX installation.
+
+The previous example assumes the first element in the options is a
+style.  Alternatively you can specify ~style=~ explicitly anywhere in
+the options string (as you would when setting the
+~org-cite-biblatex-options~ variable in your Emacs configuration):
+
+: #+cite_export: biblatex 

Re: [BUG] crash [9.7-pre (release_9.6.11-927-g819cd7 @ /home/minshall/.emacs.d/straight/build/org/)]

[Greg Minshall]

Ihor,

> You are on a fairly old common from main - 5 month old.
> May you upgrade to the latest main and let us know if you keep seeing 
> problems?

thanks.  i've re-freshed and re-built and am now on

Org mode version 9.7-pre (release_9.6.26-1368-g1ae978 @ 
/home/minshall/.emacs.d/straight/build/org/)


if i see another problem, i will let you know.

cheers, Greg