Re: [PATCH] Accept nil outline path for file+olp+datetree org-capture-templates target

[Kristoffer Balintona]

Thanks for the bump. Life stuff popped up and I got distracted by other
hacking too.

On Thu, Jun 19 2025, Ihor Radchenko wrote:

> Ihor Radchenko  writes:
>
>>> Thank you for the clarification. WDYT of the patches attached?
>>
>> See my comments below.
>> ...
>
> It has been a month.
> Kristoffer, did you have a chance to look into my comments?

I did, yes. I want to confirm because I wasn't quite sure which
direction you were trying to nudge me toward: would you like me to
ensure that the behavior introduced by the patch works well with
:prepend?

If that's the case, then is the following the expected  behavior:
1. For all three target specifications, if :prepend is nil or omitted
  and the olp (for file+olp and file+olp+datetree) or headline (for
  file+headline) is nil or omitted, insert the new entry at the end of
  the . (Already done.)
2. However, if :prepend is t and the olp/headline is omitted, insert the
  new entry such that it is the first headline in the . (Or,
  for file+olp+datetree, insert the datetree such that it's beginning is
  the first headline.) (Not implemented.)
3. If the olp/headline is not omitted from the target spec, then behave
  like current org does for both :prepend nil and :prepend t. (Done.)

If the above is accurate, I'll work on a new version of the patch. Would
you recommend setting :exact-position to achieve 2, or would that get in
the way of other org-capture features?

-- 
Kind regards,
Kristoffer

feature/all-tex-fonts

[Pedro Andres Aranda Gutierrez]

Hi again

I have made a substantial cleanup in the feature branch. It includes
restoring the original language guessing routines for documents prior
to (org-latex-multi-lang-driver).

A bit of background:
The new (org-latex-multi-lang-driver) variable controls how the
headers are generated.
The default value (nil) activates the behaviour we have in main.
Other values can be t,"polyglossia" or "babel", which in conjunction
with (org-latex-compiler) and the different font configuration
variables will generate the language configuration part of the LaTeX
header.

I'd like to thank people how have tested through the process and would
like to encourage other people to take a look and provide feedback,
including things missing

Best, /PA

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

Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy

Re: [BUG] Double slash in body text not captured in Org Protocol [9.7.30 (9.7.30-84f18c @ /Users/cchoi/.config/emacs/elpa/org-9.7.30/)]

[Max Nikulin]

[...]

Double slash in body text not captured in Org Protocol URL
   emacsclient "org-protocol://capture?body=org-protocol://"
...
Only one slash appears in the resulting Org Capture window.


On 19/06/2025 23:00, Ihor Radchenko wrote:

Max Nikulin writes:

Released version supports `server-eval-args-left' that makes hacks with
an advice for `server-visit-files' and passing URL as file name relative
to emacsclient working directory unnecessary.


Do you mean that we can somehow use `server-eval-args-left' to fix the
bug reporting by Charles?


Certainly. This server.el feature was introduced to handle "mailto:"; 
URLs. Arguments of --eval are not treated as file names and are passed 
literally. emacsclient-mail.desktop never used advice similar to 
org-protocol, but they passed through all issues related to portability 
and security vulnerabilities trying to convert URL into safe elisp 
string. Fortunately that shell code is not used any more.


Likely functions in org-protocol.el require some modifications for more 
direct handling of arguments.

org-persist causes delay when terminating emacs

[mahmood sheikh]

this is related to
https://lists.gnu.org/archive/html/emacs-orgmode/2025-03/msg00166.html
i make heavy usage of the new org-latex-preview (not sure if its related)
the profiler report upon exiting (using `(add-hook 'kill-emacs-hook 'debug
99)`) is included in this email.
this isnt new, but i couldnt possibly say since when the issue started.
thanks


report
Description: Binary data

Re: [BUG] Org parser error [9.7.11 (release_9.7.11 @ /usr/local/Cellar/emacs/30.1/share/emacs/30.1/lisp/org/)]

[Ihor Radchenko]

"George Dunlap"  writes:

> No, I've never seen anything like this before; and I haven't seen the issue 
> since (or I would have posted an update to the thread).
>
> I've installed the newest package, and I'll report any further problems.  
> Feel free to consider this closed / fallow / whatever.

Thanks for the update!
Canceled.

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

Re: [PATCH] org-element.el; significant optimizations for org-element--interpret-affiliated-keywords

[Ihor Radchenko]

"Dwarshuis, Nathan J"  writes:

>> Another effect of the patch exceeding 15LOC is that I now need you to go
>> through the copyright assignment before I can accept it.
>> Would you be interested to do it?
>> See https://orgmode.org/worg/org-contribute.html#copyright
>
> Yes but let me check a few things first

Now, as your copyright assignment is done, we can continue with the
patch review. I will be waiting for your response to the latest batch of
my comments.

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