From: suvayu ali <email@example.com>
To: Carsten Dominik <firstname.lastname@example.org>
Cc: Org mode mailing list <email@example.com>
Subject: Re: [PATCH] Implement history facility for org-occur searches
Date: Mon, 10 Oct 2011 09:47:26 +0200 [thread overview]
Message-ID: <CAMXnza0-xJVRrE35_yfEuOdLWekmqPQ+Z7omX6z24fEKo9EuMg@mail.gmail.com> (raw)
Sorry, I somehow missed this email.
On Thu, Oct 6, 2011 at 9:54 AM, Carsten Dominik
> Hi Suvayu,
> 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?
My use case was to easily traverse through a sequence of sparse-tree
searches. Something that I thought might be useful when searching in a
large file. My implementation is probably very suboptimal. I was
hoping to find a way to take a "snapshot" of a sparse tree view, and
then "undo" or "redo" a sparse tree view. By undo/redo I mean
restoring the visibility states of the trees and the highlighted
search text. However I couldn't find a way to get the "snapshot", so I
tried repeating the searches to achieve a similar result.
I have had time to think since I submitted the patch, maybe its
something very specific to how I use org and is probably more
appropriate as a local modification and not for inclusion in org (at
least not in its current form).
> - Carsten
Thanks a lot.
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-10 7:47 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
2011-10-10 7:47 ` suvayu ali [this message]
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).