unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: SteveFKI <stephen.brown@eu.fkilogistex.com>
To: Help-gnu-emacs@gnu.org
Subject: Re: Key bindings
Date: Thu, 29 Mar 2007 13:49:34 -0700 (PDT)	[thread overview]
Message-ID: <9742406.post@talk.nabble.com> (raw)
In-Reply-To: <F6BE7BA7-AA58-4411-B136-111B01E844F7@Web.DE>


Peter,

Thanks for this. xmodmap gives me this

xmodmap:  up to 2 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock      
control     Control_L (0x25),  Control_R (0x6d)
mod1        Alt_L (0x40),  Alt_R (0x71)
mod2      
mod3      
mod4      
mod5      

Which does not look too bad to me 9with my limited knowledge. Were you
expecting to see the HOME key mapped elsewhere?

Steve

Peter Dyballa wrote:
> 
> 
> Am 29.03.2007 um 15:19 schrieb SteveFKI:
> 
>> I tried this, and I get the same problem. However, when I type C-h  
>> k <home>,
>> it emacs tells me that
>>
>> "<find> runs the command search-forward
>>  (search-forward STRING &optional BOUND NOERROR COUNT)
>>       which is an interactive built-in function.
> 
> Can you check what is bound to that "home" key in X11? (The utilities  
> xmodmap and xev can give information.)
> 
> --
> Greetings
> 
>    Pete
> 
>   "A designer knows he has arrived at perfection not when there is no  
> longer anything to add, but when there is no longer anything to take  
> away."
>                                   -- Antoine de Saint-Exupéry
> 
> 
> 
> 
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
> 
> 

-- 
View this message in context: http://www.nabble.com/Key-bindings-tf3485502.html#a9742406
Sent from the Emacs - Help mailing list archive at Nabble.com.

  reply	other threads:[~2007-03-29 20:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1572.1175163715.7795.help-gnu-emacs@gnu.org>
2007-03-29 10:49 ` Key bindings Tassilo Horn
2007-03-29 13:19   ` SteveFKI
2007-03-29 20:16     ` Peter Dyballa
2007-03-29 20:49       ` SteveFKI [this message]
2007-03-29 21:22         ` Peter Dyballa
     [not found]   ` <mailman.1576.1175174562.7795.help-gnu-emacs@gnu.org>
2007-03-29 20:16     ` Malte Spiess
2007-03-29 21:02       ` SteveFKI
2007-03-29 20:22     ` Tassilo Horn
2007-03-29 10:19 SteveFKI
     [not found] <mailman.1327.1122065988.20277.help-gnu-emacs@gnu.org>
2005-07-22 21:44 ` Charles philip Chan
  -- strict thread matches above, loose matches on Subject: below --
2005-07-22 19:32 Stefan Bienert
2005-07-22 22:56 ` Peter Dyballa
     [not found] <mailman.7825.1055479806.21513.help-gnu-emacs@gnu.org>
2003-06-13  7:03 ` key bindings Kai Großjohann
2003-06-13  8:57 ` Barman Brakjoller
2003-06-13  4:49 john doe
2002-12-13 21:20 Bingham, Jay
2002-12-13 18:01 sdieselil
2002-12-13 19:51 ` Kevin Rodgers
2002-12-16 11:53 ` Kester Clegg
2002-12-18 13:10   ` sdieselil
2002-12-18 23:32 ` Koyote
2002-11-01 16:20 Jeff Rancier
2002-11-01 16:56 ` Kevin Rodgers
2002-11-01 18:37   ` Jeff Rancier
2002-11-05 17:12     ` Michael Hudson
2002-11-02  0:23 ` Henrik Enberg

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=9742406.post@talk.nabble.com \
    --to=stephen.brown@eu.fkilogistex.com \
    --cc=Help-gnu-emacs@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.
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).