emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: sergio <mailbox@sergio.spb.ru>
To: emacs-orgmode@gnu.org
Subject: Re: update agenda on file modification
Date: Sat, 17 Dec 2011 04:10:43 +0400	[thread overview]
Message-ID: <4EEBDE03.6010204@sergio.spb.ru> (raw)
In-Reply-To: <loom.20111216T054850-960@post.gmane.org>

On 12/16/2011 08:53 AM, Herbert Sitz wrote:

> This has been discussed before and even if performance was not
> a problem there are reasons for not regenerating while you're in
> agenda.

OK. May be are right, and update agenda on buffer save or get used to
update it manually is better, but what are the main reasons not to
update agenda by buffer change (except performance)? Could you give me
a link to that discussion?

> There's a function that will regenerate the agenda after an idle time
> of x seconds: http://orgmode.org/worg/org-hacks.html#sec-1-8-11
I think http://orgmode.org/worg/org-hacks.html#sec-1-8-12 (refresh the
agenda view regularly) is more suitable. I see the only one reason for
regular agenda update --- keep "now" line up to date and run update
every minute. But how to synchronize this with minute start (zero second
of each minute)?

> I assume it could be modified to check for changed files on disk, if you 
> wanted to use that as trigger for regeneration.
Via after-save-hook?

-- 
sergio.

      reply	other threads:[~2011-12-17  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 12:38 update agenda on file modification sergio
2011-12-16  4:53 ` Herbert Sitz
2011-12-17  0:10   ` sergio [this message]

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=4EEBDE03.6010204@sergio.spb.ru \
    --to=mailbox@sergio.spb.ru \
    --cc=emacs-orgmode@gnu.org \
    /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).