From: Matt H <matt@proweb.co.uk>
To: 9fans <9fans@cse.psu.edu>
Subject: Re[6]: [9fans] home, end ^h^j^k^l
Date: Sat, 19 May 2001 09:59:51 +0100 [thread overview]
Message-ID: <156148413998.20010519095951@proweb.co.uk> (raw)
In-Reply-To: <20010519084851.67E2119A18@mail.cse.psu.edu>
Hello Russ,
>> To: Russ Cox <9fans@cse.psu.edu>
oh sorry it's my email program being too clever
same with the subject line re[count++] idea
oh btw
cpu% upas/fs -f/pop3/post.proweb.co.uk/matt
upas/fs: opening mailbox: file does not exist
Which file? Vintage error message :-)
Since my patch problems I don't trust I have the latest version of
anything and that looks like the case here.
--
Best regards,
Matt mailto:matt@proweb.co.uk
next prev parent reply other threads:[~2001-05-19 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 8:48 Re[4]: " Russ Cox
2001-05-19 8:59 ` Matt H [this message]
2001-05-19 20:28 ` Boyd Roberts
2001-05-19 14:14 rob pike
2001-05-19 14:26 ` Re[6]: " Matt H
2001-05-23 8:24 ` Re[4]: " Randolph Fritz
2001-05-23 8:46 ` Re[6]: " Matt H
2001-05-23 9:04 ` Boyd Roberts
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=156148413998.20010519095951@proweb.co.uk \
--to=matt@proweb.co.uk \
--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).