[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Juanma Barranquero
Subject: Re: `*' interactive spec in some text-killing functions
Date: Wed, 27 Jun 2007 23:30:39 +0200

On 6/27/07, David Kastrup <address@hidden> wrote:

I don't see what confusion is caused by being able to switch from
insert-mode to overwrite-mode and back in a readonly buffer.

This is about angels on a pin's head, isn't it? Because I already said
that the issue was not really important...

But anyway, it is a cognitive dissonance. Nothing more, nothing less.
If I switch to overwrite mode in a read-only buffer, the problem is
not that it is *going to* cause me confusion, the problem is that I
*am* already confused; because, in most cases, it is a meaningless

When I'm at the beginning of a buffer and I do PgUP, which runs
scroll-down, I get a "Beginning of buffer" message. It's not really
necessary. But it is helpful.

you also prohibit switching _off_ overwrite-mode?  If yes, why?  If
no, why?

Prohibit? (overwrite-mode 1) works regardless of `*', so certainly
code would be able to switch it, if really needed. I wasn't talking
about "prohibiting", but about "warning" (that's what the `*' does


reply via email to

[Prev in Thread] Current Thread [Next in Thread]