From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 11 Apr 2009 12:13:55 +0100 From: Eris Discordia To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <7A431F498CA8B94AC201E2F4@[192.168.1.2]> In-Reply-To: <3aaafc130904101233q1b8791f5q52cd41d7eaab639e@mail.gmail.com> References: <7161bf48074fbed7ce78fdaf614b92b8@terzarima.net> <385e002a7435aac5d4428939fc564ac8@hamnavoe.com> <9ab217670904091228i703d5308q6ad7e5ff0987be97@mail.gmail.com> <3aaafc130904091234s55d7410bleaaec0d7277f3b04@mail.gmail.com> <58ADE353D7158CD35973F13B@192.168.1.2> <3aaafc130904101233q1b8791f5q52cd41d7eaab639e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [9fans] a bit OT, programming style question Topicbox-Message-UUID: da175f5e-ead4-11e9-9d60-3106f5b1d025 > 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" wrote: > On Thu, Apr 9, 2009 at 6:09 PM, Eris Discordia > 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" >> 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. >>> >> >> >> >> >> >> >