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

[Andreas Schwab]

"Juanma Barranquero" <address@hidden> writes:

> On 6/27/07, David Kastrup <address@hidden> wrote:
>
>> The purpose of not having `*' presumably is to have them affect the
>> kill-ring.  In order to provide similar behavior upon multiple kills
>> as in a non-readonly-buffer, it appears reasonable to move across the
>> (non-happening) kill.
>
> I'm not sure I understand. Do you mean that people routinely does kill
> operations on a read-only buffer in order to copy text to the kill
> ring?

Please read the history.  This feature has been added 15 years ago.

>> Uh what?  Switching to overwrite-mode/binary-overwrite-mode does not
>> change the buffer, does it?
>
> No. But it seems like an error to *interactively* change to
> overwrite-mode in a read-only buffer, doesn't it?

Would you also forbid enabling auto-fill-mode or abbrev-mode in a
read-only buffer?

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."