From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] home, end ^h^j^k^l
Date: Tue, 22 May 2001 16:42:31 +0200 [thread overview]
Message-ID: <20010522143538.524C6199C1@mail.cse.psu.edu> (raw)
: But how would you name it? You're inventing a lot of mechanism
: when the problem is already solved well enough.
I think you are right.
But just to clarify, I meant to use the old name for the file---which
would require read() on directories to be able to return more entries
(the deleted ones) if asked to do so. Not worth given we have dump.
next reply other threads:[~2001-05-22 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 14:42 nemo [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 12:36 rob pike
2001-05-22 7:17 nemo
2001-05-22 6:25 nemo
2001-05-22 6:35 ` Scott Merrilees
2001-05-22 8:31 ` Boyd Roberts
2001-05-19 15:39 Re[4]: " rob pike
2001-05-21 16:24 ` Douglas A. Gwyn
2001-05-19 7:54 Re[2]: " Matt H
2001-05-19 17:07 ` Quinn Dunkan
2001-05-19 20:46 ` Re[4]: " Boyd Roberts
2001-05-21 16:24 ` Douglas A. Gwyn
2001-05-21 16:23 ` Douglas A. Gwyn
2001-05-18 20:23 rog
2001-05-18 15:17 Russ Cox
2001-05-21 8:38 ` Douglas A. Gwyn
2001-05-18 10:18 Matt H
2001-05-18 19:26 ` Chris Locke
2001-05-18 19:34 ` Scott Schwartz
2001-05-18 22:28 ` 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=20010522143538.524C6199C1@mail.cse.psu.edu \
--to=nemo@gsyc.escet.urjc.es \
--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).