RE: `save-excursion' defeated by `set-buffer'

[Drew Adams]

> > People will not naturally use `save-excursion' nowadays just to save
> > the current buffer.
> 
> Maybe not naturally, no.  But thanks to the pressure of years of old
> code flying around the web, they will do it nowadays on
> a regular basis.  But indeed, thanks to threads like this one 
> and to the warning I added, I hope I can reverse the trend.

The warning has already mistaught some (e.g. Uday) that `save-excursion' is just
downright evil.  The warning leaves users either unnecessarily frightened or
unnecessarily confused, or both.  That was not your intention, I'm sure, but it
is the effect.