On 2025-11-07 at 12:08, D. R. Evans wrote: > Markus Schönhaber wrote on 11/7/25 9:41 AM: > >> So, from crontab's point of view the process it started (/usr/bin/kate) >> has terminated and, since the user hasn't had the chance to do some >> actual editing, the file-to-be-edited is unchanged. And that's what >> crontab tells you. >> > > Man, talk about making things over-complicated (and, hence, fragile). Thank > you so much for your (and other people's) explanation of what is going on. > > OK, so I have ditched kate completely for this purpose and switched to joe, at > least for now. FWIW, https://unix.stackexchange.com/questions/798563/how-to-stop-kate-forking-itself suggests that 'kate -b' (if specified in the VISUAL variable, and possibly other places depending on exactly where you need kate to be invoked from) should produce the behavior you were apparently wanting. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature