emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bernt Hansen <bernt@norang.ca>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Killed Org files referred from the agenda?
Date: Thu, 12 Apr 2012 12:56:24 -0400	[thread overview]
Message-ID: <87ehrsq47b.fsf@norang.ca> (raw)
In-Reply-To: <86k41kq53b.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Thu, 12 Apr 2012 12:37:12 -0400")

pinard@iro.umontreal.ca (François Pinard) writes:

> 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.
>
> François

Rebuilding the agenda buffer (with 'g') is potentially expensive -- I
don't want a multi-second delay in my block view whenever Emacs thinks
that is appropriate.

I'd rather have full manual control over when things are rebuilt.  I
think your error is generated because your agenda is out of date so the
markers on the agenda view are old and possibly pointing at the wrong
stuff.  Keeping this up to date automagically will make org-mode much
slower and less usable (for me)

So here's one vote against.

Regards,
Bernt

next prev parent reply	other threads:[~2012-04-12 16:56 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 [this message]
2012-04-12 19:30     ` Nick Dokos
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=87ehrsq47b.fsf@norang.ca \
    --to=bernt@norang.ca \
    --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

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).