Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 310569
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T07:50:44+00:00 2026-05-12T07:50:44+00:00

I was looking through the /etc/bash_completion script found in some Debian packages. I was

  • 0

I was looking through the /etc/bash_completion script found in some Debian packages. I was interested in using the code that looks through a specific directory (/etc/bash_completion.d/ by default) and sources every file in that directory.

Unfortunately, trying to run the script causes errors under the Mac OS X version of bash. The lines in question are:

for i in $BASH_COMPLETION_DIR/*; do
    [[ ${i##*/} != @(*~|*.bak|*.swp|\#*\#|*.dpkg*|.rpm*) ]] &&
    [ \( -f $i -o -h $i \) -a -r $i ] && . $i
done

Specifically, my version of bash (3.2.17) chokes on the @() construction. I get that the point of that first test is to make sure we don’t source any editor swap files or backups, etc. I’d like to understand exactly what that @() syntax does, and, if possible how to get something similar (and similarly elegant) running on my ancient copy of bash. Can anyone offer insight?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T07:50:44+00:00Added an answer on May 12, 2026 at 7:50 am

    It’s just an extension to the shell comparison which is equivalent to the grep “or” operator (|).

    Depending on your bash version, it may not be available or you may have to set extglob with the shopt built-in. See the following session transcript:

        pax@daemonspawn> $ bash --version
            GNU bash, version 3.2.48(21)-release (i686-pc-cygwin)
            Copyright (C) 2007 Free Software Foundation, Inc.
        pax@daemonspawn> echo @(*~|*.pl)
            bash: syntax error near unexpected token '('
        pax@daemonspawn> shopt extglob
            extglob off
        pax@daemonspawn> shopt -s extglob
        pax@daemonspawn> echo @(*~|*.pl)
            qq.pl qq.sh~ xx.pl
        pax@daemonspawn> 
    

    That allows the following to work:

        ?(pattern-list)
            Matches zero or one occurrence of the given patterns
        *(pattern-list)
            Matches zero or more occurrences of the given patterns
        +(pattern-list)
            Matches one or more occurrences of the given patterns
        @(pattern-list)
            Matches one of the given patterns
        !(pattern-list)
            Matches anything except one of the given patterns
    

    If you can’t get it working with shopt, you can generate a similar effect with older methods such as:

        #!/bin/bash
        for i in $BASH_COMPLETION_DIR/*; do
            # Ignore VIM, backup, swp, files with all #'s and install package files.
            # I think that's the right meaning for the '\#*\#' string.
            # I don't know for sure what it's meant to match otherwise.
    
            echo $i | egrep '~$|\.bak$|\.swp$|^#*#$|\.dpkg|\.rpm' >/dev/null 2>&1
            if [[ $? == 0 ]] ; then
                . $i
            fi
        done
    

    Alternatively, if there’s multiple complex determinations that will decide whether you want it sourced, you can use a doit variable that’s initially set to true, and set it to false if any of those conditions trigger. For example, the following script qq.sh:

        #!/bin/bash
        for i in * ; do
            doit=1
    
            # Ignore VIM backups.
            echo $i | egrep '~$' >/dev/null 2>&1
            if [[ $? -eq 0 ]] ; then
                doit=0
            fi
    
            # Ignore Perl files.
            echo $i | egrep '\.pl$' >/dev/null 2>&1
            if [[ $? -eq 0 ]] ; then
                doit=0
            fi
    
            if [[ ${doit} -eq 1 ]] ; then
                echo Processing $i
            else
                echo Ignoring $i
            fi
        done
    

    did this in my home directory:

        Processing Makefile
        Processing binmath.c
        : : : : :
        Processing qq.in
        Ignoring qq.pl    --+
        Processing qq.sh    |
        Ignoring qq.sh~   --+--- see?
        Processing qqin     |
        : : : : :           |
        Ignoring xx.pl    --+
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 165k
  • Answers 165k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer There are a couple of variants of a rename command,… May 12, 2026 at 12:33 pm
  • Editorial Team
    Editorial Team added an answer There is currently no way to build CLS-compliant assemblies from… May 12, 2026 at 12:33 pm
  • Editorial Team
    Editorial Team added an answer You might want to look at Google Protocol Buffers or… May 12, 2026 at 12:33 pm

Related Questions

I was just looking through the man page for printf and something occurred to
I was looking at the String and Int32 types through the reflector but couldn't
i have written a c program to which i pass in a script like
I was looking for a solution for client side printing of reports and pre
I'm a Java rookie and I was wondering, if I have the following typical

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.