From: "Štěpán Němec" <stepnem@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6334@debbugs.gnu.org
Subject: bug#6334: 24.0.50; both examples in (elisp) Defining Minor Modes raise an error
Date: Tue, 27 Jul 2010 19:00:15 +0200 [thread overview]
Message-ID: <87iq40dfmo.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTikUkssfMKe4nk_a2-YLKzFh6cEYPRN7NDmLGWAD@mail.gmail.com> (Juanma Barranquero's message of "Tue, 27 Jul 2010 18:18:04 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Tue, Jul 27, 2010 at 13:26, Štěpán Němec <stepnem@gmail.com> wrote:
>
>> I'm not sure if you intended to preserve the key binding, let me just
>> point out that ^? (which was in the original example) is (ASCII) DEL,
>> i.e. usually [backspace], not [delete] on (modern?) text terminals.
>
> The docstring for the sample minor mode says "the control delete key",
> and my DEL key returns delete. If there's a more apropriate key
> binding that does not reproduce the bug, it's fine by me.
That'd be [C-backspace], if you're using the vector notation. Note we're
talking about the DEL _character_, not the key labeled Del(ete). It's
the Backspace key that usually sends DEL in the terminal (also note that
the example speaks about deleting all _preceding_ whitespace). I suspect
"the control delete key" wording comes from times when the keyboards
were somewhat different from those of today.
But it's only an example, so all this perhaps doesn't matter. I just
thought I'd mention the semantic shift introduced by the change, sorry.
Štěpán
next prev parent reply other threads:[~2010-07-27 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcsCnIknca5GRt4nT1+ZpSXlweHjjg==>
2010-06-02 21:42 ` bug#6334: 24.0.50; both examples in (elisp) Defining Minor Modes raise an error Drew Adams
2010-07-27 1:38 ` Juanma Barranquero
2010-07-27 4:44 ` Sven Joachim
2010-07-27 16:15 ` Juanma Barranquero
2010-07-27 11:26 ` Štěpán Němec
2010-07-27 16:18 ` Juanma Barranquero
2010-07-27 17:00 ` Štěpán Němec [this message]
2010-07-27 17:08 ` Juanma Barranquero
2010-07-27 20:22 ` David De La Harpe Golden
2010-07-27 22:41 ` Juanma Barranquero
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=87iq40dfmo.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=6334@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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).