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: Thu, 28 Jun 2007 10:15:22 +0200 [thread overview]
Message-ID: <f7ccd24b0706280115o19a8e42md6f8d520b6485117@mail.gmail.com> (raw)
In-Reply-To: <86ps3gy02e.fsf@lola.quinscape.zz>
On 6/28/07, David Kastrup <dak@gnu.org> wrote:
> But _why_ wouldn't it be "smart"? The command _is_ executed, it has
> the normal effect (which may become relevant if the buffer-read-only
> state changes), and it does _absolutely_ no harm to the buffer
> contents or anything else.
Neither does any harm to PgUp at the beginning of a buffer. What is
the message for? To alert me that I cannot go up? Well, my overwrite
message is to alert me that I cannot overwrite even if I just changed
to overwrite, and that I shouldn't expect most normal keys to act
differently just because I changed to overwrite.
> You still have not presented a single case where a notice would be of
> any use at all, even if just to prevent the user from wasting time or
> energy.
Do you mean that the PgUp case is better because it prevents the user
from endlessly looping doing PgUp without noticing that he's at the
beginning of the buffer (which is also displayed in the mode line, at
least on the default line-number-mode configuration) and that nothing
is moving?
> I don't get it, and you are not exactly making a convincing, or even
> any case for it.
I stopped trying to convince you around the "angels on a pin's head"
message, if not earlier. But you are unable to accept that I'm saying
that I would find it convenient: you try to convince me that I
wouldn't. That's ridiculous.
Juanma
next prev parent reply other threads:[~2007-06-28 8:15 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0706280115o19a8e42md6f8d520b6485117@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.