From: Carsten Dominik <email@example.com>
To: Suvayu Ali <firstname.lastname@example.org>
Cc: Org mode mailing list <email@example.com>
Subject: Re: [PATCH] Implement history facility for org-occur searches
Date: Thu, 6 Oct 2011 09:54:30 +0200 [thread overview]
Message-ID: <8BC585D4-66F5-4FB3-9D85-5B23C6E44C0C@gmail.com> (raw)
could you describe your use case for this addition? When would you need
this above calling org-occur again and using the minibuffer
history to repeat your search?
On Aug 24, 2011, at 1:47 AM, Suvayu Ali wrote:
> Hi Bastien and everyone,
> I wanted to implement a history facility for sparse trees. Since sparse
> trees use org-occur and org-scan-tags any such facility would need to
> be aware of both functions. My lisp foo proved to be too weak to
> understand org-scan-tags, so I implemented this only for org-occur
> With this patch one can traverse the sparse tree history for date,
> regular expression and TODO keyword searches with the
> org-occur-history-forward and org-occur-history-backward functions. One
> can also call the org-occur-history-next function interactively to jump
> to the nth history entry. This should also work for any other searches
> that uses org-occur as the backend.
> Please feel free to modify the patch if there are better ways to
> implement this facility. Thank you.
> Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-06 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 23:47 [PATCH] Implement history facility for org-occur searches Suvayu Ali
2011-10-06 7:54 ` Carsten Dominik [this message]
2011-10-10 7:47 ` suvayu ali
2011-10-10 18:16 ` Carsten Dominik
2011-10-10 18:46 ` suvayu ali
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).