From: Rick Moynihan <rick@calicojack.co.uk>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Restricting the agenda to the current subtree
Date: Wed, 28 Nov 2007 10:52:27 +0000 [thread overview]
Message-ID: <474D486B.6070406@calicojack.co.uk> (raw)
In-Reply-To: <871wabahza.fsf@bzg.ath.cx>
Bastien wrote:
> Hi Rick,
>
> Rick Moynihan <rick@calicojack.co.uk> writes:
>
>> Firstly is it possible to bind this to a simple key-chord though as I'm
>> finding
>>
>> C-a < < a
>>
>> A little unwieldy.
>
> You can still press `C-c a 0' instead -- this keybinding is kept for
> backward compatibility.
>
>> Also, how about implementing another "follow" command, that does the
>> opposite of following movements in the agenda view and displaying them
>> in the file. i.e. When enabled it uses the org-goto interface to follow
>> movements within the file and display the restricted agenda view in
>> another window.
>
> I'm not sure to understand.
>
> Do you mean: while browsing an org file with org-goto, display the
> current entry in an agenda view when available?
Yes, but an appropriately filtered agenda view to the current subtree.
Maybe you could give a
> try to `org-toc.el': when the "info mode" is on and you are browsing the
> table of contents, it displays any timestamp the entry may have (which I
> find more "light" than building agenda views successively...)
Thanks for this, when I find the time I'll take a look at it.
R.
next prev parent reply other threads:[~2007-11-28 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 18:04 Restricting the agenda to the current subtree Rick Moynihan
2007-11-27 14:19 ` Bastien
2007-11-28 10:52 ` Rick Moynihan [this message]
[not found] ` <acf852aa0711271028m24c3d944wdde1481e4f7c9fa9@mail.gmail.com>
2007-11-28 17:41 ` Rick Moynihan
[not found] ` <474D4F98.1020505@calicojack.co.uk>
2007-11-30 14:32 ` Carsten Dominik
2007-11-30 16:33 ` Rick Moynihan
2007-11-30 18:38 ` Carsten Dominik
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=474D486B.6070406@calicojack.co.uk \
--to=rick@calicojack.co.uk \
--cc=bzg@altern.org \
--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).