From: dnied@tiscali.it (Dario Niedermann)
Subject: [TUHS] the origin of dotfiles
Date: Sun, 19 Aug 2012 00:46:23 +0200 [thread overview]
Message-ID: <50301b3f.ZZmPbBROqUcYLlK2%dnied@tiscali.it> (raw)
In-Reply-To: <20120818175100.GA19098@DataIX.net>
Jason Hellenthal <jhellenthal at dataix.net> wrote:
> With all due respect to Rob Pike, I really do not find it all that
> interesting. .files being no different than any other file other than
> not being displayed in a listing ? it seriously makes utterly no
> difference other than the human PoV. Just because "We did it in Plan
> 9" does mean squat other than "We did it differently".
IMO the interesting - and funny - part is that dotfiles were born as an
unintended side effect of a flagrant kludge.
DN
next prev parent reply other threads:[~2012-08-18 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 5:13 Kuroishi Mitsuo
2012-08-18 17:51 ` Jason Hellenthal
2012-08-18 18:49 ` Ori Idan
2012-08-18 19:07 ` sl
2012-08-18 19:16 ` Lyndon Nerenberg
2012-08-18 22:46 ` Dario Niedermann [this message]
2012-08-18 23:08 ` Tim Newsham
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=50301b3f.ZZmPbBROqUcYLlK2%dnied@tiscali.it \
--to=dnied@tiscali.it \
/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).