I've attached the complete (and working) version for context/feedback.
binBA0QOH1eR0.bin
Description: application/emacs-lisp
I've cleaned it up and turned it into a patch. It now correctly handles
(ignores) buffers without associated file names (which don't work with IDs).
>From 1861637d7b05f2e7ac11edf89f6939145c7be091 Mon Sep 17 00:00:00 2001
From: Steven Allen
Date: Wed, 27 Aug 2025 09:05:08 -0700
Su
Rodolf,
Thanks for the feedback! Here's a fixed version:
(org-link-set-parameters
"id"
:complete
(lambda (&optional _prefix)
(unless org-id-locations (org-id-locations-load))
(when-let* ((id (org-id-get-with-outline-path-completion
'((nil
Samuel Wales writes:
> fyi, the behavior with your form for me is identical to the behavior without
> it.
Ah, sorry, I should have explained how it works:
1. C-c C-l (org-insert-link).
2. At the completion prompt, type "id:" followed by RET.
3. Pick from one of the provided links via completio
I use the following snippet to quickly link to headings by ID with
via org-insert-link. If there's any interest, I'm happy to clean this
up and submit a patch but I figured I'd ask first.
(org-link-set-parameters
"id"
:complete
(lambda (&optional _prefix)
(unless org-id-locat
Suhail Singh writes:
> Steven Allen writes:
>
>> The concern is that, e.g., there may b a function _marked_ as pure
>> that's not actually pure, leaks some information, and/or has a
>> security vulnerability (e.g., a C function exposed to lisp that's
>>
Suhail Singh writes:
> Steven Allen writes:
>
>> 1. While this feature no longer invokes completely arbitrary code, it
>> still allows an attacker to call any function marked as "pure" which
>> is a pretty large attack surface.
>
> I am struggling to a
Suhail Singh writes:
> Ihor Radchenko writes:
>
>> If you are actively using #+LINK: keywords with %(...) placeholders or
>> have any objections to this feature removal, please let us know.
>
> I do not actively use this feature, however, removing it seems
> excessive. IIUC, it's a useful feat
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>> I just released Org mode 9.7.5 that fixes a critical vulnerability.
>> The release is coordinated with emergency Emacs 29.4 release.
>
> This one is another potential issue (or a feature) we have found while
> discussing the main vulnerability
Greg Troxel writes:
> (Thanks for fixing and your efforts on org. I've been an org user since
> at least July of 2010.)
>
> Just to be clear, is this the commit that needs applying to emacs
> sources, 29.3, 28.x, and so on?
Yes, that's the correct commit.
> It seems so, but I would rather not
p 17 00:00:00 2001
From: Steven Allen
Date: Thu, 1 Jun 2023 11:49:19 -0700
Subject: [PATCH] org.el: inline display of attached images in link
descriptions
* lisp/org.el (org-display-inline-images): inline display of attached
images in link descriptions.
Previously, `org-display-inline-images&#x
* lisp/org.el (org-display-inline-images): inline display of attached
images in link descriptions.
Previously, `org-display-inline-images' only inlined images in link
descriptions when they were explicit "file:" links. This change adds
support for "attachment:" links. E.g.:
[[https://orgmode.
12 matches
Mail list logo
