Re: user has no business toggling overwrite-mode in read-only buffers

[Dan Jacobson <jidanni@dman.ddts.net>]

A> 1. You have a source-file which is RO due to some version control system,
A> but you want to make a private (changed) copy on your own hard disk.  You
A> C-x C-q it, make the changes, then store it where you want with C-x C-w.

You do C-x C-q first.  So it isn't a read-only buffer anymore. I.e.,
um, "like, read the Subject line, Holmes."  Sorry about that.

A> 2. Something (something like dired, perhaps?), makes a listing of files
A> in a buffer, but leaves the buffer RO because "the user has no reason to
A> edit it".

You got me all wrong.  overwrite-mode is that little thing activated
by your pinky when it misses the DEL key and hits the INS key.  It is
good for changing xxxxxxxxxxxx to xxxxxyyyxxxx without hitting
DEL... maybe it should have been called overprint or overstrike mode.

I was just saying the user should have to do vc-toggle-read-only
(^X^Q) before doing (<insert>) overwrite-mode.
-- 
http://jidanni.org/ Taiwan(04)25854780