Dear Org maintainers,
I've noticed that when a repeating task is toggled from DONE back to TODO
(or when the repeater is triggered), the =*Messages*= buffer receives a
large amount of text‑property noise. After investigation, I traced the
issue to a debugging =print= statement left in the function
=org-auto-repeat-maybe= .
Specifically, the line:
#+begin_src elisp
(print (list has-start-time (org-current-line-string)))
#+end_src
appears inside the loop that processes timestamps with repeaters. This
=print= outputs the current line string with all its text properties,
resulting in messages like:
#+begin_example
(0 #("SCHEDULED: <2026-08-12 Wed 16:00 .+1d>" 0 10 (face ...) ...))
#+end_example
This is clearly not intended for normal usage and should be removed.
*Steps to reproduce:*
1. Have a headline with a repeating timestamp, e.g.:
** TODO Test
SCHEDULED: <2026-08-12 Wed 16:00 .+1d>
2. Change the TODO state to DONE (triggers the repeater).
3. Change it back to TODO (the repeater is processed again).
4. Observe the /Messages/ buffer or the echo area -- you will see the printed
property list.
*Expected behavior:*
Only the normal “Entry repeats: ...” message should appear, without any raw
data structure.
*Environment:*
- Emacs version: GNU Emacs 32.0.50 (build 1, x86_64-w64-mingw32) of 2026-07-16
- Org mode version: Org mode version 10.0-pre (10.0-pre-e186e4 @
c:/Users/riko/AppData/Roaming/.emacs.d/elpa/packages/org-10.0pre0.20260809.415/)
- Operating system: Windows 11
发送自 Outlook<http://aka.ms/weboutlook>
