From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Killed Org files referred from the agenda?
Date: Thu, 12 Apr 2012 15:30:06 -0400 [thread overview]
Message-ID: <4894.1334259006@alphaville> (raw)
In-Reply-To: Message from pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) of "Thu\, 12 Apr 2012 12\:37\:12 EDT." <86k41kq53b.fsf@iro.umontreal.ca>
François Pinard <pinard@iro.umontreal.ca> wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
>
> > François Pinard <pinard@iro.umontreal.ca> wrote:
>
> >> 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?
> >>
>
> > Just do "g" in the agenda and retry the "t".
>
> Thanks for hint, Nick, I'll surely use it.
>
> Yet, I do not think it is appropriate for Org to raise an Emacs Lisp
> error. It really looks like a bug.
>
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
next prev parent reply other threads:[~2012-04-12 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 15:20 Killed Org files referred from the agenda? François Pinard
2012-04-12 16:02 ` Nick Dokos
2012-04-12 16:37 ` François Pinard
2012-04-12 16:56 ` Bernt Hansen
2012-04-12 19:30 ` Nick Dokos [this message]
2012-04-13 5:07 ` Bastien
2012-04-13 10:21 ` Jambunathan K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4894.1334259006@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).