From: Scott Schwartz <schwartz@groucho.cse.psu.edu>
To: pete@minster.york.ac.uk
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 13:47:07 -0400 [thread overview]
Message-ID: <93Jul21.134625edt.2591@groucho.cse.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 21 Jul 1993 12:11:48 EDT." <swordfish.743268100@minster.york.ac.uk>
| 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.
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.
next prev parent reply other threads:[~1993-07-21 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-07-21 16:11 pete
1993-07-21 17:47 ` Scott Schwartz [this message]
1993-07-21 21:52 pete
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=93Jul21.134625edt.2591@groucho.cse.psu.edu \
--to=schwartz@groucho.cse.psu.edu \
--cc=9fans@cs.psu.edu \
--cc=pete@minster.york.ac.uk \
--cc=sam-fans@hawkwind.utcs.toronto.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).