From: Carsten Dominik <carsten.dominik@gmail.com>
To: Denis Bueno <dbueno@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: C-n and saving in agenda buffers
Date: Thu, 27 Sep 2007 20:19:38 +0200 [thread overview]
Message-ID: <909b09c80a364e7f2ba014753a81607f@science.uva.nl> (raw)
In-Reply-To: <6dbd4d000709271028o26a11e7dvcefeced720d0700b@mail.gmail.com>
On Sep 27, 2007, at 19:28, Denis Bueno wrote:
> Hi all,
>
> First of all, although I kind of lurk on this list, I absolutely adore
> org-mode. Carsten's attention to everyone's complaints is amazingly
> consistent. Thank you.
You are welcome.
> Second, in the buffer that shows the agenda for the current week or
> day, why is C-n bound to an action that moves you forward a day at a
> time? Since the current day shows all my deadlines and TODOs for the
> future, it's not likely that one will need to look at days ahead, and
> if I do, it's probably not common enough to be bound to something as
> fundamental as C-n. I most frequently want to move in agenda buffers
> in order to mark TODOs done. Since I always use C-n/C-p instead of
> the arrow keys, using the arrow keys in this one particular situation
> requires a significant mental step that always causes me to mutter
> under my breath.
Point taken, and I actually agree and will change this.
Note that "n" and "p" also move you around.
> Also, I suggest that if I go through an Agenda buffer and mark some
> todos done, if I hit C-x C-s it should save the files whose todo items
> have changed. This would reinforce the abstraction that I'm really
> just looking at my org files through different lenses, and actions in
> that abstraction affect the underlying locations.
OK, also this is a useful addition. Again, "s" does this already, but
I agree C-x C-s is logical.
- Carsten
prev parent reply other threads:[~2007-09-27 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 17:28 C-n and saving in agenda buffers Denis Bueno
2007-09-27 18:19 ` Carsten Dominik [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=909b09c80a364e7f2ba014753a81607f@science.uva.nl \
--to=carsten.dominik@gmail.com \
--cc=dbueno@gmail.com \
--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).