From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Implement history facility for org-occur searches
Date: Mon, 10 Oct 2011 20:46:07 +0200 [thread overview]
Message-ID: <CAMXnza2x_t8tvDxkwT0_c_qHBr0Aags43wch98oaLdjyUVpNsA@mail.gmail.com> (raw)
In-Reply-To: <4D84CA41-ED23-4107-AD6D-7D1D1B1D0D6C@gmail.com>
On Mon, Oct 10, 2011 at 8:16 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On 10.10.2011, at 09:47, suvayu ali wrote:
>>
>> 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.
>
> We do have support for storing and setting outline visibility:
>
> Take a look at the functions
>
> org-outline-overlay-data
> org-set-outline-overlay-data
>
> and at the macro
>
> org-save-outline-visibility
>
> which uses the two functions described above.
>
Thanks a lot for these pointers Carsten!
>
> OK, I will mark it rejected, feel free to come back when you have
> something convincing (not only for us, but also convincing for you!) :)
>
Will do. :)
> - Carsten
Cheers,
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2011-10-10 18:46 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
2011-10-10 18:16 ` Carsten Dominik
2011-10-10 18:46 ` suvayu ali [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=CAMXnza2x_t8tvDxkwT0_c_qHBr0Aags43wch98oaLdjyUVpNsA@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=carsten.dominik@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).