From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
To: arnold@skeeve.atl.ga.us
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: X11R6?
Date: Thu, 19 Jan 1995 02:30:21 -0500 [thread overview]
Message-ID: <95Jan19.023034est.12685@galapagos.cse.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 18 Jan 1995 22:02:21 EST." <m0rUn8f-00013yC@skeeve.atl.ga.us>
| Greetings. I've been wondering if X11R6 has enough new stuff / performance
| enhancements to be worth the switch?
It's definately bigger and not noticably faster.
The most concrete advantages are that the fonts are somewhat nicer and
the font server works a little better, and it supports the Sun type 5
keyboard properly. (Properly means all the keys have keysyms bound,
and there are keysyms like SunXK_VideoLowerBrightness to go with the
new keys.)
| Is R6 worth the trouble to get, compile overnight, rebuild sam/9term/9wm,
| and in general switch?
How bored are you feeling? :-)
prev parent reply other threads:[~1995-01-19 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-01-19 3:02 X11R6? arnold
1995-01-19 7:30 ` Scott Schwartz [this message]
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=95Jan19.023034est.12685@galapagos.cse.psu.edu \
--to=schwartz@galapagos.cse.psu.edu \
--cc=arnold@skeeve.atl.ga.us \
--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).