> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ross Smith
> Sent: Tuesday, May 10, 2005 4:33 PM
> To: cygwin@cygwin.com
> Subject: Re: "ls" finds file1 but "ls file1" does not
>
> Charles D. Russell w
Charles D. Russell wrote:
Eric Blake wrote:
mv -v "$f" " ` echo $f | tr A-Z a-z ` "
EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces,
but not leading spaces, so it is really moving to " foo"). YOU ARE
ADDING SPACES to the filename. Fix your script so that there are no
sp
Eric Blake wrote:
mv -v "$f" " ` echo $f | tr A-Z a-z ` "
EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces,
but not leading spaces, so it is really moving to " foo"). YOU ARE
ADDING SPACES to the filename. Fix your script so that there are no
spaces between "` and `".
__
Original Message
>From: Charles D. Russell
>Sent: 10 May 2005 16:54
> __
> I am attaching cygcheck in case you can find something obvious.
> However,I am reluctant to upgrade because the use of large static
> fortran arrays with cygwin/g77 seems to be a fragile issue and my
> mv -v "$f" " ` echo $f | tr A-Z a-z ` "
EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces, but not
leading spaces, so it is really moving to " foo"). YOU ARE ADDING SPACES to
the filename. Fix your script so that there are no spaces between "` and `".
Also, as mention
Eric Blake wrote:
What version of coreutils are you using? Attach the output of `cygcheck
-svr' as described in cygwin.com/problems.html, then consider upgrading.
__
I am attaching cygcheck in case you can find something obvious.
However,I am reluctant to upgrade because the use
Original Message
>From: Ross b
>Sent: 10 May 2005 16:17
>
> I'm wondering if something else happened in the renaming
> script. Is it possible there is a space (or some other
> non-printable character) as the first character of the file
> names? The output on a couple of messages leads m
> >> [etc] Did your ash script go wrong and rename all
> those files with
> actual
> >> asterisks on the end ?
>
> > The * in the listing just indicates that the file is
> executable (an ls
> > option that I use by default).
>
>
> Hey, just wondered. It happened to me once
>
>
I'm won
Original Message
>From: Charles D. Russell
>Sent: 10 May 2005 04:58
>> [etc] Did your ash script go wrong and rename all those files with
actual
>> asterisks on the end ?
> The * in the listing just indicates that the file is executable (an ls
> option that I use by default).
Hey,
Eric Blake wrote:
So next, check:
$ type ls
$ alias ls
___
$ type ls
ls is aliased to `ls -aF'
$ alias ls
alias ls='ls -aF'
__
Maybe you have an alias/function for ls that includes the --hide='*.htm'
option, so that ls is doing the filtering (and not bash, like I guesse
Ross Boulet wrote:
ls is acting like the -F option is specified which would
cause the '*' to be displayed at the end of any file name
which is executable (as one prior message shows these files
are).? Under what shell is ls being run and is there an
alias for ls that is causing this option to be in
> $ echo ignoring:$GLOBIGNORE options:$-
> ignoring: options:himBH
>
> $ shopt |grep glob
> dotglob off
> extglob off
> nocaseglob off
> nullgloboff
OK, bash is not filtering the glob. But you are obviously using an alias or
function for ls, since it is acting like
Original Message
>From: Charles D. Russell
> "ls" finds file1 but "ls file1" does not. How can this happen?
>
> The following example occurred just after I had renamed some *.htm files
> to *.html using
> an ash shell script. No such problem occurr
> Response 2 to Eric Blake:
> Thanks. I forgot that unix had separate permissions for directories.
> However, I have
> now given myself all the permissions I know of and I still have the same
> problem.
>
> EXAMPLE:
>
> $ ls ass*
> ls: ass*: No such file or directory <--BUT IT IS THERE
>
>
> > "ls" finds file1 but "ls file1" does not. How can this
> happen?
> >
> > The following example occurred just after I had renamed
> some *.htm files
> > to *.html using
> > an ash shell script. No such problem occurred, however,
&g
Original Message
>From: Charles D. Russell
>Sent: 09 May 2005 20:07
> "ls" finds file1 but "ls file1" does not. How can this happen?
>
> The following example occurred just after I had renamed some *.htm files
> to *.html using
> an ash shell s
> Response to Eric Blake:
> Thanks. I forgot that unix had separate permissions for directories.
> However, I have
> now given myself all the permissions I know of and I still have the same
> problem.
>
> EXAMPLE:
>
> $ ls ass*
> ls: ass*: No such file or directory <--BUT IT IS THERE
>
Response to Eric Blake:
Thanks. I forgot that unix had separate permissions for directories.
However, I have
now given myself all the permissions I know of and I still have the same
problem.
EXAMPLE:
$ ls ass*
ls: ass*: No such file or directory <--BUT IT IS THERE
$ ls -l
total 722
-rwxr
> "ls" finds file1 but "ls file1" does not. How can this happen?
>
[...]
>
> The only difference here from a correctly working directory is that the
> correctly working
> directory does not have execute permissions
You are correct that it has something wit
"ls" finds file1 but "ls file1" does not. How can this happen?
The following example occurred just after I had renamed some *.htm files
to *.html using
an ash shell script. No such problem occurred, however, when I used DOS
"rename" to make
the same change. (Win
20 matches
Mail list logo
