Re: [9fans] naming conventions

2010-06-14 Thread erik quanstrom
> I can run "9 9term", but what happens when you run something like "9vx -u > glenda -r /some/very/long/path/" and then run "!9vx" the next time to rerun > the last command starting with ? It probably runs the 9'th command in the > history. Sorry I was not clear. I consider this a minor his is a

Re: [9fans] naming conventions

2010-06-14 Thread EBo
On Mon, 14 Jun 2010 21:10:38 +, hiro <23h...@googlemail.com> wrote: > I tried running 9 9term in bash and had no problems. > Perhaps you haven't set up your $PATH correctly? I can run "9 9term", but what happens when you run something like "9vx -u glenda -r /some/very/long/path/" and then run

Re: [9fans] naming conventions

2010-06-14 Thread hiro
I tried running 9 9term in bash and had no problems. Perhaps you haven't set up your $PATH correctly?

Re: [9fans] naming conventions

2010-06-14 Thread Nick LaForge
Would a phonetic morphology à la the ceePlusPlus of wiki would suffice for our lexically challenged friends?

Re: [9fans] naming conventions

2010-06-14 Thread Stanley Lieber
On Mon, Jun 14, 2010 at 8:47 AM, EBo wrote: > >> your shell is broken.  [0-9] are perfectly valid anywhere in a unix file >> name. > > does bash completion work for you on *anything*?  Or does it get confused > thinking that you are specifying a previous command (!### in the history)? > Yes, a fil

Re: [9fans] naming conventions

2010-06-14 Thread erik quanstrom
> does bash completion work for you on *anything*? that's a purely theoretical question. i use rc. - erik

Re: [9fans] naming conventions

2010-06-14 Thread EBo
> your shell is broken. [0-9] are perfectly valid anywhere in a unix file > name. does bash completion work for you on *anything*? Or does it get confused thinking that you are specifying a previous command (!### in the history)? Yes, a file/script named [0-9]* is valid, but still breaks thing

Re: [9fans] naming conventions

2010-06-14 Thread erik quanstrom
> 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 broke

Re: [9fans] naming conventions

2010-06-14 Thread Charles Forsyth
>Is it more reasonable in this case to name the executive vx32 instead of >9vx since it is a plan 9 emulator for linux? not really, because vx32 is the library, and 9vx is just one sample application. (there are others.)

[9fans] naming conventions

2010-06-14 Thread EBo
I do not mean to feed any trolls with this one, but I need to know how people what some of this addressed in the future. 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 linu