From: David Kastrup <dak@gnu.org>
To: "Drew Adams" <drew.adams@ORACLE.COM>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; kbd returns wrong value
Date: Fri, 16 May 2008 11:32:17 +0200 [thread overview]
Message-ID: <86zlqqy4pq.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <004201c8b724$7c7cabb0$0200a8c0@us.oracle.com> (Drew Adams's message of "Fri, 16 May 2008 00:14:30 -0700")
"Drew Adams" <drew.adams@ORACLE.COM> writes:
> This problem is more widespread than I thought. Menu items can of course contain
> spaces: <My Foobar>, and when used in submenus the same problem arises as for
> <Brazilian Portuguese> in a <Describe> submenu.
>
> An there are other keys that have spaces and so could make `edmacro-parse-keys'
> choke in the same way (e.g. if in a submenu). In my `global-map', for instance,
> I see these keys that contain spaces:
>
> <RHP of Latin-1>
> <RHP of Latin-2>
> <RHP of Latin-3>
> <RHP of Latin-4>
> The bug is thus with `edmacro-parse-keys', not with the fact of having
> keys with spaces.
So how about using
>> After tracing edmacro-parse-keys, the problem seems to be here:
>>
>> (while (and (< pos (length string))
>> (string-match "[^ \t\n\f]+" string pos))
>> (let ((word (substring string (match-beginning 0)
>> (match-end 0)))
(string-match "[^ \t\n\f<]+\\|<[^>]+>" ...
instead?
--
David Kastrup
next prev parent reply other threads:[~2008-05-16 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87myj88yot.fsf@cyd.mit.edu>
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 [this message]
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 ` More key strangeness (was: 23.0.60; kbd returns wrong value) David Kastrup
2008-05-19 8:20 ` More key strangeness Stefan Monnier
2008-08-19 21:55 ` bug#237: marked as done (23.0.60; kbd returns wrong value) Emacs bug Tracking System
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=86zlqqy4pq.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=drew.adams@ORACLE.COM \
--cc=emacs-pretest-bug@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.