From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] naming conventions
Date: Mon, 14 Jun 2010 09:32:40 -0400 [thread overview]
Message-ID: <b3ff81f04ee52820237c23ead451c137@kw.quanstro.net> (raw)
In-Reply-To: <2bca08f7e5b22db500c54deb4b58bc0c@swcp.com>
> I've been catching a little flack off and on about the Plan 9's naming
> convention of adding a '9' in front of program names. I've also noticed
> that using emulators, on the linux side, prefixing a 9 breaks history
> utilization functionality in most of the shells I use.
your shell is broken. [0-9] are perfectly valid anywhere in a unix file
name.
- erik
next prev parent reply other threads:[~2010-06-14 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:29 EBo
2010-06-14 9:01 ` Charles Forsyth
2010-06-14 13:32 ` erik quanstrom [this message]
2010-06-14 13:47 ` EBo
2010-06-14 15:16 ` Stanley Lieber
2010-06-14 15:19 ` erik quanstrom
2010-06-14 15:35 ` Nick LaForge
2010-06-14 21:10 ` hiro
2010-06-14 21:24 ` EBo
2010-06-14 21:32 ` erik quanstrom
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=b3ff81f04ee52820237c23ead451c137@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).