From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a bit OT, programming style question
Date: Sat, 11 Apr 2009 12:13:55 +0100 [thread overview]
Message-ID: <7A431F498CA8B94AC201E2F4@[192.168.1.2]> (raw)
In-Reply-To: <3aaafc130904101233q1b8791f5q52cd41d7eaab639e@mail.gmail.com>
> No, bash's completion system is what's responsible for line numbers in
> the thousands.
How? Is bash's completion on your system different than on my system? I'd
like you to substantiate that statement and will thank you for a proper
response.
--On Friday, April 10, 2009 3:33 PM -0400 "J.R. Mauro" <jrm8005@gmail.com>
wrote:
> On Thu, Apr 9, 2009 at 6:09 PM, Eris Discordia <eris.discordia@gmail.com>
> wrote:
>>> It only starts to balloon once you begin customizing bash.
>>
>> Have you customized your bash by aliases as long as tens or hundreds of
>> lines? Now is it bash's fault you have defined an alias for something
>> that ought to be a script/program in its own right?
>
> No, bash's completion system is what's responsible for line numbers in
> the thousands.
>
>>
>> --On Thursday, April 09, 2009 3:34 PM -0400 "J.R. Mauro"
>> <jrm8005@gmail.com> wrote:
>>
>>>> No, it's very likely bigger. wc -l is lines of course, and I'm
>>>> guessing each line is more than 1 character. However,
>>>>
>>>> $ set | wc -l
>>>> 64
>>>>
>>>> I don't quite get that locally.
>>>
>>> It only starts to balloon once you begin customizing bash. I'm not
>>> sure how rc handles functions, but the nice thing about zsh is that it
>>> compiles them to bytecode instead of this insanity that bash employs.
>>>
>>
>>
>>
>>
>>
>>
>
next prev parent reply other threads:[~2009-04-11 11:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 5:32 Corey
2009-04-07 5:39 ` erik quanstrom
2009-04-07 7:53 ` sqweek
2009-04-07 7:28 ` Eris Discordia
[not found] ` <3AB58E51F3A5C561C4B065E3@192.168.1.2>
2009-04-07 14:31 ` sqweek
2009-04-07 15:09 ` ron minnich
2009-04-07 18:21 ` Eris Discordia
[not found] ` <A297371273CD8D67A21A921E@192.168.1.2>
2009-04-07 19:57 ` J.R. Mauro
2009-04-08 1:48 ` Eris Discordia
2009-04-08 2:53 ` erik quanstrom
[not found] ` <A411EFAE2566F856F3034B12@192.168.1.2>
2009-04-08 3:04 ` J.R. Mauro
2009-04-09 13:44 ` Eris Discordia
2009-04-09 15:06 ` erik quanstrom
2009-04-09 22:34 ` Eris Discordia
2009-04-10 16:15 ` john
2009-04-17 13:07 ` Balwinder S Dheeman
2009-04-17 13:28 ` erik quanstrom
2009-04-17 13:42 ` Devon H. O'Dell
[not found] ` <3F6B6589F529BEAECE105A71@192.168.1.2>
2009-04-10 19:35 ` J.R. Mauro
[not found] ` <5EF90081E9B1D745047218E6@192.168.1.2>
2009-04-09 17:32 ` J.R. Mauro
2009-04-09 18:10 ` Charles Forsyth
2009-04-09 18:28 ` Richard Miller
2009-04-09 19:28 ` Devon H. O'Dell
2009-04-09 19:31 ` erik quanstrom
2009-04-09 19:34 ` J.R. Mauro
2009-04-09 22:09 ` Eris Discordia
[not found] ` <58ADE353D7158CD35973F13B@192.168.1.2>
2009-04-10 19:33 ` J.R. Mauro
2009-04-11 11:13 ` Eris Discordia [this message]
2009-04-09 21:01 ` Richard Miller
2009-04-09 21:28 ` Bakul Shah
2009-04-09 21:34 ` J.R. Mauro
2009-04-09 22:16 ` erik quanstrom
2009-04-09 22:37 ` Devon H. O'Dell
2009-04-09 22:05 ` Eris Discordia
2009-04-07 15:08 ` ron minnich
2009-04-07 16:05 ` Corey
2009-04-07 16:44 ` ron minnich
2009-04-07 18:34 ` erik quanstrom
2009-04-07 22:50 ` dave.l
2009-04-07 22:56 ` 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='7A431F498CA8B94AC201E2F4@[192.168.1.2]' \
--to=eris.discordia@gmail.com \
--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).