François Pinard <pin...@iro.umontreal.ca> wrote: > Bastien <b...@gnu.org> writes: > > > "Sebastien Vauban" > > <wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org> writes: > > >> These last days, I've observed that, whenever creating a new Org file > >> (to be precise, when saving it), I'm asked: > >> > >> non-existent agenda file ~/file.txt. [R]emove from list or [A]bort? > >> > >> I'm then forced to answer `R' for the save to be done. Do you see > >> that behavior as well? > > > Nope. Any help on how to reproduce this? Since which commit do you > > see this? > > I'm not fully sure, but I think I saw this diagnostic already. It was > quite a while ago, and the problem disappeared by upgrading. Could it be > that, by some operational error, Sebastien is using some old Org code? >
The message is generated from org-check-agenda-file, so just edebug-defun this function (C-u M-C-x), try the operation and when (if) it stops, get a backtrace with ``d''. Nick PS. I don't see this bahavior at all.
