[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Occur stack
From: |
Lars Ingebrigtsen |
Subject: |
Re: Occur stack |
Date: |
Sat, 18 Jan 2014 09:04:50 -0800 |
User-agent: |
Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) |
Tom <address@hidden> writes:
> Here's an other experimental code which does it the other way:
> it does not store buffer contents, it reruns the command
> instead.
Storing the command, too, is also nice, because then we can re-run the
command with the `g' command.
However, re-running an external command will not, in general, give us
the same buffer we had before. Things change, and re-running (say) grep
half an hour later might very well give us a different buffer than what
we expected (because files have changed, etc).
Having a history that presents us with ever-changing output doesn't seem
optimal.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
- Re: Occur stack, (continued)
- Re: Occur stack, Tom, 2014/01/17
- Re: Occur stack, Tom, 2014/01/18
- Re: Occur stack, Stefan Monnier, 2014/01/18
- Re: Occur stack, Tom, 2014/01/19
- Re: Occur stack, Daniel Colascione, 2014/01/19
- Re: Occur stack, Stefan Monnier, 2014/01/19
- Re: Occur stack, Tom, 2014/01/19
- Re: Occur stack,
Lars Ingebrigtsen <=
- Re: Occur stack, Stefan Monnier, 2014/01/18
- Re: Occur stack, Juri Linkov, 2014/01/21
- Re: Occur stack, joakim, 2014/01/21
- Re: Occur stack, Juri Linkov, 2014/01/22
- Re: Occur stack, Lars Ingebrigtsen, 2014/01/21
- Re: Occur stack, Stefan Monnier, 2014/01/21