From: ori@helicontech.co.il (Ori Idan)
Subject: [TUHS] the origin of dotfiles
Date: Sat, 18 Aug 2012 21:49:15 +0300 [thread overview]
Message-ID: <CACyhTRFOXTpbJzO+PRs02O-OB2Eip7EwUHkOB0mcbd=32kmQkA@mail.gmail.com> (raw)
In-Reply-To: <20120818175100.GA19098@DataIX.net>
On Sat, Aug 18, 2012 at 8:51 PM, Jason Hellenthal <jhellenthal at dataix.net>wrote:
> On Fri, Aug 17, 2012 at 02:13:00PM +0900, Kuroishi Mitsuo wrote:
> >
> > Hi. Just FYI.
> >
> > It's an interesting article about the origin of dotfiles.
> >
> > https://plus.google.com/101960720994009339267/posts/R58WgWwN9jp
> >
>
> 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".
>
> $ ls -A |grep ^\\. |wc -l
> 108
>
> All of which I know how they got there and why they are there.
>
>
> You have to keep in mind that the old UNIX systems did not have all the
> crap that has evolved today for "Desktop" use and programmers in any
> given situation will leverage all aspects available in any environment
> to achieve a goal, just as Plan 9 does.
>
>
> Just out of curiosity, how does plan 9 handles it?
Are there hidden files there? I am sure there are but how are they handled?
--
Ori Idan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20120818/4b83d9e5/attachment.html>
next prev parent reply other threads:[~2012-08-18 18:49 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 [this message]
2012-08-18 19:07 ` sl
2012-08-18 19:16 ` Lyndon Nerenberg
2012-08-18 22:46 ` Dario Niedermann
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='CACyhTRFOXTpbJzO+PRs02O-OB2Eip7EwUHkOB0mcbd=32kmQkA@mail.gmail.com' \
--to=ori@helicontech.co.il \
/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).