From: David Kastrup <dak@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org, 'Stefan Monnier' <monnier@iro.umontreal.ca>
Subject: More key strangeness (was: 23.0.60; kbd returns wrong value)
Date: Sun, 18 May 2008 11:26:20 +0200 [thread overview]
Message-ID: <85tzgwufnn.fsf_-_@lola.goethe.zz> (raw)
In-Reply-To: <004601c8b8a8$85c89230$0200a8c0@us.oracle.com> (Drew Adams's message of "Sat, 17 May 2008 22:32:11 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> > (string-match "[^ \t\n\f<]+\\|<[^>]+>" ...
>>
>> To avoid problems with C-x < and such, I'd recomment
>> (string-match "[^ \t\n\f<]+\\|<[^ \n>]\\(?:[^>]*[^ >\n]\\)?>" ...
>> So there can be spaces in symbols, but not as first or last char.
>
> See my previous message in reply to David, and my followup to that. Like David's
> suggestion for the regexp, yours fails for "C-x <":
>
> (edmacro-parse-keys "C-x <") gives "^X" (control-x character).
>
>> The handling of "C-x <<" and such shouldn't matter because
>> these aren't valid anyway.
>
> Then what is that part of the code for? Addin some comments to the code would
> help understanding.
Typing C-h k C-x <menu-bar> <options> <highlight-paren-mode>
gives the resulting error message
C-x <menu-bar> is undefined
in the *Messages* buffer, but
<highlight-paren-mode> is undefined
in the echo area.
Wow. Where does that discrepancy come from?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-05-18 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 20:01 23.0.60; kbd returns wrong value Drew Adams
2008-05-16 7:14 ` Drew Adams
2008-05-16 9:32 ` David Kastrup
2008-05-17 15:13 ` Drew Adams
2008-05-17 23:46 ` Drew Adams
2008-05-18 0:00 ` Drew Adams
2008-05-18 3:12 ` Stefan Monnier
2008-05-18 5:32 ` Drew Adams
2008-05-18 9:26 ` David Kastrup [this message]
2008-05-19 8:20 ` More key strangeness Stefan Monnier
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=85tzgwufnn.fsf_-_@lola.goethe.zz \
--to=dak@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).