Re: say when undo reaches last save

[Kevin Rodgers]

Dan Jacobson wrote:

> Idea: you know how we usually do edit, save, edit, save ...
> Well, when hitting the undo button, C-/, it would be nice to know when
> we have reached at least the most recent previous save depth!
>
> Sure, if we haven't saved recently, then we just hit undo until we see
> the ** change into a -- in the modeline.
>
> But, let's say we are lest happy with this compile of the file and
> want to backtrack to the previous version just a few steps ago, and no
> further.  Well, just hitting undo, there is just those "Undo!"
> messages in the mimbuffer, no hint of when we pass the undo that
> marked the last save.
>
> No voices from the peanut gallery saying "just save a .bak", please.

1. M-x revert-buffer RET (aka <menu-bar> <files> <revert-buffer>)

2. M-x find-alternate-file RET (aka C-x C-v)

3. Try this:

(defadvice undo (after buffer-modified-message activate)
  "If undoing the changes leaves the buffer unmodified (as it is is on disk),
display a message."
  (if (not (buffer-modified-p))
      (message "Buffer unmodified since its file was last read or saved")))

--
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;";>Kevin Rodgers</a>