unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tyler <tyler.smith@mail.mcgill.ca>
Subject: Re: key binding with windows and menu keys
Date: Mon, 15 Aug 2005 18:59:24 -0400	[thread overview]
Message-ID: <F69Me.8856$kz6.423195@news20.bellglobal.com> (raw)
In-Reply-To: <mailman.3819.1124119132.20277.help-gnu-emacs@gnu.org>

Thanks Pete, that's great. I've now got access to the windows keys, 
either by labelling them with xmodmap or using the quoted number. The 
only problem now is figuring out which keys to bind to which commands!

Tyler

Peter Dyballa wrote:
> 
> Am 15.08.2005 um 16:35 schrieb Angelina Carlton:
> 
>> There is one problem however, 2 of my computers do not run X and
>> consequently do not have the xmodmap command. So If I am working on them
>> in the console or via ssh I have to maintain my old key binding and try
>> to remember not to press the windows logo key instead.
>>
>> I will try to figure out how to enable these keys in non X environment an
>> let you know, perhaps someone already knows how to do this?
>>
> 
> Is C-h k <Windows key+another key> returns just <another key>?
> 
> If not, you could by hand 'M-x global-set-key <the combination> RET 
> scroll-other-window RET C-x ESC ESC C-a C-k C-g' -- bind the key and 
> start to repeat-previous-command. The cursor goes into the minibuffer, 
> where you put it at the beginning and then kill the whole line. Now an 
> interrupt, and you're ready to yank/paste the valid ELisp expression 
> into .emacs ... it wouldn't look pretty with a number instead of symbols 
> (that's what I am used from X11 or Apple's Aqua), but it would work.
> 
> -- 
> Greetings
> 
>   Pete
> 
> Without vi there is only GNU Emacs
> 
> 
> 

  parent reply	other threads:[~2005-08-15 22:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3675.1123988380.20277.help-gnu-emacs@gnu.org>
2005-08-14  4:44 ` key binding with windows and menu keys Tyler
2005-08-14  8:58   ` Friedrich Laher
2005-08-14 17:48   ` Peter Dyballa
     [not found]   ` <mailman.3737.1124042549.20277.help-gnu-emacs@gnu.org>
2005-08-15  1:45     ` Tyler
2005-08-15  5:41       ` Angelina Carlton
     [not found]       ` <mailman.3777.1124085510.20277.help-gnu-emacs@gnu.org>
2005-08-15 13:09         ` Tyler
2005-08-15 14:35           ` Angelina Carlton
2005-08-15 15:12             ` Peter Dyballa
2005-08-16 13:21               ` Angelina Carlton
2005-08-16 17:33                 ` Peter Dyballa
2005-08-16 18:41                   ` Angelina Carlton
2005-08-17 11:09                   ` Peter Dyballa
     [not found]                   ` <mailman.4032.1124278522.20277.help-gnu-emacs@gnu.org>
2005-08-17 13:13                     ` Tyler
     [not found]             ` <mailman.3819.1124119132.20277.help-gnu-emacs@gnu.org>
2005-08-15 22:59               ` Tyler [this message]
2005-08-16  8:49                 ` Peter Dyballa
2005-08-14  2:35 Sean Sieger
  -- strict thread matches above, loose matches on Subject: below --
2005-08-14  2:23 Sean Sieger
2005-08-14  1:18 Tyler

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='F69Me.8856$kz6.423195@news20.bellglobal.com' \
    --to=tyler.smith@mail.mcgill.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.
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).