"\rm -f" stops after the 1st glob not found

"\rm -f" stops after the 1st glob not found

[Leonardo Barbosa]

Hello all,

I'm sure that's a simple questions, but the keywords are so common
that i couldn't find the answer by googling them.

My problem is this, when i type:

\rm -f *.aux *.blg *.out *.ps *.log *.toc *.tcp *.idx *.bak *.tps
*.ilg *.ind *.sty *.bst *.bbl

zsh stops in the first glob it doesn't find. How could i fix this?

Thanks in advance

Leo

Re: "\rm -f" stops after the 1st glob not found

[Peter Stephenson]

On Wed, 14 Aug 2013 06:25:27 -0300
Leonardo Barbosa <barbosa.leonardo@gmail.com> wrote:
> I'm sure that's a simple questions, but the keywords are so common
> that i couldn't find the answer by googling them.
> 
> My problem is this, when i type:
> 
> \rm -f *.aux *.blg *.out *.ps *.log *.toc *.tcp *.idx *.bak *.tps
> *.ilg *.ind *.sty *.bst *.bbl
> 
> zsh stops in the first glob it doesn't find. How could i fix this?

You need to change the options (using "setopt" in ~/.zshrc).  There are
various things you can do.

setopt NULL_GLOB

simply removes completely all command line entries where the pattern
didn't expand to anything.

setopt CSH_NULL_GLOB

does the same, but if all patterns failed to expand it's an error (a bit
safer).

setopt NO_NOMATCH

leaves the argument unmodified --- this is what some other shells do, so
it might be your best bet.  That means rm -f will try to remove files
called e.g. "*.bak", but the -f means that's OK.

There's a summary of all (well, some of) this in "From Bash to Z Shell"
chapter 9, page 211 (see www.bash2zsh.com for information about the
book).

pws

Re: "\rm -f" stops after the 1st glob not found

[zzapper]

Leonardo Barbosa <barbosa.leonardo@gmail.com> wrote in 
news:CAMXWGTxJiYpsksFKfEi0=p+nj=O06YQorg3n5MOD8MpNxdQsjQ@mail.gmail.com:

> Hello all,
> 
> I'm sure that's a simple questions, but the keywords are so common
> that i couldn't find the answer by googling them.
> 
> My problem is this, when i type:
> 
> \rm -f *.aux *.blg *.out *.ps *.log *.toc *.tcp *.idx *.bak *.tps
> *.ilg *.ind *.sty *.bst *.bbl
> 
> zsh stops in the first glob it doesn't find. How could i fix this?
> 
I have the following but it doesn't or no longer works??

ls *.{jpg,gif}(.N) # do not break if one or other image type absent


zzapper

Re: "\rm -f" stops after the 1st glob not found

[Bart Schaefer]

On Aug 16,  2:34pm, zzapper wrote:
}
} I have the following but it doesn't or no longer works??
} 
} ls *.{jpg,gif}(.N) # do not break if one or other image type absent

"Doesn't" in what way?

If you do that in a directory that has *neither* .jpg *nor* .gif files,
"ls" will be invoked with no arguments.  Might that be what happened?

Re: "\rm -f" stops after the 1st glob not found

[zzapper]

Bart Schaefer <schaefer@brasslantern.com> wrote in 
news:130816211320.ZM27930@torch.brasslantern.com:

>  ls *.{jpg,gif}(.N)

Bart,
Yeah that's what happened and confused me, of course if I was doing a 
delete that would/could be disastrous

zzapper

Re: "\rm -f" stops after the 1st glob not found

[Aaron Schrab]

At 11:11 +0000 17 Aug 2013, zzapper <david@rayninfo.co.uk> wrote:
>Bart Schaefer <schaefer@brasslantern.com> wrote in
>news:130816211320.ZM27930@torch.brasslantern.com:
>
>>  ls *.{jpg,gif}(.N)
>
>Bart,
>Yeah that's what happened and confused me, of course if I was doing a
>delete that would/could be disastrous

How so?

ls with no (non-option) arguments will list the current directory.  rm 
with no arguments won't delete anything, it will just display an error 
message if the -f option wasn't used.

Re: "\rm -f" stops after the 1st glob not found

[zzapper]

Aaron Schrab <aaron@schrab.com> wrote in news:20130817133600.GG10846
@pug.qqx.org:

> At 11:11 +0000 17 Aug 2013, zzapper <david@rayninfo.co.uk> wrote:
>>Bart Schaefer <schaefer@brasslantern.com> wrote in
>>news:130816211320.ZM27930@torch.brasslantern.com:
>>
>>>  ls *.{jpg,gif}(.N)
>>
>>Bart,
>>Yeah that's what happened and confused me, of course if I was doing a
>>delete that would/could be disastrous
> 
> How so?
> 
> ls with no (non-option) arguments will list the current directory.  rm 
> with no arguments won't delete anything, it will just display an error 
> message if the -f option wasn't used.
> 
You are right you are corect all though ls lists the unmatched files rm 
will not delete them with or without the -f.

Re: "\rm -f" stops after the 1st glob not found

[Bart Schaefer]

On Aug 17, 11:11am, zzapper wrote:
}
} Yeah that's what happened and confused me

If you would prefer to get the "no match" error, write it like this:

% ls *.(jpg|gif)(.)