From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: Slightly OT: Where are keycodes defined for emacs -nw in X-Windows?
Date: 28 Oct 2003 13:17:13 GMT [thread overview]
Message-ID: <bnlq8p$kgj$1@news1.radix.net> (raw)
In-Reply-To: 0lflnb.16.ln@acm.acm
Alan Mackenzie <none@example.invalid> wrote:
> Thomas Dickey <dickey@saltmine.radix.net> wrote on 26 Oct 2003 16:15:57
> GMT:
>> Alan Mackenzie <none@example.invalid> wrote:
>>> On my xterm, the modifier keys get filtered out, so that C-up and up
>>> degenerate into the same event sequence. :-(
>> a vt102, you may recall, doesn't have modifiers...
> Well, funnily enough, in the twenty years since I last used one, that
> fact seemed to have slipped my mind. ;-) The next question, of course,
> is why on earth are we emulating a VT102, when "we" just want a command
> line window? Maybe I should look for a different emulator, "linux-term"
> (or whatever).
oddly enough, Linux console uses modifiers less than xterm.
XFree86 xterm keyboard handling normally (the default resource settings),
does use modifiers (but your posting implied that you're not seeing that
behavior).
as for why (vt102 - or vt220) because it simplifies using systems that
people occasionally find useful. A complete redesign won't solve that
problem.
>> start with man X11.
> I Haven't got it. Haven't got "man x11" either, but "man X" works.
> Maybe that's because my system is very old. In that manual page they go
> with the "warm cosy feeling" approach too:
it seems to depend on the system - I was quoting from Solaris' xterm manpage
xterm control sequences is not a manpage - there's an nroff-formatted copy off
my webpage (but it looks nicer in postscript).
> From X man page:
>> To make the tailoring of applications to personal preferences easier,
>> X provides a mechanism for storing default values for program
>> resources (e.g. background color, window title, etc.) Resources are
>> specified as strings that are read in from various places when an
>> application is run.
> So, one can store default values of program "resources"; but still no
> sentence which has "resource" as the subject and "is" as the verb. I
> think "resource" is the X11 term for what sensible programs call
> "settings" or "options" (or "customizable variables" ;-) and patronising
> programs call "preferences". It would be nice to be told, though, rather
> than having to pick it up osmotically.
like all jargon - it's simple if you're familiar with it.
(and once familiar, one forgets that it's jargon).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
next prev parent reply other threads:[~2003-10-28 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 19:03 Slightly OT: Where are keycodes defined for emacs -nw in X-Windows? Alan Mackenzie
2003-10-24 19:25 ` Barry Margolin
2003-10-24 20:15 ` Stefan Monnier
2003-10-24 20:19 ` Stefan Monnier
2003-10-26 10:19 ` Alan Mackenzie
2003-10-26 16:15 ` Thomas Dickey
2003-10-28 10:16 ` Alan Mackenzie
2003-10-28 13:17 ` Thomas Dickey [this message]
2003-10-28 15:21 ` Barry Margolin
2003-10-27 9:50 ` Gian Uberto Lauri
[not found] ` <mailman.2518.1067256787.21628.help-gnu-emacs@gnu.org>
2003-10-27 15:56 ` Stefan Monnier
2003-12-03 22:20 ` Kai Grossjohann
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='bnlq8p$kgj$1@news1.radix.net' \
--to=dickey@saltmine.radix.net \
/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).