From: dmr@plan9.bell-labs.com (Dennis Ritchie)
Subject: [TUHS] The nameless horror of dotfiles [was (no subject)]
Date: Sat, 24 May 2003 00:17:52 -0400 [thread overview]
Message-ID: <c799721951ed6dacbac364b8dcd0ef78@plan9.bell-labs.com> (raw)
The omniscient Norman seems to have nailed me:
> Judging by the manuals, Research did it first. In every manual from
> 1/e to 6/e, the entry for ls(I) has this description for the -a option:
> list all entries; usually those beginning with "." are suppressed
I suspect that in v7 (where .thing was indeed listed by default)
we decided that since .thing was a real file in the
directory it was better to list it instead of hiding it
by default. (Seeing . and .. seemed seldom interesting,
however).
I was solely (and much more recently) responsible for the lack
of subject header in my earlier reply.
Dennis
next reply other threads:[~2003-05-24 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 4:17 Dennis Ritchie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 13:40 Norman Wilson
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=c799721951ed6dacbac364b8dcd0ef78@plan9.bell-labs.com \
--to=dmr@plan9.bell-labs.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).