6:54 p.m.
Hello:
how do I bind commands to the "G" keys of my G11 keyboard
(http://www.logitech.com/en-gb/434/285?section=downloads&bit=&osid=13). I've
already used-up all of my "F" keys (see below):
unfortunately, replacing the "f" with "g" does not work.
Sirano
<http://www.sgc.utoronto.ca/pmwiki/pmwiki.php?n=ubiquitinbiology.HomePage>
(define-key global-map '(f1)
'set-mark-command)
(define-key global-map '(f2)
'string-rectangle)
(define-key global-map '(f3) 'q125)
(define-key global-map '(f4)
'delete-all)
(define-key global-map '(f5)
'hyphenall)
(define-key global-map '(f6)
'fastall)
(define-key global-map '(f7)
'sequence-one-line3)
(define-key global-map '(f8)
'hyphenall_with_vecseq)
(define-key global-map '(f9)
'set-mark-command)
(define-key global-map '(f10)
'kill-rectangle)
(define-key global-map '(f11)
'count-lines-region)
(define-key global-map '(f12)
'yank-rectangle)
(define-key global-map '(control f1) 'fasta2sirana)
(define-key global-map '(control f2) 'lig-pY)
(define-key global-map '(control f3) 'q127)
(define-key global-map '(control f4) 'lig-unmodified)
(define-key global-map '(control f5) 'translation_all)
(define-key global-map '(control f6) 'query-replace)
(define-key global-map '(control f7) 'load-file)
(define-key global-map '(control f8) 'set-regexp-face-interactively)
(define-key global-map '(control f9) 'set-mark-command)
(define-key global-map '(control f10)
'2glycerolfamilies)
(define-key global-map '(control f11)
'consensus_alignment)
(define-key global-map '(control f12)
'consensus_2dpred)
(define-key global-map '(shift f1) 'rev_trans_ascii_all)
(define-key global-map '(shift f2) 'hyphenallminus)
(define-key global-map '(shift f3) 'pymol2sdp)
(define-key global-map '(shift f4) 'custom-set-faces2)
(define-key global-map '(shift f5) 'misc_sites)
(define-key global-map '(shift f6) 'protein-weight-region)
(define-key global-map '(shift f7) '2expressions)
(define-key global-map '(shift f8) 'sortfasta)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
1:11 a.m.
From: "Sirano Dhe-Paganon" <sirano.dhepaganon(a)utoronto.ca>
Date: Mon, 15 Nov 2010 13:54:00 -0500
how do I bind commands to the "G" keys of my G11 keyboard
(http://www.logitech.com/en-gb/434/285?section=downloads&bit=&osid=13).
I've
already used-up all of my "F" keys (see below):
unfortunately, replacing the "f" with "g" does not work.
If the keysym is getting to XEmacs it is easy. If the keysym gets to
XEmacs you'll probably get <keysym> is undefined. I'm going to guess
that you aren't seeing that.
You'll probably have to do .xmodmap to map a keycode to a keysym and
do setkeycodes, depending. For example for ubuntu
https://help.ubuntu.com/community/MultimediaKeys
-jeff
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
12:31 p.m.
Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on Windows-7.
I was hoping something like this in my custom.el file might do the trick
"(define-key global-map '(E0_17) 'kill-primary-selection)", but ... it
doesn't.
Sirano
-----Original Message-----
From: Jeff Mincy [mailto:jeff＠delphioutpost.com]
Sent: Monday, November 15, 2010 8:12 PM
To: Sirano Dhe-Paganon
Cc: xemacs-beta(a)xemacs.org
Subject: Re: binding to G keys
From: "Sirano Dhe-Paganon" <sirano.dhepaganon(a)utoronto.ca>
Date: Mon, 15 Nov 2010 13:54:00 -0500
how do I bind commands to the "G" keys of my G11 keyboard
(http://www.logitech.com/en-gb/434/285?section=downloads&bit=&osid=13).
I've
already used-up all of my "F" keys (see below):
unfortunately, replacing the "f" with "g" does not work.
If the keysym is getting to XEmacs it is easy. If the keysym gets to
XEmacs you'll probably get <keysym> is undefined. I'm going to guess
that you aren't seeing that.
You'll probably have to do .xmodmap to map a keycode to a keysym and
do setkeycodes, depending. For example for ubuntu
https://help.ubuntu.com/community/MultimediaKeys
-jeff
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:55 p.m.
On Tue, 16 Nov 2010 07:31:08 -0500
"Sirano Dhe-Paganon" <sirano.dhepaganon(a)utoronto.ca> wrote:
Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on
Windows-7.
I was hoping something like this in my custom.el file might do the
trick "(define-key global-map '(E0_17) 'kill-primary-selection)",
but ... it doesn't.
If E0_17 is recognized as a keysym, try this:
(global-set-key [E0_17] 'kill-primary-selection)
Cheers,
Sean
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:29 a.m.
Sean MacLennan writes:
On Tue, 16 Nov 2010 07:31:08 -0500
"Sirano Dhe-Paganon" <sirano.dhepaganon(a)utoronto.ca> wrote:
> Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on
> Windows-7.
If you press a key that XEmacs doesn't understand, it should report
"<keysym> not defined" in the echo area. The keysym that is reported
there can then be bound using define-key (which you are using
correctly, although Sean's version is the more common idiom).
You can see old messages by looking at the buffer named
" *Message-Log*" (the quotation marks are not part of the name, but
the leading space is significant).
> I was hoping something like this in my custom.el file might do
the
> trick "(define-key global-map '(E0_17) 'kill-primary-selection)",
> but ... it doesn't.
If E0_17 is recognized as a keysym, try this:
(global-set-key [E0_17] 'kill-primary-selection)
And if it works, report it as a bug :-). Those two forms should be
equivalent.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:10 p.m.
Stephen; regarding binding to G keys, unfortunately, nothing is reported in
the echo area by xemacs if I press any of the G keys. As a test, I pressed
other non-G keys, and found that if I press the top-right-most key on my
keyboard, labeled "Pause/Break", xemacs notes in the echo area: "Pause not
defined.". I then mapped the "Pause" <keysym> as follows:
"(global-set-key
[pause] 'translation_all)" and it works! Great. Now I need to know the
<keysym> of the G keys.
Thanks again for the init.el detail; my scripts are much more organized now.
-----Original Message-----
From: xemacs-beta-bounces(a)xemacs.org [mailto:xemacs-beta-bounces＠xemacs.org]
On Behalf Of Stephen J. Turnbull
Sent: Wednesday, November 17, 2010 12:29 AM
To: Sean MacLennan
Cc: xemacs-beta(a)xemacs.org
Subject: Re: binding to G keys
Sean MacLennan writes:
On Tue, 16 Nov 2010 07:31:08 -0500
"Sirano Dhe-Paganon" <sirano.dhepaganon(a)utoronto.ca> wrote:
> Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on
> Windows-7.
If you press a key that XEmacs doesn't understand, it should report
"<keysym> not defined" in the echo area. The keysym that is reported
there can then be bound using define-key (which you are using
correctly, although Sean's version is the more common idiom).
You can see old messages by looking at the buffer named
" *Message-Log*" (the quotation marks are not part of the name, but
the leading space is significant).
> I was hoping something like this in my custom.el file might do
the
> trick "(define-key global-map '(E0_17) 'kill-primary-selection)",
> but ... it doesn't.
If E0_17 is recognized as a keysym, try this:
(global-set-key [E0_17] 'kill-primary-selection)
And if it works, report it as a bug :-). Those two forms should be
equivalent.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:42 p.m.
Sirano Dhe-Paganon writes:
Stephen; regarding binding to G keys, unfortunately, nothing is
reported in
the echo area by xemacs if I press any of the G keys.
Unfortunately, I know nothing about the Windows keyboard driver, but
that sounds to me like no keysyms are reaching XEmacs when you press
those keys. It looks like the keysyms we know about are hard-coded in
mswindows_key_to_emacs_keysym() in src/event-msw.c, and there's no
default to do something useful if we get an unknown keysym -- it's
just dropped on the floor.
BTW, for anybody who might have a clue about how Windows does these
things and would be willing to hack on it, GNU uses GetKeyNameText()
which I assume is a Windows API.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:55 p.m.
On Wed, Nov 17, 2010 at 12:29 AM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
You can see old messages by looking at the buffer named
" *Message-Log*" (the quotation marks are not part of the name, but
the leading space is significant).
I seem to recall having XEmacs grind to a halt in connection with
having that open in the past. I think I've been assuming that that was
why there was a leading space in the buffer name -- to keep people
from opening it and getting into a state where they might have to exit
XEmacs non-gracefully.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6 p.m.
I was unable to bind to G keys because cannot find the <keysym> of the G
keys on G11 keyboard. Next, I will try to contact Logitech directly.
-----Original Message-----
From: xemacs-beta-bounces(a)xemacs.org [mailto:xemacs-beta-bounces＠xemacs.org]
On Behalf Of Samuel Bronson
Sent: Friday, December 03, 2010 11:56 AM
To: Stephen J. Turnbull
Cc: Sean MacLennan; xemacs-beta(a)xemacs.org
Subject: Re: binding to G keys
On Wed, Nov 17, 2010 at 12:29 AM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
You can see old messages by looking at the buffer named
" *Message-Log*" (the quotation marks are not part of the name, but
the leading space is significant).
I seem to recall having XEmacs grind to a halt in connection with
having that open in the past. I think I've been assuming that that was
why there was a leading space in the buffer name -- to keep people
from opening it and getting into a state where they might have to exit
XEmacs non-gracefully.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:25 p.m.
Sirano Dhe-Paganon writes:
I was unable to bind to G keys because cannot find the <keysym>
of the G
keys on G11 keyboard. Next, I will try to contact Logitech
directly.
I don't think that will be helpful without changes to XEmacs. Based
on your report (that you don't see a keysym in the echo area when you
press that key) and a look at the implementation, I believe that
XEmacs simply doesn't see those keysyms at all, so binding it won't
help even if you know what it is. However, I don't know how to fix
it, since I don't know MS Windows, the code is pretty confusing, and
this happens at a very low level.
We need somebody who knows something about Windows programming and has
access to MSDN (experience in programming keyboard drivers would be
too much to ask for, I suppose!) to take a look at it.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:16 p.m.
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Stephen> ... Based on your report (that you don't see a keysym in the echo
Stephen> area when you press that key) and a look at the
Stephen> implementation, I believe that XEmacs simply doesn't see
Stephen> those keysyms at all, so binding it won't help even if you
Stephen> know what it is. ...
Could it be that the keyboard driver maps those keys some esoteric
feature and don't let it through to XEmacs? From the very little I
have just learned about the keyboard by surfing the net it seems like
the G-keys can be used in gaming to define different kinds of
macros. So the driver is likely to catch the keys!?
I have had similar experience with mouse drivers. Mouses with many
buttons etc comes with a driver that allows you to map the buttons to
different features. With XEmacs I often have to disable the default
behavior, as defined by the driver, tide to the middle button. As an
old X-windows user I like the middle press just to be sent to
XEmacs. Nothing else.
Maybe you are experiencing something similar with the G-keys? Either
you can bind them to some keys that XEmacs do recognise or just
disable any special treatment on them? But I'm just a standard
keyboard user ...
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
6:30 p.m.
Interesting. Let me clarify though. Indeed, I am using the G-keys in xemacs,
but I am using them thru the Logitech macro mapper. For example, my G1 key
is mapped to Control-F1. No problem there. But, the point of the G keys, I
thought, is so that we don't have to tie-up by F-keys or any other keys for
that matter. I've already mapped to my commands all of the standard keys
(including the use of control , shift, and alt); now I would like to use the
G keys. So far, I cannot map the G-keys directly to an xemacs command.
Cheers, S.
-----Original Message-----
From: Mats Lidell [mailto:matsl＠xemacs.org]
Sent: Saturday, December 04, 2010 1:17 PM
To: Sirano Dhe-Paganon
Cc: Stephen J. Turnbull; 'Sean MacLennan'; 'Samuel Bronson';
xemacs-beta(a)xemacs.org
Subject: Re: binding to G keys
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Stephen> ... Based on your report (that you don't see a keysym in the echo
Stephen> area when you press that key) and a look at the
Stephen> implementation, I believe that XEmacs simply doesn't see
Stephen> those keysyms at all, so binding it won't help even if you
Stephen> know what it is. ...
Could it be that the keyboard driver maps those keys some esoteric
feature and don't let it through to XEmacs? From the very little I
have just learned about the keyboard by surfing the net it seems like
the G-keys can be used in gaming to define different kinds of
macros. So the driver is likely to catch the keys!?
I have had similar experience with mouse drivers. Mouses with many
buttons etc comes with a driver that allows you to map the buttons to
different features. With XEmacs I often have to disable the default
behavior, as defined by the driver, tide to the middle button. As an
old X-windows user I like the middle press just to be sent to
XEmacs. Nothing else.
Maybe you are experiencing something similar with the G-keys? Either
you can bind them to some keys that XEmacs do recognise or just
disable any special treatment on them? But I'm just a standard
keyboard user ...
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:05 p.m.
>>>> Sirano Dhe-Paganon
<sirano.dhepaganon(a)utoronto.ca> writes:
Sirano> But, the point of the G keys, I thought, is so that we don't
Sirano> have to tie-up by F-keys or any other keys for that
Sirano> matter. I've already mapped to my commands all of the standard
Sirano> keys (including the use of control , shift, and alt); now I
Sirano> would like to use the G keys. So far, I cannot map the G-keys
Sirano> directly to an xemacs command.
Since it is called macro mapper you might be able to assign a sequence
och key strokes to one G key. Then it is just a matter of assigning
that key sequence to an XEmacs command.
I don't know what is the best command sequence to use but I have bound
keys in the C-x 4 map, ctl-x-4-map, to some personal commands. I also
use the native swedish chars on my keyboard to bind to some good
functions. An extra bonus for us having keyboards with non standard
native chars ;-)
One alternative could be using a sequence with the super modifier, S-,
since that is not bound by default to any command. So that space is
free.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:28 a.m.
Mats Lidell writes:
>>>>> Stephen J Turnbull <stephen(a)xemacs.org>
writes:
Stephen> ... Based on your report (that you don't see a keysym in the echo
Stephen> area when you press that key) and a look at the
Stephen> implementation, I believe that XEmacs simply doesn't see
Stephen> those keysyms at all, so binding it won't help even if you
Stephen> know what it is. ...
Could it be that the keyboard driver maps those keys some esoteric
feature
No. XEmacs in the Windows port has a list of keys that it knows about
and drops the rest on the floor AFAICS. But I'm not a Windows
programmer, somebody who is should take a look.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:47 a.m.
Samuel Bronson writes:
On Wed, Nov 17, 2010 at 12:29 AM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
> You can see old messages by looking at the buffer named
> " *Message-Log*" (the quotation marks are not part of the name, but
> the leading space is significant).
I seem to recall having XEmacs grind to a halt in connection with
having that open in the past.
If you see that happen again, please report it as a bug.
I think I've been assuming that that was
why there was a leading space in the buffer name -- to keep people
from opening it and getting into a state where they might have to exit
XEmacs non-gracefully.
Nope. The idea is to reduce UI clutter. The leading space prevents
it from being listed in the buffer list, which would normally be just
clutter since messages are supposed to be emphemeral, and also
prevents the buffer from interfering with completion of other buffer
names beginning with "*".
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:14 a.m.
Sirano Dhe-Paganon writes:
Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on
Windows-7.
I was hoping something like this in my custom.el file
I hope you mean init.el. Editing custom.el is one of those "Kids,
these are professional stunt men; don't try this at home!" stunts. Of
course, from your point of view, editing those two files has the same
effect.
However, for XEmacs, they are very different. XEmacs never tries to
edit init.el, so it doesn't matter what you put in there, as long as
it is valid Lisp code. It *does* edit custom.el, and like most
software, it is easily confused by the unexpected, even if it is valid
code.
Why is it called "custom.el" if you're not supposed to customize it?
Because the GUI CUSTOMize system uses it.
"(define-key global-map '(E0_17)
'kill-primary-selection)", but ... it
Where did you get that keysym "E0_17"?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:20 p.m.
Stephen,
thank you for the description of init.el and custom.el; I will move all my
scripts from custom.el to init.el, and essentially never manually modify
custom.el.
Sirano
-----Original Message-----
From: xemacs-beta-bounces(a)xemacs.org [mailto:xemacs-beta-bounces＠xemacs.org]
On Behalf Of Stephen J. Turnbull
Sent: Wednesday, November 17, 2010 12:14 AM
To: Sirano Dhe-Paganon
Cc: xemacs-beta(a)xemacs.org
Subject: RE: binding to G keys
Sirano Dhe-Paganon writes:
Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on
Windows-7.
I was hoping something like this in my custom.el file
I hope you mean init.el. Editing custom.el is one of those "Kids,
these are professional stunt men; don't try this at home!" stunts. Of
course, from your point of view, editing those two files has the same
effect.
However, for XEmacs, they are very different. XEmacs never tries to
edit init.el, so it doesn't matter what you put in there, as long as
it is valid Lisp code. It *does* edit custom.el, and like most
software, it is easily confused by the unexpected, even if it is valid
code.
Why is it called "custom.el" if you're not supposed to customize it?
Because the GUI CUSTOMize system uses it.
"(define-key global-map '(E0_17)
'kill-primary-selection)", but ... it
Where did you get that keysym "E0_17"?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:32 p.m.
On Wed, Nov 17, 2010 at 12:14 AM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
Sirano Dhe-Paganon writes:
> Hi Jeff; thanks, but way over my head. I'm using Xemacs-21.4 on Windows-7.
>
> I was hoping something like this in my custom.el file
I hope you mean init.el. Editing custom.el is one of those "Kids,
these are professional stunt men; don't try this at home!" stunts. Of
course, from your point of view, editing those two files has the same
effect.
Does this include removing individual customize settings by simply
deleting them from the file? I sometimes do that...
However, for XEmacs, they are very different. XEmacs never tries to
edit init.el, so it doesn't matter what you put in there, as long as
it is valid Lisp code. It *does* edit custom.el, and like most
software, it is easily confused by the unexpected, even if it is valid
code.
Why is it called "custom.el" if you're not supposed to customize it?
Because the GUI CUSTOMize system uses it.
Maybe it should be created with a comment to that effect at the top?
Of course, that would only help people who are just starting out with
a new ~/.xemacs, but even so...
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:25 a.m.
Samuel Bronson writes:
On Wed, Nov 17, 2010 at 12:14 AM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
> I hope you mean init.el. Editing custom.el is one of those
"Kids,
> these are professional stunt men; don't try this at home!" stunts. Of
> course, from your point of view, editing those two files has the same
> effect.
Does this include removing individual customize settings by simply
deleting them from the file? I sometimes do that...
Dunno. Feel free to read the source of the code that implements
custom.el munging. ;-)
IIRC, however, that may not work if you do other customization via the
M-x customize family. The reason is that basically when you save
settings, it doesn't edit the file, it dumps the current internal
database of customize settings to it. So if you edit customize, then
do custom-save-all in the same session, you lose your manual edits.
Maybe it should be created with a comment to that effect at the top?
Of course, that would only help people who are just starting out with
a new ~/.xemacs, but even so...
Good idea, and probably more effective than you think (see above).
Issue #742 (just a feature request at this point, but it will show up
when people are looking for things to do).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5101
days inactive
5121
days old
18 comments
6 participants
participants (6)
-
Jeff Mincy -
Samuel Bronson -
Sean MacLennan -
Sirano Dhe-Paganon -
Stephen J. Turnbull -
The XEmacs Package Smoketest