From: "Mathias Dahl" <mathias.dahl@gmail.com>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: `*' interactive spec in some text-killing functions
Date: Fri, 29 Jun 2007 00:07:16 +0200 [thread overview]
Message-ID: <7dbe73ed0706281507sf061363h3095cbb3f97df610@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0706280838o7b2fb3d0r75d71e276e56f197@mail.gmail.com>
> This discussion ceased to be about technical matters very soon...
But it was amusing, a bit like a ping pong match... :)
FWIW, I think you are both right; toggling overwrite mode in an
read-only buffer is probably, in most cases, not something you meant
to do, so it might be useful to hint this to the user in an
educational sense. However, it makes no harm whatsoever, it is mostly
just meaningless operation, and you have to weigh the harm of this
meaninglessness against the possible inflation in echo area messages.
A defadvice, like you suggested yourself, seems to be the win-win
solution here. You are happy, David is happy and this means we all are
happy :)
Good night!
next prev parent reply other threads:[~2007-06-28 22:07 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
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 [this message]
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=7dbe73ed0706281507sf061363h3095cbb3f97df610@mail.gmail.com \
--to=mathias.dahl@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=teirllm@dms.auburn.edu \
/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).