From: mycroft@gnu.ai.mit.edu
To: matty@cs.su.OZ.AU (James Matthew Farrow)
Cc: dschieb@muse.CV.NRAO.EDU, rc@hawkwind.utcs.toronto.edu
Subject: Re: $history on plan 9
Date: Sun, 6 Jun 1993 12:20:41 -0400 [thread overview]
Message-ID: <9306061620.AA02886@trinity.gnu.ai.mit.edu> (raw)
In-Reply-To: <19930605202647.22292.frobozz@orthanc.cs.su.OZ.AU> from "James Matthew Farrow" at Jun 5, 93 06:26:33 am
> (How many times have you just wanted to add that `-g' flag to a 5
> line cc line output by make and been foiled by xterm inserting CRs at
> the end of each line?)
Never, since I started using X11R5. Must be about 21 months now.
next prev parent reply other threads:[~1993-06-06 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-04 17:53 Darrell Schiebel
1993-06-05 10:26 ` James Matthew Farrow
1993-06-06 16:20 ` mycroft [this message]
1993-06-06 18:34 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
1993-06-05 0:27 Scott Schwartz
1993-06-04 18:00 Arnold Robbins
1993-06-03 21:57 Byron Rakitzis
1993-06-03 19:51 Arnold Robbins
1993-06-03 19:35 Darrell Schiebel
1993-06-03 19:24 Steve_Kilbane
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=9306061620.AA02886@trinity.gnu.ai.mit.edu \
--to=mycroft@gnu.ai.mit.edu \
--cc=dschieb@muse.CV.NRAO.EDU \
--cc=matty@cs.su.OZ.AU \
--cc=rc@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).