Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Gnus v5.6.24 is released
Date: 15 Jul 1998 18:32:25 +0200	[thread overview]
Message-ID: <kigbtqrm5wm.fsf@jagor.srce.hr> (raw)
In-Reply-To: Dave Love's message of "Tue, 14 Jul 1998 19:33:18 GMT"

Dave Love <d.love@dl.ac.uk> writes:

> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:
> 
>  Hrvoje> In XEmacs, [(meta tab)] binding will do the right thing on TTY's.
> 
> Out of interest, and not able to experiment, will "\M-\t" not DTRT in
> XEamcs?

Here is what happens in XEmacs:

(define-key MAP "\M-\t" 'foo)
  ; binds M-C-i and M-tab to `foo'

(define-key MAP [(meta tab)] 'foo)
  ; binds M-tab (but not M-C-i!) to `foo'

(define-key MAP '(meta tab) 'foo)
  ; shorthand for previous

(define-key MAP [(meta control i)] 'foo)
  ; bind M-C-i (but not M-tab!) to `foo'

So, if you use the "old" string notation, you get the old semantics
(C-i and TAB being the same).  If you use the "new" vector notation,
you get new semantics (difference between C-i and TAB).  This is a
feature.

Under TTY's, however, C-i is treated exactly the same as TAB, so all
of the above examples bind ?\M-C-i or `ESC C-i' to `foo'.


Look at the XEmacs docs of `define-key' for more explanation of this
(I can mail the docs to you if you don't have XEmacs handy.)

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Lost in Static 18 / And the storm is closing in now


  reply	other threads:[~1998-07-15 16:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-11  1:06 Lars Magne Ingebrigtsen
1998-07-11 21:17 ` Berry Kercheval
1998-07-11 21:27   ` Lars Magne Ingebrigtsen
1998-07-11 22:55     ` Bruce Stephens
1998-07-11 23:05       ` SL Baur
1998-07-12 17:29         ` Dave Love
1998-07-12 17:36           ` Hrvoje Niksic
     [not found]             ` <x77m1ifwei.fsf@peorth.gweep.net>
1998-07-13  2:31               ` Bud Rogers
1998-07-14 19:46               ` Dave Love
1998-07-14 19:33             ` Dave Love
1998-07-15 16:32               ` Hrvoje Niksic [this message]
1998-07-12 18:40           ` Dave Love
1998-07-13  9:03       ` Mats Lofdahl
1998-07-13 12:10         ` Vladimir Volovich
     [not found]           ` <x7emvpbbov.fsf@peorth.gweep.net>
1998-07-14  1:06             ` Aaron M. Ucko
     [not found]               ` <x7u34kgsam.fsf@peorth.gweep.net>
1998-07-15  0:02                 ` Aaron M. Ucko
     [not found]                   ` <x73ec37s53.fsf@peorth.gweep.net>
1998-07-15  3:11                     ` Alan Shutko
     [not found]                       ` <x77m1fj7t2.fsf@peorth.gweep.net>
1998-07-15 19:02                         ` Alan Shutko
     [not found]                           ` <x7btqqvlru.fsf@peorth.gweep.net>
1998-07-15 23:01                             ` Alan Shutko
     [not found]                               ` <x7u34i8tcb.fsf@peorth.gweep.net>
1998-07-16 10:58                                 ` Robert Bihlmeyer
1998-07-14  9:35           ` Mats Lofdahl
1998-07-14 14:20             ` Aaron M. Ucko
1998-07-14 18:05             ` SL Baur
1998-07-16  6:29               ` Yair Friedman
1998-07-13 15:18         ` Hrvoje Niksic
1998-07-14 10:05         ` Kai Grossjohann
1998-07-14 11:36           ` François Pinard
1998-07-14 12:00             ` Kai Grossjohann
1998-07-23 13:09 ` Jochen_Hayek
1998-07-23 13:48 ` Jochen_Hayek
1998-07-23 14:02   ` Kai Grossjohann
1998-07-23 14:21     ` Jochen_Hayek

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=kigbtqrm5wm.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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 NNTP newsgroup(s).