From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Killed Org files referred from the agenda? Date: Thu, 12 Apr 2012 15:30:06 -0400 Message-ID: <4894.1334259006@alphaville> References: <861untq8mg.fsf@iro.umontreal.ca> <14311.1334246544@alphaville> <86k41kq53b.fsf@iro.umontreal.ca> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56908) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SIPie-0006L1-GY for emacs-orgmode@gnu.org; Thu, 12 Apr 2012 15:30:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SIPic-0005tH-NU for emacs-orgmode@gnu.org; Thu, 12 Apr 2012 15:30:12 -0400 Received: from g6t0186.atlanta.hp.com ([15.193.32.63]:9567) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SIPic-0005t1-IK for emacs-orgmode@gnu.org; Thu, 12 Apr 2012 15:30:10 -0400 In-Reply-To: Message from pinard@iro.umontreal.ca (=?us-ascii?Q?=3D=3Futf-?= =?us-ascii?Q?8=3FQ=3FFran=3DC3=3DA7ois=3F=3D?= Pinard) of "Thu\, 12 Apr 2012 12\:37\:12 EDT." <86k41kq53b.fsf@iro.umontreal.ca> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?us-ascii?Q?=3D=3Futf-8=3FQ=3FFran=3DC3=3DA7?= =?us-ascii?Q?ois=3F=3D?= Pinard Cc: emacs-orgmode@gnu.org Fran=C3=A7ois Pinard wrote: > Nick Dokos writes: >=20 > > Fran=C3=A7ois Pinard wrote: >=20 > >> Now that many Org files are part of my agenda list, it became more > >> likely that I inadvertently kill one of them. Then, commands like > >> "t" or "RET" in the agenda fail. I have to first revisit the Org > >> file by some other mean first, for such commands to succeed. Could > >> Org do the revisiting as needed, instead of raising an error? > >>=20 >=20 > > Just do "g" in the agenda and retry the "t". >=20 > Thanks for hint, Nick, I'll surely use it. >=20 > Yet, I do not think it is appropriate for Org to raise an Emacs Lisp > error. It really looks like a bug. >=20 But it is an error: you've gotten rid of a buffer that it expected to find. Admittedly however, the error should be caught and a reasonable error message printed out (something like ``Try pressing "g" in the agenda and then retry the command '' :-) ) This would alleviate Bernt's performance concerns as well: if you make the mistake (kill a buffer that's needed), you suffer the consequences (slow rebuilding of the agenda) - it does not affect anybody else. Maybe org-with-remote-undo can check if the buffer argument is nil and complain if it is. Nick