2 votes

bash : complete : filenames : nom d'option invalide ?

Lorsque j'essaie d'extraire mon fichier .bashrc après l'avoir mis à jour avec de nouvelles variables d'environnement, j'obtiens le message suivant : "bash : complete : filenames : invalid option name". Comme je suis nouveau sur Ubuntu, je ne sais pas vraiment ce que cela signifie et comment m'en débarrasser. Toute aide est sincèrement appréciée. Merci !

Le contenu du fichier .bashrc :

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# added by Anaconda3 4.2.0 installer
export PATH="/home/anaconda3/bin/:$PATH"
export PATH="/home/tls_profiles/rivlib-2_3_0-x86_64-linux-gcc44/bin/:$PATH"

export LD_LIBRARY_PATH="/home/tls_profiles/rivlib-2_3_0-x86_64-linux-gcc44/lib/:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH="/home/tls_profiles/riwavelib_wfm-2_3_0-x86-linux-gcc44/lib/:$LD_LIBRARY_PATH"

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi

0voto

KIRAN B Points 71

Je viens d'essayer

exec bash

Et puis

source .bashrc

il fonctionne

J'ai également ajouté quelques commandes d'exportation dans le fichier .bashrc. Il se peut que ce soit la cause du problème.

0voto

Shakiba Moshiri Points 300

C'est probablement parce que la version de complete du système d'exploitation ne prend pas en charge la commande filenames option. Nous pouvons le tester facilement sur Centos7 depuis complete sur Centos7 ne prend pas en charge nosort option.

TEST

> curl -sLO https://raw.githubusercontent.com/redcursor/btc/master/ldc/_comp_ldc.sh
# it gives us error
> source _comp_ldc.sh 
-bash: complete: nosort: invalid option name

et dans le code source, il y a une configuration pour cela :

complete -o bashdefault -o nosort  -o default -F _comp_ldc ldc

si nous supprimons -o nosort à partir de la source, il fonctionne sans erreur, donc il devrait être :

complete -o bashdefault  -o default -F _comp_ldc ldc

Notez que le même code sur Debian o Ubuntu n'a pas de problème.

# no error
> source <(curl -sL https://raw.githubusercontent.com/redcursor/btc/master/ldc/_comp_ldc.sh)

SistemesEz.com

SystemesEZ est une communauté de sysadmins où vous pouvez résoudre vos problèmes et vos doutes. Vous pouvez consulter les questions des autres sysadmins, poser vos propres questions ou résoudre celles des autres.

Powered by:

X