From: Brad Miller <bmiller@cs.umn.edu>
Cc: steventamm@mac.com
Subject: Re: Problem with the RETURN key
Date: Tue, 17 Dec 2002 08:20:32 -0600 [thread overview]
Message-ID: <B3A77154-11CA-11D7-ABC1-0003938697CA@cs.umn.edu> (raw)
In-Reply-To: <E18OFC1-0005TJ-04@monty-python.gnu.org>
I've had this same problem with the return key ever since I first tried
to rebuild after going to 10.2.2
I think I mentioned it here at the time.
My setup is an 800MHz G4 tower. I have a non-apple natural keyboard,
so I thought maybe it had something to do with the driver for that.
I'm glad someone else has now found the same problem.
return is not defined in my function-key-map.
Adding the line:
> (define-key function-key-map [return] [13])
seems to work.
Brad
>
> ------------------------------
>
> Date: Tue, 17 Dec 2002 01:48:06 -0700
> From: Andrew Choi <akochoi@shaw.ca>
> To: Ovidiu Predescu <ovidiu@apache.org>
> Cc: emacs-devel@gnu.org
> Cc: Steven Tamm <steventamm@mac.com>
> Subject: Re: Problem with the RETURN key
> Message-ID: <m2n0n5c9q1.fsf@owlbear.local>
> In-Reply-To: <453EDB86-118F-11D7-B29E-00039398D61E@apache.org>
> References: <453EDB86-118F-11D7-B29E-00039398D61E@apache.org>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7BIT
> Precedence: list
> Message: 2
>
> Ovidiu Predescu <ovidiu@apache.org> writes:
>
>> The result is "<return> is undefined". This happens with no startup
>> file. [...]
>>
>> Any ideas on how to proceed further?
>
> Please read the node `Translating Input' in the Elisp manual.
>
> What is the value of `function-key-map'? Mine says:
>
> (keymap (M-return . [-134217715]) (return . [13]) (kp-equal . [61])
> (kp-divide . [47]) (kp-decimal . [46]) (kp-subtract . [45])
> (kp-separator . [44]) (kp-add . [43]) (kp-multiply . [42]) (kp-enter .
> [13]) (kp-tab . [9]) ...)
>
> Note the entry for `return'. If it is not there, you can say something
> like
>
> (define-key function-key-map [return] [13])
>
> but this really shouldn't be necessary. Are you sure you have a
> correct
> installation? Is the problem really specific to the Powerbook G4?
>
>
Brad Miller
PhD Candidate
University of Minnesota
(612) 384-8351
http://www-users.cs.umn.edu/~bmiller
next parent reply other threads:[~2002-12-17 14:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18OFC1-0005TJ-04@monty-python.gnu.org>
2002-12-17 14:20 ` Brad Miller [this message]
2002-12-17 14:42 ` Problem with the RETURN key Andreas Schwab
2002-12-17 14:46 ` Brad Miller
2002-12-17 14:55 ` Andreas Schwab
2002-12-17 15:19 ` Brad Miller
2002-12-17 15:33 ` Andreas Schwab
2002-12-17 17:42 ` Brad Miller
2002-12-18 12:25 ` Ovidiu Predescu
2002-12-18 12:26 ` Ovidiu Predescu
2002-12-18 12:27 ` Ovidiu Predescu
2002-12-16 19:51 Ovidiu Predescu
2002-12-16 20:17 ` Andrew Choi
2002-12-17 0:50 ` Ovidiu Predescu
2002-12-17 1:36 ` Ovidiu Predescu
2002-12-17 2:12 ` Andrew Choi
2002-12-17 7:15 ` Ovidiu Predescu
2002-12-17 8:48 ` Andrew Choi
2002-12-20 2:22 ` Ovidiu Predescu
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=B3A77154-11CA-11D7-ABC1-0003938697CA@cs.umn.edu \
--to=bmiller@cs.umn.edu \
--cc=steventamm@mac.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).