Carsten Dominik, Carsten Dominik wrote: >> I don't understand the cause of this, moreover as I have the linked file >> open in my Emacs. >> >> Of course, since I've just reinstalled my Emacs, Org, and so on, on a new >> Windows setup, I have many small differences with before. >> >> Someone would have an idea for this? > > do you have agenda-follow-mode on?
Nope. I only use that once in a month, when checking clock times and description of tasks. Not enabled in yesterday's session. > Also, can you please hit the bug again in the debugger and then press > > e m RET > > and let me know what the debuffer reports? This should retrieve the value of > m. > > One possible reason to get this bug is to kill the buffer one of one of the > agenda files and then to revisit it. The marker will then not be nil, but it > will point nowhere.... I killed one of the org-agenda-files, and moved the cursor on it. I could reproduce the same problem as yesterday. Entering debugger... --8<---------------cut here---------------start------------->8--- Debugger entered--Lisp error: (wrong-type-argument stringp nil) set-buffer(nil) (if (markerp m) (set-buffer (marker-buffer m))) (save-excursion (if (markerp m) (set-buffer ...)) (save-excursion (goto-char ...) (org-display-outline-path t))) (org-with-point-at m (org-display-outline-path t)) (if (and m org-agenda-show-outline-path) (org-with-point-at m (org-display-outline-path t))) (let ((m ...)) (if (and org-agenda-follow-mode m) (org-agenda-show)) (if (and m org-agenda-show-outline-path) (org-with-point-at m ...))) org-agenda-do-context-action() org-agenda-next-line() call-interactively(org-agenda-next-line nil nil) --8<---------------cut here---------------end--------------->8--- =e m RET= displays: #<marker in no buffer> Though, here and now, pressing =g= resolves the problem. Agenda is refreshed, with the missing file being reloaded, and I can once again move and click on any line of the agenda. Yesterday, there were 2 differences: - =g= did not solve anything - all the agenda lines were bugging... Unluckily, I don't enough context now to be able to reproduce that exact same problem as of yesterday. I said it only occurred a couple of times, over a couple of days. Thanks! Best regards, Seb -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
