From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: Occur stack
Date: Fri, 17 Jan 2014 09:24:43 +0100 [thread overview]
Message-ID: <52D8E8CB.5080600@online.de> (raw)
In-Reply-To: <loom.20140116T180512-732@post.gmane.org>
Am 16.01.2014 18:19, schrieb Tom:
> Tom <adatgyujto <at> gmail.com> writes:
>>
>> The code is generic, so in theory it can work for other
>> commands too, but I only tested it with occur.
>>
>
> I tried it with grep too, specifically grep-find. You need to
> add the saving function to compilation-finish-functions:
>
>
> (defun buffer-history-grep-save (buf result)
> (if (and (eq major-mode 'grep-mode)
> (equal result "finished\n"))
> (buffer-history-save)))
>
> (add-hook 'compilation-finish-functions 'buffer-history-grep-save)
>
>
> If you do some grepping and then run M-x buffer-history-list
> in the *grep* buffer then you can see your previous greps
> and you can restore them.
>
> The listing is not as useful as with occur, because this
> simple implementation only takes the first line of the
> output, assuming it describes the contents which is true
> for occur, but not really true for grep-find. It only gives
> you the directory, so a proper implementation should be more
> clever about that, it should have a way to retrieve the relevant
> inputs from the target command.
>
> Another thing is that unlike occur it does not work seamlessly
> if you do grep-find in different directories, because the
> results are displayed as relative file names, so default-directory
> should be restored too.
>
> A proper implementation should restore the buffer local variables too
> in addition to the buffer contents.
>
>
>
Hi Tom,
works for me, great, thanks!
BTW needed a (require 'cl) still.
In cases where a plenty of occur-calls is done, maybe the discussion WRT to memory pertains?
Andreas
next prev parent reply other threads:[~2014-01-17 8:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 16:24 Occur stack Tom
2014-01-14 16:35 ` Nicolas Richard
2014-01-14 16:57 ` Tom
2014-01-14 17:00 ` Tom
2014-01-14 17:07 ` Juanma Barranquero
2014-01-14 17:12 ` Tom
2014-01-14 17:21 ` Lars Magne Ingebrigtsen
2014-01-14 20:30 ` Tom
2014-01-14 20:40 ` Tom
2014-01-14 21:08 ` Daniel Colascione
2014-01-14 21:24 ` John Yates
2014-01-14 21:32 ` Drew Adams
2014-01-14 21:26 ` Stefan Monnier
2014-01-14 17:41 ` Allen S. Rout
2014-01-15 8:27 ` Juri Linkov
2014-01-15 9:06 ` David Kastrup
2014-01-16 7:57 ` Juri Linkov
2014-01-16 8:53 ` David Kastrup
2014-01-16 9:46 ` Lars Ingebrigtsen
2014-01-16 10:36 ` David Kastrup
2014-01-16 13:47 ` Stefan Monnier
2014-01-16 13:54 ` David Kastrup
2014-01-17 15:52 ` Lars Ingebrigtsen
2014-01-15 18:52 ` Andreas Röhler
2014-01-15 20:16 ` Tom
2014-01-16 17:19 ` Tom
2014-01-17 8:24 ` Andreas Röhler [this message]
2014-01-17 13:24 ` Tom
2014-01-19 14:50 ` Andreas Röhler
2014-01-19 16:03 ` Tom
2014-01-17 17:19 ` Tom
2014-01-18 17:01 ` Tom
2014-01-19 2:39 ` Stefan Monnier
2014-01-19 6:40 ` Tom
2014-01-19 7:12 ` Daniel Colascione
2014-01-19 14:38 ` Stefan Monnier
2014-01-19 15:56 ` Tom
2014-01-18 17:04 ` Lars Ingebrigtsen
2014-01-19 2:45 ` Stefan Monnier
2014-01-21 7:51 ` Juri Linkov
2014-01-21 9:05 ` joakim
2014-01-22 8:03 ` Juri Linkov
2014-01-21 19:42 ` Lars Ingebrigtsen
2014-01-22 1:27 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D8E8CB.5080600@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@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.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).