From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] External Monitors on Laptops
Date: Mon, 27 Nov 2000 13:20:02 -0500 [thread overview]
Message-ID: <20001127182004.1D2C9199DD@mail.cse.psu.edu> (raw)
I've used them once in a while. They are in fact
unpredictable and quick to anger. We don't have
a good interface for setting two sets of registers:
one for the LCD and one for the external monitor.
I have some ideas about how to fix it, but it hasn't
been pressing. It's on the vga todo list.
If anyone else wants to beat me to it...
Russ
next reply other threads:[~2000-11-27 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 18:20 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-27 17:54 Eric Van Hensbergen
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=20001127182004.1D2C9199DD@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@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).