emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Detlef Steuer <detlef.steuer@gmx.de>,
	Tommy Stanton <tommystanton@gmail.com>,
	Kiwon Um <um.kiwon@gmail.com>, Nick Dokos <nicholas.dokos@hp.com>
Subject: Re: org-agenda-show-current-time-in-grid and automatic refresh
Date: Thu, 13 Jan 2011 07:36:09 +0100	[thread overview]
Message-ID: <AANLkTinePR_+GvqTbt0iVoQyxAHvzw0WNQS89Czu+fmx@mail.gmail.com> (raw)
In-Reply-To: <87mxn54d0q.fsf@gmail.com>

On Thu, Jan 13, 2011 at 05:56, Kiwon Um <um.kiwon@gmail.com> wrote:
> ;; refresh agenda view regurally
> (defun kiwon/org-agenda-redo-in-other-window ()
>  "Call org-agenda-redo function even in the non-agenda buffer."
>  (interactive)
>  (let ((agenda-window (get-buffer-window org-agenda-buffer-name t)))
>    (when agenda-window
>      (with-selected-window agenda-window (org-agenda-redo)))))
> (run-at-time nil 300 'kiwon/org-agenda-redo-in-other-window)

I must admit that I would like and use a less simple solution where
only the line with the current time would be updated and if necessary
also moved within the time grid once every minute. I would like it
even additionally to the clock on the OS desktop because the agenda
view current time does not only show the current time itself but also
the current time position within the time grid.

For me it would not be desirable to update also all other agenda view
contents like above without request from the user with `g'. On one
side because it can collide badly with the user while manipulating (e.
g. shift-right several times on an entry) or only moving in the agenda
view and on one side because an overall update can take an
unpredictably large amount of CPU time for a larger set of larger
agenda files.

Michael

  reply	other threads:[~2011-01-13  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12  3:23 org-agenda-show-current-time-in-grid and automatic refresh Kiwon Um
2011-01-12  7:19 ` Suvayu Ali
2011-01-12  8:23   ` Nick Dokos
2011-01-12 21:33     ` Suvayu Ali
2011-01-13  4:56       ` Kiwon Um
2011-01-13  6:36         ` Michael Brand [this message]
2011-01-15 11:35         ` Bastien
2011-01-18  9:58   ` Carsten Dominik
2011-01-12  7:58 ` Detlef Steuer
  -- strict thread matches above, loose matches on Subject: below --
2011-01-13  1:43 Tommy Stanton
2011-01-13  8:41 ` Sébastien Vauban

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=AANLkTinePR_+GvqTbt0iVoQyxAHvzw0WNQS89Czu+fmx@mail.gmail.com \
    --to=michael.ch.brand@gmail.com \
    --cc=detlef.steuer@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=tommystanton@gmail.com \
    --cc=um.kiwon@gmail.com \
    /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).