Patrick, The structure within the paren's looks like what would be used for a 'grep -Ev' to find everything BUT that mix of patterns. Can you explain what it is you are attempting to do, and provide some context, please. Thank you.-Joe On Friday, June 4, 2021, 2:14:53 PM EDT, Patrick Dupre <pdupre(a)gmx.com&gt; wrote: Hello, Sorry, I am a bit of list This command line works in a shell, but not in a bash I may miss some quotes ! Thanks for your help. /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*) =========================================================================== Patrick DUPRÉ                                | | email: pdupre(a)gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988                    | | Room# D114A =========================================================================== _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

On 6/4/21 12:21 PM, Joe Wulf via users wrote: Checking with the man page, I find that -v stands for verbose, telling you what's happening.

On 6/4/21 1:11 PM, Samuel Sieb wrote: The man page for rm, of course. Why would I suggest that you look at any other command's man page to find out what an option for rm means?

Could you not simply \ escape the ! ? On Fri, Jun 4, 2021, 3:05 PM Samuel Sieb <samuel(a)sieb.net&gt; wrote:

Joe Zeff wrote: I don't think that's entirely accurate. :) You quoted the portion which had `grep -Ev` in your reply: On 6/4/21 12:21 PM, Joe Wulf via users wrote: Checking with the man page, I find that -v stands for verbose, telling you what's happening. So Joe Wulf is explicitly talking about the -v option to grep and your reply suggests that -v means verbose -- without any mention that you are referring to rm. Within your own context that might have made perfect sense, but I hope you can see how it's certainly not as clear to others reading the various sub-threads in this topic. :) Anyway, all of that was a distraction from the issue at hand, which was the difference between interactive use with extglob and non-interactive use without it. -- Todd

On 6/4/21 1:17 PM, wwp wrote: Yes, that's true for grep, but we're discussing rm here.

Fantastic, Thanks. How can I leave this mode extglob ? > > Patrick Dupre wrote: > > Sorry, I am a bit of list > > This command line works in a shell, but not in a bash > > I may miss some quotes ! > > Thanks for your help. > > > > /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*) > > The !(ZMAT*|...) syntax requires the bash extglob option. > This must be explicitly enabled in a non-interactive session > (like a script). For example: > > #!/bin/bash > > shopt -s extglob > /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*) > > -- > Todd > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure >

Samuel Sieb wrote: True. Though depending on the size of the script and what else it does, there are certainly times when you don't want this enabled for the entire script. There are a few ways to handle that. You can simply unset it via `shopt -u extglob` after the rm. Another common method to set an option and only have it effect a small portion of the code is to use a subshell. Like: #!/bin/bash # some code ( shopt -s extglob rm -v !(...) ) # some other code The subshell ensures that the shopt is only in effect for the commands run within the opening and closing parentheses. There are, as alway, pros and cons to each method. With the subshell method, a potential con is that the environment might differ from the rest of the script. If you depend on variables which are set earlier in the script you just need to be sure they're available to you in the subshell. Similarly, if you set a variable in the subshell it won't be available outside of the subshell. -- Todd