Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: rmstar option nit in 2.6-beta11
- X-seq: zsh-workers 593
- From: schaefer@xxxxxxxxxxxxxx (Barton E. Schaefer)
- To: Richard Coleman <coleman@xxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: rmstar option nit in 2.6-beta11
- Date: Fri, 10 Nov 1995 16:12:32 -0800
- In-reply-to: Richard Coleman <coleman@xxxxxxxxxxxxxxx> "Re: rmstar option nit in 2.6-beta11" (Nov 10, 6:45pm)
- References: <199511102345.SAA00693@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxxxxxxxxx
On Nov 10, 6:45pm, Richard Coleman wrote:
} Subject: Re: rmstar option nit in 2.6-beta11
}
} Interesting. Looking at the code, I see that if you do
}
} $ rm *
}
} and then type `n' when it queries you, it will abort the command with
} a return value of 1. If you type
}
} $ rm file1 *
}
} and then type `n' when it queries you, it will delete `*' from the argument
} list and continue. Therefore file1 gets deleted and it returns with a
} return value of 0.
}
} Not very consistent.
Look at the case of
$ rm foo/file1 bar/*
before you pass judgement.
--
Bart Schaefer Vice President, Technology, Z-Code Software
schaefer@xxxxxxxxxx Division of NCD Software Corporation
http://www.well.com/www/barts
Messages sorted by:
Reverse Date,
Date,
Thread,
Author