Arch Linux

Zer0

Member

From: Windsor, ON, Canada

Registered: 2006-08-25

Posts: 299

What is going on with my SET variables? (6000+ lines listed) [SOLVED]

Ok today I noticed something really weird.  I ran SET to see my system variables and a way too many lines came spitting out that are quite unusual.

Here is a snippit

_=set
__git_commandlist=$'add\ngui\nam\nrelink\nannotate\nremote\napply\nimap-send\nrepack\narchive\ninit\nrequest-pull\nbisect\nblame\ninstaweb\nreset\nbranch\nbundle\nlog\nlost-found\nrevert\nls-files\nrm\nls-remote\ncheckout\nls-tree\nsend-email\ncheckout-index\ncherry\ncherry-pick\nmerge\ncitool\nshortlog\nclean\nshow\nclone\nshow-branch\ncommit\nshow-ref\nconfig\ncount-objects\nstash\nstatus\nmergetool\ndescribe\nsubmodule\ndiff\nmv\nname-rev\ntag\nfetch\nfilter-branch\nformat-patch\npull\nfsck\npush\nvar\nverify-pack\ngc\nget-tar-commit-id\nrebase\nwhatchanged\ngrep\nrebase--interactive'
__git_merge_strategylist='recur recursive octopus resolve stupid ours subtree'
__git_whitespacelist='nowarn warn error error-all strip'
bash205='3.2.33(1)-release'
bash205b='3.2.33(1)-release'
bash3='3.2.33(1)-release'
_ImageMagick () 
{ 
    local prev;
    prev=${COMP_WORDS[COMP_CWORD-1]};
    case "$prev" in 
        -channel)
            COMPREPLY=($( compgen -W 'Red Green Blue Opacity \
                Matte Cyan Magenta Yellow Black' -- $cur ));
            return 0
        ;;
        -colormap)
            COMPREPLY=($( compgen -W 'shared private' -- $cur ));
            return 0
        ;;
        -colormap)
            COMPREPLY=($( compgen -W 'shared private' -- $cur ));
            return 0
        ;;
        -colorspace)
            COMPREPLY=($( compgen -W 'GRAY OHTA RGB Transparent \
                XYZ YCbCr YIQ YPbPr YUV CMYK' -- $cur ));
            return 0
        ;;
        -compose)
            COMPREPLY=($( compgen -W 'Over In Out Atop Xor Plus \
                Minus Add Subtract Difference Multiply Bumpmap\
                Copy CopyRed CopyGreen CopyBlue CopyOpacity'                 -- $cur ));
            return 0
        ;;

I'd post the whole thing but it's 6961 lines of crap.. OMG what is going on here.  Anyone else have this happen or is it just something *wonky* with my setup.  BTW my usual variables are ahead of this crap and are working fine (eg. $PATH)

EDIT: I just created a new user and checked that user and root, both with the same result of 6000+ lines of nonsense when running set.

Last edited by Zer0 (2008-02-08 01:59:03)

yabbadabbadont

Member

Registered: 2008-01-19

Posts: 22

Re: What is going on with my SET variables? (6000+ lines listed) [SOLVED]

That is how bash-completion works.  If you don't like it, uninstall the bash-completion package. 

Zer0

Member

From: Windsor, ON, Canada

Registered: 2006-08-25

Posts: 299

Re: What is going on with my SET variables? (6000+ lines listed) [SOLVED]

That is how bash-completion works.  If you don't like it, uninstall the bash-completion package. 

Haha, I figured this out by following how /etc/profile works and what it calls.. I came back to post that I figured it out and you had already answered me.   Thanks

My god, 6000+ lines is excessive considering set usually returns >100 without bash-completion.

None the less I use bash-completion too often to justify it's removal