From: pete@minster.york.ac.uk
To: pete@minster.york.ac.uk, schwartz@groucho.cse.psu.edu
Cc: 9fans@cs.psu.edu, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: libXg and caps lock on Sun type V keyboard under openwindows
Date: Wed, 21 Jul 1993 17:52:49 -0400 [thread overview]
Message-ID: <swordfish.743288490@minster.york.ac.uk> (raw)
From schwartz@groucho.cse.psu.edu Wed Jul 21 13:47:07 0400 1993
[I said]
>| As far as I'm concerned this is only a minor irritant -- Caps Lock is
>| pointless anyway in these days of OPERATING SYSTEMS THAT DON'T REQUIRE
>| YOU TO SHOUT -- but I wondered if anyone else had noticed this bug-ette
>| and/or had a fix for it?
>It doesn't show up here, running MIT X11.
I tried re-linking against MIT X11R4 libraries rather than the Openwindows
ones, with the same result. I guess it's an Openwindows 2 server
``feature''. Sigh.
>In terms of shouting, if you use MODULA-3, encrusted as it is with
>upper case keywords, caps-lock is about the only alternative (and a
>poor one at that) to a context sensitive editor like emacs.
Hmmm.... I think if I was using sam to edit a language which required upper
case I'd knock together some sort of filter to do the capitalisation and
pipe the file through it before a write... that's what the '|' command is
there for! Couple of extra keystrokes perhaps (maybe only one if you're
using the keyboard extensions to sam) and it avoids the dreaded emacs...
pete
--
Peter Fenelon - Research Associate - High Integrity Systems Engineering Group,
Dept. of Computer Science, University of York, York, Y01 5DD +44 (0)904 433388
EMAIL: pete@minster.york.ac.uk `There's no room for enigmas in built-up areas'
next reply other threads:[~1993-07-21 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-07-21 21:52 pete [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-07-21 16:11 pete
1993-07-21 17:47 ` Scott Schwartz
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=swordfish.743288490@minster.york.ac.uk \
--to=pete@minster.york.ac.uk \
--cc=9fans@cs.psu.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
--cc=schwartz@groucho.cse.psu.edu \
/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).