Org mode version 9.8-pre (9.8-pre-n/a-gc2d57d @ /home/n/.emacs.d/elpaca/builds/org/); org-babel-execute:emacs-lisp relies on pp's implicit return value

[No Wayman]

A recent commit on Emacs master branch changes the return value of 
pp:

https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d3311499339fab0371cb7502a1e2481fbcd2c65d
The function does not document a stable return value, either.

This causes babel emacs-lisp source blocks to return "nil" for the 
value. e.g.


#+begin_src emacs-lisp :lexical t :results value code :exports 
both

(list 1 2 3)
#+end_src

#+RESULTS:
#+begin_src emacs-lisp
nil
#+end_src

Emacs  : GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ 
Version 3.24.43, cairo version 1.18.2)

of 2025-01-26
Package: Org mode version 9.8-pre (9.8-pre-n/a-gc2d57d
@ /home/n/.emacs.d/elpaca/builds/org/)

Re: [BUG] Cannot tangle src block in capture buffer [9.7.6]

[Derek Chen-Becker]

I submitted my assignment form this week, but I'm not sure how long it
takes for that to get processed. In the meantime, I'm attaching the latest
version of my patches for capture buffer tangling, updated with feedback.
If there are any other suggestions or concerns with the patches I can
address them while we wait on assignment.

Thanks,

Derek

On Sat, Jan 18, 2025 at 7:44 AM Ihor Radchenko  wrote:

> Derek Chen-Becker  writes:
>
> > I'm still sorting out the copyright assignment, but I have another style
> > question: It feels like I should move the `should' clauses closer to the
> > checks so that I get a more concise report when something is wrong:
> > ...
> > Is that OK?
>
> Yes, it is fine. Also, no need to overthink things - as long as the test
> is readable, we should be good.
>
> --
> Ihor Radchenko // yantar92,
> Org mode maintainer,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>


-- 
+---+
| Derek Chen-Becker |
| GPG Key available at https://keybase.io/dchenbecker and   |
| https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org |
| Fngrprnt: EB8A 6480 F0A3 C8EB C1E7  7F42 AFC5 AFEE 96E4 6ACC  |
+---+


0001-testing-README-Add-details-on-use-of-TEST_NO_AUTOCLE.patch
Description: Binary data


0002-ob-tangle-Ensure-proper-tangling-within-a-capture-bu.patch
Description: Binary data

Re: Feature request: Export to text file with no line wrapping

[Ihor Radchenko]

Ihor Radchenko  writes:

> Morten Kjeldgaard  writes:
>
>> The subject says it, it would be very nice if there was an export option 
>> to export to text mode without wrapping paragraphs,so the resulting text 
>> file can be read with visual-line-mode on.
>
> See org-export-preserve-breaks. Does it do what you want?

I assume that it does.
Canceled.

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

Re: Customize list of blocks that use "\footnotemark" in `org-latex-footnote-reference'

[Ihor Radchenko]

Ihor Radchenko  writes:

>>> I am exporting an Org file that contains a large verse block to
>>> LaTeX. This verse block contains footnotes, but they appear in the page
>>> where the LaTeX verse environment ends. I looked at the exported .tex
>>> file and I noticed that it was using "\footnotemark" and
>>> "\footnotetext[N]{...}", instead of "\footnote{...}".
>> ...
>> I seem to remember that the problem you describe goes back to how Org
>> understood the footnote text. When exporting to LaTeX, each line of a
>> footnote was understood as if it were a verse, and Org added \\ at the
>> end. Hence the use of \footnotemark and the
>> ‘org-latex--delayed-footnotes-definitions’ function.
>
> Please try the attached tentative fix.
> I limited special verse contents processing to plain-text directly
> inside verse blocks (as in Org AST), except plain text inside inline
> footnote definitions.

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

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

Re: Noisy and unreliable (de-)tangling

[Rudolf Adamkovič]

Rudolf Adamkovič  writes:

> Actually, I found a problem: If I add a new Emacs Lisp code block to my
> literate Emacs configuration, Emacs launches with a blank screen,
> asking:
>
>   Buffer ... modified; kill anyway? (yes, no, save and then kill, ?):

With clocks, it gets even weirder:

Org asks whether to clock out on launch. :)

Rudy
-- 
"I have only made this letter longer because I have not had the time to make it 
shorter."
--- Blaise Pascal, The Provincial Letters, 1657

Rudolf Adamkovič  [he/him]
http://adamkovic.org

Re: [BUG] org-gnus-follow-link tries to select dead frame [9.8-pre (release_9.7.15-163-g3ff21c.dirty @ /home/bidar/.local/etc/emacs/lib/org/lisp/)]

[Ihor Radchenko]

Björn Bidar  writes:

>>> * Preconditions
>>> - gnus-other-frame-object is a dead frame
>>
>> May you please describe when `gnus-other-frame-object' could become a
>> dead frame?
>
> I assume when  the frame that is in the object was closed.
>
> E.g. for example to trigger this state again I closed the Gnus frame I
> was writing this reply in.  Afterwards the frame is dead.

Then, why not simply the attached patch?

>From 73bb83c67dbda24c7b4455073482020b5e4e357b Mon Sep 17 00:00:00 2001
Message-ID: <73bb83c67dbda24c7b4455073482020b5e4e357b.1738513362.git.yanta...@posteo.net>
From: Ihor Radchenko 
Date: Sun, 2 Feb 2025 17:20:50 +0100
Subject: [PATCH] ol-gnus: Do not err when gnus frame is dead
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* lisp/ol-gnus.el (org-gnus-follow-link): Do not try to switch to dead
frame.

Reported-by: Björn Bidar 
Link: https://list.orgmode.org/orgmode/87o6zn4m40.fsf@/
---
 lisp/ol-gnus.el | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/lisp/ol-gnus.el b/lisp/ol-gnus.el
index 5cddc3790a..ac2cadbc66 100644
--- a/lisp/ol-gnus.el
+++ b/lisp/ol-gnus.el
@@ -228,7 +228,9 @@ (defun org-gnus-follow-link (&optional group article)
   "Follow a Gnus link to GROUP and ARTICLE."
   (require 'gnus)
   (funcall (org-link-frame-setup-function 'gnus))
-  (when gnus-other-frame-object (select-frame gnus-other-frame-object))
+  (when (and gnus-other-frame-object
+ (frame-live-p gnus-other-frame-object))
+(select-frame gnus-other-frame-object))
   (let ((group (org-no-properties group))
 	(article (org-no-properties article)))
 (cond
-- 
2.47.1


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

[PATCH] Improve the clock-out message

[Rudolf Adamkovič]

* lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
out and save?" message to "Clock out before saving?" to convey the
important fact that no data will be lost when answered "no".
---
 lisp/org-clock.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 5fd0580d0..f10d7f339 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -3316,7 +3316,7 @@ The details of what will be saved are regulated by the 
variable
   "Query user when killing Emacs.
 This function is added to `kill-emacs-query-functions'."
   (let ((buf (org-clocking-buffer)))
-(when (and buf (yes-or-no-p "Clock out and save? "))
+(when (and buf (yes-or-no-p "Clock out before saving? "))
   (with-current-buffer buf
 (org-clock-out)
 (save-buffer
-- 
2.48.1

Re: [PATCH] Improve the clock-out message

[Rudolf Adamkovič]

Rudolf Adamkovič  writes:

> * lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
> out and save?" message to "Clock out before saving?" to convey the
> important fact that no data will be lost when answered "no".

I forgot to prefix the commit title with the package name.

See the attached v2.

P.S. This message has been making me confused ever since I started using
Org, and it still makes me pause and think today, hence the patch.

Rudy
>From c8d7e985f728d38e7eff3c5eaa4db0f0171f90a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?= 
Date: Sun, 2 Feb 2025 09:14:49 +0100
Subject: [PATCH] org-clock: Improve the clock-out message

* lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
out and save?" message to "Clock out before saving?" to convey the
important fact that no data will be lost when answered "no".
---
 lisp/org-clock.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 5fd0580d0..f10d7f339 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -3316,7 +3316,7 @@ The details of what will be saved are regulated by the variable
   "Query user when killing Emacs.
 This function is added to `kill-emacs-query-functions'."
   (let ((buf (org-clocking-buffer)))
-(when (and buf (yes-or-no-p "Clock out and save? "))
+(when (and buf (yes-or-no-p "Clock out before saving? "))
   (with-current-buffer buf
 (org-clock-out)
 (save-buffer
-- 
2.39.5 (Apple Git-154)

-- 
"I would prefer an intelligent hell to a stupid paradise."
--- Blaise Pascal

Rudolf Adamkovič  [he/him]
http://adamkovic.org

Re: insert a header and automatically a timestamp with date/time

[General discussions about Org-mode.]

> On 2025-02-02 08:38, Uwe Brauer via General discussions about Org-mode. 
> wrote:
> Yes :D
>    but let's keep the discussion in the mailinglist in English so other 
> people can participate, or benefit from it


Sure!

> In fact you don't need ~my/get-inactive-timestamp~ for your pursposes, 
> try with this one:

> #+begin_src emacs-lisp
> (defun my/org-add-timestamp-on-heading ()
>    (save-excursion
>      (org-back-to-heading)
>      (org-edit-headline (format-time-string "<%F>"

> (add-hook 'org-insert-heading-hook 'my/org-add-timestamp-on-heading 'append)
> ;; to remove it
> ;; (remove-hook 'org-insert-heading-hook 'my/org-add-timestamp-on-heading)
> #+end_src

I did this already 😉 thanks

Actually I used 
(defun my/org-add-timestamp-on-heading ()
  (save-excursion
(org-back-to-heading)
(org-edit-headline (format-time-string "<%Y-%m-%d %H:%M>")))
  (insert " "))

(add-hook 'org-insert-heading-hook 'my/org-add-timestamp-on-heading 'append)




> but here you have for curiosity, there you can see compact strftime 
> format to construct a inactive timestamp

> [1]

> #+begin_src emacs-lisp
> (defun my/get-inactive-timestamp ()
>    (format-time-string "[%F %a %R]"))

> (defun my/set-property-with-inactive-timestamp (property)
>    (interactive)
>    (org-set-property property (my/get-inactive-timestamp)))
> #+end_src

Thanks, I try that out.


A last question though.

Now if I want my headings look like 

* <2025-02-02 08:58> Second entry 

* <2025-02-02 08:53> First 

* <2025-02-02 08:56> third 



Is there any way to sort these heading with respect to the timestamps from 
oldes to newest?

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 



smime.p7s
Description: S/MIME cryptographic signature

Re: insert a header and automatically a timestamp with date/time

[pinmacs]

On 2025-02-02 21:02, Uwe Brauer via General discussions about Org-mode. 
wrote:

A last question though.

Now if I want my headings look like

* <2025-02-02 08:58> Second entry

* <2025-02-02 08:53> First

* <2025-02-02 08:56> third



Is there any way to sort these heading with respect to the timestamps from 
oldes to newest?


I'm glad it works for you :)

You need a parent entry (see how I added example). From that parent 
entry, do M-x org-sort and select alphanumeric (a), and that sorts fine 
the timestamps; you will see that there are other ways to sort entries, 
the one I use today is scheduled (s).



* example

** <2025-02-02 08:53> First

** <2025-02-02 08:56> third

** <2025-02-02 08:58> Second entry

Bug: octave newline not printed when using :session [9.8-pre (release_9.7.18-205-g0ce4f3)]

[Paul Stansell]

Hello,

The attached org file gives an example of output from an octave code block
that is unexpected and inconsistent.  The problem is that disp("\n") does
not print a new line.  The problem only occurs when the ":session" header
is used.

Paul




Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.33, cairo version 1.16.0)
 of 2024-09-17, modified by Debian
Package: Org mode version 9.8-pre (release_9.7.18-205-g0ce4f3.dirty @
~/.emacs.d_org_from_git/org-mode-git/lisp/)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-link-shell-confirm-function 'yes-or-no-p
 org-sort-function 'string-collate-lessp
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-persist-directory "/tmp/org-persist-J74MUs"
 org-persist-before-write-hook '(org-element--cache-persist-before-write)
 org-mode-hook '(#[0 "\300\301\302\303\304$\207"
  [add-hook change-major-mode-hook org-fold-show-all append
   local]
  5]
#[0 "\300\301\302\303\304$\207"
  [add-hook change-major-mode-hook org-babel-show-result-all
   append local]
  5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-persist-before-read-hook '(org-element--cache-persist-before-read)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-persist-after-read-hook '(org-element--cache-persist-after-read)
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-babel-pre-tangle-hook '(save-buffer)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
 org-babel-header-arg-expand)
 org-babel-load-languages '((octave . t))
 org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe
   org-babel-header-arg-expand)
 org-agenda-loop-over-headlines-in-active-region nil
 org-fold-core-isearch-open-function 'org-fold--isearch-reveal
 org-occur-hook '(org-first-headline-recenter)
 org--warnings nil
 org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-show-empty-lines
 org-cycle-optimize-window-after-visibility-change
 org-cycle-display-link-previews)
 org-speed-command-hook '(org-speed-command-activate
 org-babel-speed-command-activate)
 org-yank-image-file-name-function 'org-yank-image-autogen-filename
 org-export-before-parsing-hook '(org-attach-expand-links)
 org-confirm-shell-link-function 'yes-or-no-p
 org-link-parameters '(("attachment" :follow org-attach-follow :complete
org-attach-complete-link :preview
org-attach-preview-file)
  ("id" :follow org-id-open :store
org-id-store-link-maybe)
  ("eww" :follow org-eww-open :store org-eww-store-link)
  ("rmail" :follow org-rmail-open :store
org-rmail-store-link)
  ("mhe" :follow org-mhe-open :store org-mhe-store-link)
  ("irc" :follow org-irc-visit :store org-irc-store-link
:export org-irc-export)
  ("info" :follow org-info-open :export org-info-export
:store org-info-store-link :insert-description
org-info-description-as-command)
  ("gnus" :follow org-gnus-open :store
org-gnus-store-link)
  ("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
  ("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
  ("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
  ("w3m" :store org-w3m-store-link)
  ("doi" :follow org-link-doi-open :export
org-link-doi-export)
  ("file+sys") ("file+emacs")
  ("shell" :follow org-link--open-shell)
  ("news" :follow
#[514 "\301\300\302 Q \"\207"
 ["news" browse-url ":"] 6 "\n\n(fn URL ARG)"]
)
  ("mailto" :follow
#[514 "\301\300\302 Q \"\207"
 ["mailto" browse-url ":"] 6 "\n\n(fn URL ARG)"]
)
  ("https" :follow
#[514 "\301\300\302 Q \"\207"
 ["https" browse-url ":"] 6 "\n\n(fn URL ARG)"]
)
  ("http" :follow
#[514 "\301\300\302 Q \"\207"
 ["http" browse-url ":"] 6 "\n\n(fn URL ARG)"]
)
  ("ftp" :follow
#[514 "\301\300\302 Q \"\207" ["ftp" browse-url ":"]
 6 "\n\n(fn URL ARG)"]
)
  ("help" :follow org-link--open-help :store
org-link--store-help)
  ("file" :complete org-link-complete-file :preview
org-link-preview-file)
  ("elisp" :follow org-link--open-elisp))
 org-link-elisp-confirm-function 'yes-or-no-p
 org-confirm-babel-evaluate nil
 )
-- 
Paul


bug.org
Description: Binary data

[PATCH] Have org-string-width's temporary buffer be declared as such

[Jules Tamagnan]

Hi all,

I hope this email finds you well. This is my first time contributing to
this mailing list attempting to contribute to org-mode, so hopefully I
do this correctly.

I recently noticed that `org-string-width` ran all buffer hooks like
`buffer-list-update-hook` for the ` *Org string width*` buffer. This
doesn't seem needed because it feels like ` *Org string width*` should
act like a temporary buffer that is only needed for these simple
operations. With that in mind I wanted to set `inhibit-buffer-hooks` to
`t`.

Hopefully this rationale and patch makes sense. After getting this in I
can also review other places that `get-buffer-create` is used and
possible use `inhibit-buffer-tools` there as well if it would help.

Best,
Jules

>From cc8dc0a9d8d4b72f2a820dd901b6ddcb9727b9fb Mon Sep 17 00:00:00 2001
From: Jules Tamagnan 
Date: Fri, 31 Jan 2025 11:36:13 -0800
Subject: [PATCH] Have org-string-width's temporary buffer be declared as such

---
 lisp/org-macs.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-macs.el b/lisp/org-macs.el
index 044c49efb..9d35857e2 100644
--- a/lisp/org-macs.el
+++ b/lisp/org-macs.el
@@ -1199,7 +1199,7 @@ STRING width.  When REFERENCE-FACE is nil, `default' face is used."
  (push el result)))
  result)))
   (current-char-property-alias-alist char-property-alias-alist))
-  (with-current-buffer (get-buffer-create " *Org string width*")
+  (with-current-buffer (get-buffer-create " *Org string width*" t)
 (setq-local display-line-numbers nil)
 (setq-local line-prefix nil)
 (setq-local wrap-prefix nil)
--
2.47.1

Re: [PATCH] Autoload org-link-set-parameters

[Joseph Turner]

Max Nikulin  writes:

> Sorry if I confused everything. Does it mean that loading of mu4e will
> cause immediate loading of ol and so whole org? Is it acceptable to use
> `with-eval-after-load' in packages?

Thanks for bringing this up.  AFAICT, requiring mu4e already loads all
of org.  It probably shouldn't.  Perhaps we can put the mu4e-org.el
integration logic behind a minor mode.

Thank you!

Joseph

Re: [BLOG] #15 [[bbb:OrgMeetup]] on Wed, Jan 8, 19:00 UTC+3

[Ihor Radchenko]

Zororg via "General discussions about Org-mode." 
writes:

>>   - common arguments are listed in a dedicated wiki page
>
>> https://orgmode.org/worg/org-tutorials/org-lookups.html
>
> This link seems unrelated. If I'm not wrong the expected link was
> https://orgmode.org/worg/topics/how-many-files.html ?

Yup, you are right.

And I forgot to mention that sub-topic about advanced usage of Org tables
we discussed at the end. org-lookups.html link is about that topic - we
provide a set of Elisp functions that can be used to filter and
summarize table fields.

> Also additionally to refer previous discussion posts on r/orgmode
> https://old.reddit.com/r/orgmode/search?q=single+file&restrict_sr=on&sort=relevance&t=all
>
>> - (feel free to add new things to that page - it is a wiki; wee
>>   https://orgmode.org/worg/worg-about.html on how to contribute)
>
> Although to add my opinion, I do maintain single big org file,
> since leveraging tags and properties provide so much benefits in
> filtering (sparse-tree), searching and narrowing

Would you be interested to take 
https://orgmode.org/worg/topics/how-many-files.org
and add this information there?

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

#16 [[bbb:OrgMeetup]] on Wed, Feb 12, 19:00 UTC+3

[Ihor Radchenko]

Dear all,

Another OrgMeetup will be scheduled on the second Wednesday of February,
in 10 days.

 *Note that we are back to using BBB server for the meetup (thanks to
  Sacha Chua)*

Previous meetup notes:
https://list.orgmode.org/87y0ysb20i.fsf@localhost/T/#u

WORG page with earlier notes and meetup schedule:
https://orgmode.org/worg/orgmeetup.html

URL: https://bbb.emacsverse.org/rooms/orgmeetup/join
Time & Date: <2025-02-12 Wed 19:00-21:00 @+03,Europe/Istanbul>

During the meetup, we can:

- Give advice to new users
- Showcase Org configs or workflows
- Demo/discuss interesting packages
- Troubleshoot each-other's issues
- Discuss Org mode development
- Discuss "Org mode" section of Emacs news (https://sachachua.com/blog/)
- Discuss anything else Org-related

Everyone is free to join the discussion/chat or lurk around silently,
listening.

We will _not_ do any recording by default.

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

Re: [PATCH] Improve the clock-out message

[Kévin Le Gouguec]

Rudolf Adamkovič  writes:

> Rudolf Adamkovič  writes:
>
>> * lisp/org-clock.el (org-clock-kill-emacs-query): Reword the "Clock
>> out and save?" message to "Clock out before saving?" to convey the
>> important fact that no data will be lost when answered "no".
>
> I forgot to prefix the commit title with the package name.
>
> See the attached v2.
>
> P.S. This message has been making me confused ever since I started using
> Org, and it still makes me pause and think today, hence the patch.

Seconded, thanks for taking the time to tweak this!  I sometime clock in
to some task that may require restarting Emacs (or the DE session, or
the computer); the message no longer gives me pause but it would be good
to spare future users.

One question: should it be "before saving" or "before exiting"?

* My usage pattern is "clock in; save; exit", so the buffer is already
saved;
* also, if I'm reading save-buffers-kill-emacs right, the
-query-functions are run _after_ the save prompts?

Re: insert a header and automatically a timestamp with date/time

[pinmacs]

On 2025-02-02 08:38, Uwe Brauer via General discussions about Org-mode. 
wrote:

Vale, entendido (supongo que eres español, porque usas la palabra movil,
¿correcto?)

Yes :D
  but let's keep the discussion in the mailinglist in English so other 
people can participate, or benefit from it

Thanks, but I cannot find the function

my/set-property-with-inactive-timestamp

In your code,


In fact you don't need ~my/get-inactive-timestamp~ for your pursposes, 
try with this one:


#+begin_src emacs-lisp
(defun my/org-add-timestamp-on-heading ()
  (save-excursion
    (org-back-to-heading)
    (org-edit-headline (format-time-string "<%F>"

(add-hook 'org-insert-heading-hook 'my/org-add-timestamp-on-heading 'append)
;; to remove it
;; (remove-hook 'org-insert-heading-hook 'my/org-add-timestamp-on-heading)
#+end_src

but here you have for curiosity, there you can see compact strftime 
format to construct a inactive timestamp


[1]

#+begin_src emacs-lisp
(defun my/get-inactive-timestamp ()
  (format-time-string "[%F %a %R]"))

(defun my/set-property-with-inactive-timestamp (property)
  (interactive)
  (org-set-property property (my/get-inactive-timestamp)))
#+end_src

Re: I'm giving a FOSDEM talk on Org Mode

[L.C. Karssen]

Hi Amy,

That sounds awesome! Unfortunately, I couldn't attend FOSDEM on 
Saturday. Do you know if your talk has been recorded? It would be great 
if we could watch it later.



Best regards,

Lennart.

On 30-01-2025 11:31, Amy Grinn wrote:


Hello all,

I hope you can join me in person or online at the Tool the Docs devroom
at FOSDEM! I will be giving a talk about how Org mode and Emacs is used
at Spritely.

https://fosdem.org/2025/schedule/event/fosdem-2025-5139-org-mode-witchcraft-at-spritely/

It will be Saturday at 10:30 AM CET.

Re: [BUG] Texinfo: Error when exporting source block with no language

[Ihor Radchenko]

Ihor Radchenko  writes:

>> I am using Org mode version 9.6.15 in GNU Emacs 29.4.
>
> Have you tried Org 9.7?

Canceled.
Most likely, this has been fixed already.
See https://list.orgmode.org/orgmode/87ikrdtf8u@gmail.com/

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