ls output

2011-05-12 Thread David Henderson
Gang, I'm working with the 'ls' command and noticed some inconsistencies among the 'ls --help' and the generated output. I have a directory tree that contains some hidden files so I modify the 'ls' commands to show/hide them, however, the commands don't appear to be working correctly. Here's

Re: ls output

2011-05-12 Thread Harald Becker
Hallo David! ... again ;-) > It appears as though '-A' also shows hidden files, but that defeats > the purpose of the '-a' command. Bug perhaps? No bug. It is exactly what '-A' shall do, else suppression of '.' and '..' doesn't show up either (they start wit a dot, that is they are hidden). The

Re: ls output

2011-05-12 Thread Bob Dunlop
Hi, On Thu, May 12 at 10:26, David Henderson wrote: > Gang, I'm working with the 'ls' command and noticed some inconsistencies ... Well ls output is working correctly for me on 1.18.3. Have you compared it against full blown ls on another box ? I think the problem is tha

Re: ls output

2011-05-12 Thread Ralf Friedl
Harald Becker wrote: To show all of the files in a single column without showing the . and .. directories, I would use 'ls -AR1', however the . and .. directories are still showing up in the listing. Looks like a bug, combining '-A' and '-R'. That would be a bug, but I can't reproduce i

Re: ls output

2011-05-12 Thread Douglas Mencken
Works for me too: $ ls -AR1 | grep "\.\." $ It of course lists .: and then current dir's contents, but that's exactly how coreutils' ls works. ls -aR1, however, lists .., as expected: $ ls -aR1 | grep "\.\." .. .. ___ busybox mailing list busybox@busy

Re: ls output

2011-05-12 Thread David Henderson
On 05/12/2011 11:10 AM, Ralf Friedl wrote: Harald Becker wrote: To show all of the files in a single column without showing the . and .. directories, I would use 'ls -AR1', however the . and .. directories are still showing up in the listing. Looks like a bug, combining '-A' and '-R'. That w

Re: ls output

2011-05-12 Thread Harald Becker
Hi Ralf! > > Looks like a bug, combining '-A' and '-R'. > That would be a bug, but I can't reproduce it. Me too, at least my 1.16.0 on the mail machine can't reproduce the problem David described. -- Harald ___ busybox mailing list busybox@busybox.net

Re: ls output

2011-05-12 Thread David Henderson
On 05/12/2011 11:07 AM, Bob Dunlop wrote: I think the problem is that -A does not mean what you expect. It's a modified version of -a which shows all hidden files except "." and "..". The problem is expressing these concepts concisely in what is already a very big help message. Perhaps:

Re: ls output

2011-05-12 Thread Denys Vlasenko
On Thu, May 12, 2011 at 5:42 PM, David Henderson wrote: > On 05/12/2011 11:07 AM, Bob Dunlop wrote: >> >> I think the problem is that -A does not mean what you expect.  It's a >> modified version of -a which shows all hidden files except "." and "..". >> >> The problem is expressing these concepts

Re: ls output

2011-05-12 Thread David Henderson
On 05/12/2011 12:20 PM, Denys Vlasenko wrote: On Thu, May 12, 2011 at 5:42 PM, David Henderson wrote: On 05/12/2011 11:07 AM, Bob Dunlop wrote: I think the problem is that -A does not mean what you expect. It's a modified version of -a which shows all hidden files except "." and "..". The p

Re: ls output

2011-05-12 Thread Harald Becker
Hallo David! > Any chance of getting '--hide' implemented? IMHO No ... it would increase Busybox size be a reasonable amount of size ... and I never used --hide (like many others, don't think that ls option is very popular) ... have you ever tried to use find, it allows complex selections of inc

Re: ls output

2011-05-12 Thread David Henderson
On 05/12/2011 02:20 PM, Harald Becker wrote: Hallo David! Any chance of getting '--hide' implemented? IMHO No ... it would increase Busybox size be a reasonable amount of size ... and I never used --hide (like many others, don't think that ls option is very popular) ... have you ever tried t

Re: ls output

2011-05-12 Thread Harald Becker
Hallo David! > I'm not sure how much it would increase the size of BB, ... I can't tell that either, without looking for details of implementation. > but I wouldn't think much since the 'ls' command already processes > regex's. Something like this in bash/perl would take a few lines at best In

Re: ls output

2011-05-12 Thread Ralf Friedl
David Henderson wrote: I'm not sure how much it would increase the size of BB, but I wouldn't think much since the 'ls' command already processes regex's. Well, where exactly does 'ls' already processes regex's? Ralf ___ busybox mailing list busybox@b

Re: ls output

2011-05-13 Thread David Henderson
On 05/12/2011 05:11 PM, Ralf Friedl wrote: David Henderson wrote: I'm not sure how much it would increase the size of BB, but I wouldn't think much since the 'ls' command already processes regex's. Well, where exactly does 'ls' already processes regex's? Ralf Taken directly from the 'ls --he

Re: ls output

2011-05-13 Thread Ralf Friedl
David Henderson wrote: On 05/12/2011 05:11 PM, Ralf Friedl wrote: David Henderson wrote: I'm not sure how much it would increase the size of BB, but I wouldn't think much since the 'ls' command already processes regex's. Well, where exactly does 'ls' already processes regex's? Ralf Taken di

Re: ls output

2011-05-13 Thread David Henderson
On 05/13/2011 08:45 AM, Ralf Friedl wrote: David Henderson wrote: On 05/12/2011 05:11 PM, Ralf Friedl wrote: David Henderson wrote: I'm not sure how much it would increase the size of BB, but I wouldn't think much since the 'ls' command already processes regex's. Well, where exactly does 'ls'

Re: ls output

2011-05-13 Thread David Henderson
On 05/13/2011 09:01 AM, David Henderson wrote: On 05/13/2011 08:45 AM, Ralf Friedl wrote: David Henderson wrote: On 05/12/2011 05:11 PM, Ralf Friedl wrote: David Henderson wrote: I'm not sure how much it would increase the size of BB, but I wouldn't think much since the 'ls' command already p

Re: ls output

2011-05-13 Thread Gilles Espinasse
- Original Message - From: "David Henderson" To: "Ralf Friedl" Cc: Sent: Friday, May 13, 2011 3:19 PM Subject: Re: ls output > On 05/13/2011 09:01 AM, David Henderson wrote: > > On 05/13/2011 08:45 AM, Ralf Friedl wrote: > >> David Henderson wro

Re: ls output

2011-05-13 Thread David Henderson
On 05/12/2011 04:31 PM, Harald Becker wrote: Hallo David! I'm not sure how much it would increase the size of BB, ... I can't tell that either, without looking for details of implementation. but I wouldn't think much since the 'ls' command already processes regex's. Something like this in

'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-01 Thread Tomasz Czapiewski
Hi, I have replaced BusyBox 1.2.1 with 1.18.1 yestarday on one embedded machine and I've encountered problems using FISH connection from Midnight Commander on PC to Dropbear SSH server on embedded machine. All the file and dir names (including '.' and '..') are ending with: '\"\ \ ' - quotatio

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-01 Thread Ed W
On 01/04/2011 22:00, Tomasz Czapiewski wrote: > Unfortunately I don't know how MC executes 'ls' command (which arguments). > I couldn't get the problematic output with 'ls' or 'ls -al' or other > arguments so can't track where's the problem myself. No idea, but it occurs to me that if it's an ssh

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-01 Thread Denys Vlasenko
On Friday 01 April 2011 23:00, Tomasz Czapiewski wrote: > Hi, > I have replaced BusyBox 1.2.1 with 1.18.1 yestarday on one embedded machine > and > I've encountered problems using FISH connection from Midnight Commander on PC > to Dropbear SSH server on embedded machine. > > All the file and di

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-02 Thread Sergey Naumov
It seems that it is problem of new mc. I have similar problems with mc from Debian 6.0.0 and openssh. mc from debian 5.0.0 works fine with my busybox-based system. Sergey Naumov. 2011/4/2 Tomasz Czapiewski : > Hi, > I have replaced BusyBox 1.2.1 with 1.18.1 yestarday on one embedded machine > and

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-02 Thread Rich Felker
On Sat, Apr 02, 2011 at 08:40:08PM +0400, Sergey Naumov wrote: > It seems that it is problem of new mc. I have similar problems with mc > from Debian 6.0.0 and openssh. mc from debian 5.0.0 works fine with my > busybox-based system. Parsing ls Output Considered Harmf

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-02 Thread Tomasz Czapiewski
On Sat, 2 Apr 2011, Sergey Naumov wrote: It seems that it is problem of new mc. I have similar problems with mc from Debian 6.0.0 and openssh. mc from debian 5.0.0 works fine with my busybox-based system. Sergey Naumov. Thanks for info, but I haven't upgraded MC in last few moths (it's defaul

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-02 Thread Tomasz Czapiewski
On Sat, 2 Apr 2011, Sergey Naumov wrote: It seems that it is problem of new mc. I have similar problems with mc from Debian 6.0.0 and openssh. mc from debian 5.0.0 works fine with my busybox-based system. Sergey Naumov. Yeah, it's Midnight Commander error. I've just made temporarly perl not

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-02 Thread Denys Vlasenko
= 1 891 read(0, " ", 1) = 1 891 read(0, "J", 1) = 1 891 read(0, "a", 1) = 1 891 read(0, "n", 1) = 1 891 read(0, " ", 1) = 1 891 read(0

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-03 Thread Tomasz Czapiewski
t;n", 1) = 1 891 read(0, " ", 1) = 1 891 read(0, " ", 1) = 1 891 read(0, "1", 1) = 1 891 read(0, " ", 1) = 1 891 read(0, "0", 1)

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-03 Thread Denys Vlasenko
> > 891 read(0, " ", 1) = 1 > > 891 read(0, " ", 1) = 1 > > 891 read(0, " ", 1) = 1 > > 891 read(0, " ", 1) = 1 > > 891 read(0, " ", 1)

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-03 Thread Denys Vlasenko
On Sunday 03 April 2011 23:51, Tomasz Czapiewski wrote: > > So, what is your shell? > > In TV it's BusyBox 1.18.4 ash > On PC it's bash 4.1.5 > > > > > > >>> Can you run this: > >>> > >>> ls -Qlan /tmp | grep '^[^cbt]' | ( while read p x u g s m d y n; do echo > >>> "P$p $u.$g > >>> S$s > >>> d$

Re: 'ls' output with '\"\ \ ' on 1.18.4 - problem with dropbear+mc

2011-04-03 Thread Tomasz Czapiewski
On Mon, 4 Apr 2011, Denys Vlasenko wrote: On Sunday 03 April 2011 23:51, Tomasz Czapiewski wrote: So, what is your shell? In TV it's BusyBox 1.18.4 ash On PC it's bash 4.1.5 Can you run this: ls -Qlan /tmp | grep '^[^cbt]' | ( while read p x u g s m d y n; do echo "P$p $u.$g S$s d$m $d