[4051] in testers
update_ws, rel-notes, printing
daemon@ATHENA.MIT.EDU (Jeremy Daniel)
Wed May 19 19:11:38 1999
Date: Wed, 19 May 1999 19:11:29 -0400 (EDT)
Message-Id: <199905192311.TAA01404@oliver.mit.edu>
From: Jeremy Daniel <jdaniel@MIT.EDU>
To: testers@MIT.EDU
update_ws
---------
update_ws gives a bunch of errors involving no krb tickets and can't
sub. I assume we're running attach in various places? Maybe we
should run it with the option not to try to sub if so.
release-notes
-------------
>xscreensaver & - & 3.08 \\
xscreensaver (as xss) & - & 3.08 \\
Though it's mentioned later in the itemized section so I guess it's
not necessary
Emacs:
perhaps mention M-x customize
line 420>\item The of handling filesystem options (primarily used for NFS
^ word missing? "way"?
Emacs Discuss:
>\item Font-lock support has been added.
I hardly call making From and Subject bold "adding support" was
anything else done? Maybe font-lock-keywords should be stolen from
one of the mail packages.
>\item discuss-invisible-headers ...
It's probably a bit late for a feature request, but it would be nice
if there was a key you could push to show all headers on this message.
>\item If discuss-use-short-meeting-name ...
Any reason not to make this the default? It's nice to have this, I
had hacked it in my own elisp a while ago.
>\item Where possible, workstations will present a 24-bit default
>visual (in the case of 24-bit capable Ultra 5s, that's the only
>visual). If a user needs to run an application which doesn't work in
>a 24-bit visual, the user can select ``Restart X in 8-bit mode'' in
>the other logins options menu before logging in.
After restarting in 8-bit mode the option is still available and
there's no obvious way to tell it's in 8-bit mode (if a user hits it
and walks away from the machine). There should be an obvious option
to go back to 24 once in 8.
[I tried this on savage which might actually not have an 24 bit mode
in the first place ... I didn't have access to a more recent machine
to check on.]
printing
--------
Re: lxs observations ... it somehow does seem to be LPROPT's fault ...
oliver:~--> echo $LPROPT
-h -z
oliver:~--> echo foo | \lpr
Warning - Cannot open file 'l', No such file or directory
meadow: nothing to print
oliver:~--> unsetenv LPROPT
oliver:~--> echo foo | \lpr
[command succeeds]
lpq seems to hang, perhaps this is because meadow is still Q'd off a
non LPRng server
