From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] export TERM=aaa-60
Date: Sat, 22 Oct 2016 11:02:42 -0500 [thread overview]
Message-ID: <CAC20D2OvNGXbeMN5kyURMVPSLDWvPuoPBY3mcW3zogEm=EWHMQ@mail.gmail.com> (raw)
In-Reply-To: <20161022155850.4662C18C0BC@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
On Sat, Oct 22, 2016 at 10:58 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> my old eyes prefer black on white
Fair enough.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161022/32429d4d/attachment.html>
next prev parent reply other threads:[~2016-10-22 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 15:58 Noel Chiappa
2016-10-22 16:02 ` Clem Cole [this message]
2016-10-22 23:09 ` Greg 'groggy' Lehey
2016-10-23 0:04 ` Steve Nickolas
-- strict thread matches above, loose matches on Subject: below --
2016-10-22 5:10 Ramakrishnan Muthukrishnan
2016-10-22 14:00 ` Clem Cole
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='CAC20D2OvNGXbeMN5kyURMVPSLDWvPuoPBY3mcW3zogEm=EWHMQ@mail.gmail.com' \
--to=clemc@ccc.com \
/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).