From: Carsten Dominik <dominik@uva.nl>
To: Thomas Morgan <tlm@ziiuu.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Persistent filters in Org mode
Date: Thu, 20 May 2010 09:40:22 +0200 [thread overview]
Message-ID: <F6118958-4A77-453D-82F3-8CE6483BDD54@uva.nl> (raw)
In-Reply-To: <87iq6j79x5.fsf@ziiuu.com>
On May 20, 2010, at 1:23 AM, Thomas Morgan wrote:
> Hi, Carsten,
>
>> I think this is good - so if you agree, I will apply your patch
>> and rename the variable to ...persistent-filter
>
> That would be great, thanks.
>
>>> The main thing I am missing now is a command to edit the filter
>>> in the minibuffer. Or, if there's a separate persistent filter,
>>> perhaps the command could edit that if given an argument.
>>>
>>> It might also be useful to save filters to registers and restore
>>> them later.
>>
>> I guess a command to edit the filter, and a dedicated history
>> variable
>> for that command would be good enough? Would you like to make this
>> command and send me a combined patch with both changes?
>
> Alternatively, what do you think of the idea of saving
> a complete agenda view to a register (including the filter)?
> The register would contain all the information necessary to
> recreate the agenda view, and there would be a command to
> restore it.
That might be nice! Or a way to interactively create a view and then
turn it into a custom command with one key...
- Carsten
next prev parent reply other threads:[~2010-05-20 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 4:21 Persistent filters in Org mode Thomas Morgan
2010-05-07 7:26 ` Carsten Dominik
[not found] ` <CBB93A41-08A8-45A3-BC8D-DD2BCE3171BA@uva.nl>
2010-05-15 21:32 ` Thomas Morgan
2010-05-19 9:46 ` Carsten Dominik
2010-05-19 23:23 ` Thomas Morgan
2010-05-20 7:40 ` Carsten Dominik [this message]
2010-05-24 1:55 ` Samuel Wales
2010-05-20 7:40 ` 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=F6118958-4A77-453D-82F3-8CE6483BDD54@uva.nl \
--to=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=tlm@ziiuu.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).