Re: `*' interactive spec in some text-killing functions

[David Kastrup]

Stefan Monnier <address@hidden> writes:

>> If I do a command, and the result of this command is irrelevant, I
>> consider it an error.
>
> The result is not irrelevant because you may do C-x C-q afterwards.
> But maybe a little warning reminding the user that the buffer is not yet
> writable could be added.  It doesn't seem tremendously useful, tho: she'll
> figure it out soon enough.

But the result will be the same whether or not overwrite-mode is
active.  So there is no sense in connecting the warning with
overwrite-mode.  And I don't see _any_ usefulness for this warning
since we'll get an error, anyway, once the readonly buffer is tried to
be written, without affecting the buffer.  Of course, if the user has
made a definition
(defadvice beep (after wwiii) (launch-missiles))
he will be happy about any such warning before actually committing an
error.  But other than that, Emacs' reaction to writing over readonly
text is perfectly harmless, and there is no reason to _warn_ people
that an error _might_ occur given certain behavior.

We also don't warn people one screen _before_ reaching the top of the
buffer "Further pressing of PgUp might lead to an error.  Be careful
now".

-- 
David Kastrup