in reply to Oddity...losing filename from stdin - very wierd

I notice that you're piping the output of ls... are you doing this in the directory where saveme is located? If not, ls will produce no output (but an error message on STDERR). Are you sure that ls is producing what you think it is? Maybe you could try using echo "saveme" instead?
  • Comment on Re: Oddity...losing filename from stdin - very wierd

Replies are listed 'Best First'.
Re: Re: Oddity...losing filename from stdin - very wierd
by snafu (Chaplain) on Apr 09, 2002 at 16:51 UTC
    Good question. In fact, I am in the right directory. I've even checked to make sure that the file is there.

    $ ls -l saveme -rw-r--r-- 1 jconner jconner 0 04-09 12:07 saveme

    I also decided to check a few more ways and found that the first file is getting skipped! Very wierd. I've never seen this before.

    $ ls saveme .vimrc | perl -n -e ' print <>,"\n";' saveme $ ls saveme .vimrc | perl -n -e ' >while (<> ) { > print $_,"\n"; >} >' saveme

    Notice in these examples that I gave ls two files to query and this it should be that ls pipes out the two files to the perl one-liner. Btw, I double-checked that .vimrc exists too. :)

    $ ls -l .vimrc -rw-r--r-- 1 jconner jconner 831 01-18 17:55 .vimrc

    _ _ _ _ _ _ _ _ _ _
    - Jim
    Insert clever comment here...