From: "Juanma Barranquero" <lekktu@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: `*' interactive spec in some text-killing functions
Date: Wed, 27 Jun 2007 23:30:39 +0200 [thread overview]
Message-ID: <f7ccd24b0706271430x74398de7g5aed0c7f42c3db2f@mail.gmail.com> (raw)
In-Reply-To: <858xa56rm5.fsf@lola.goethe.zz>
On 6/27/07, David Kastrup <dak@gnu.org> 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
action.
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.
> Would
> 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
IMHO).
Juanma
next prev parent reply other threads:[~2007-06-27 21:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 13:39 `*' interactive spec in some text-killing functions Juanma Barranquero
2007-06-27 14:08 ` David Kastrup
2007-06-27 14:25 ` Juanma Barranquero
2007-06-27 14:55 ` David Kastrup
2007-06-27 15:52 ` Juanma Barranquero
2007-06-27 16:22 ` Andreas Schwab
2007-06-27 18:43 ` Juanma Barranquero
2007-06-27 20:59 ` David Kastrup
2007-06-27 21:30 ` Juanma Barranquero [this message]
2007-06-27 22:04 ` David Kastrup
2007-06-27 22:11 ` Juanma Barranquero
2007-06-27 22:24 ` David Kastrup
2007-06-27 22:43 ` Juanma Barranquero
2007-06-27 23:13 ` David Kastrup
2007-06-27 23:22 ` Juanma Barranquero
2007-06-28 5:23 ` David Kastrup
2007-06-28 7:51 ` Juanma Barranquero
2007-06-28 8:07 ` David Kastrup
2007-06-28 8:15 ` Juanma Barranquero
2007-06-28 8:25 ` David Kastrup
2007-06-28 8:41 ` Juanma Barranquero
2007-06-28 9:04 ` David Kastrup
2007-06-28 9:09 ` Juanma Barranquero
2007-06-28 9:16 ` David Kastrup
2007-06-28 9:22 ` Juanma Barranquero
2007-06-28 9:48 ` Andreas Schwab
2007-06-28 10:21 ` Juanma Barranquero
2007-06-28 11:14 ` Andreas Schwab
2007-06-28 11:33 ` Juanma Barranquero
2007-06-28 10:55 ` David Kastrup
2007-06-28 14:03 ` Stefan Monnier
2007-06-28 14:12 ` David Kastrup
2007-06-28 14:16 ` Juanma Barranquero
2007-06-28 14:30 ` David Kastrup
2007-06-28 14:39 ` Vinicius Jose Latorre
2007-06-28 14:51 ` David Kastrup
2007-06-28 15:21 ` Luc Teirlinck
2007-06-28 15:38 ` Juanma Barranquero
2007-06-28 22:07 ` Mathias Dahl
2007-06-28 22:20 ` David Kastrup
2007-06-28 22:31 ` Juanma Barranquero
2007-06-28 16:25 ` Robert J. Chassell
2007-06-28 15:08 ` Davis Herring
2007-06-28 15:22 ` Juanma Barranquero
2007-06-28 8:47 ` Lennart Borgman (gmail)
2007-06-28 9:11 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0706271430x74398de7g5aed0c7f42c3db2f@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).