☰

g++ bash：警告：programmable_completion：g++：可能的重试循环

tag-icon • tag-icon bash autocomplete
g++ bash：警告：programmable_completion：g++：可能的重试循环

当我键入g++并完成文件列表的制表符时，我收到此警告

   **g++ bash: warning: programmable_completion: g++: possible retry loop**

我用谷歌搜索了它，到目前为止还没有结果。有人可以帮助解决这个问题吗？

Ubuntu 版本是 14.04。

我的 .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) 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

# 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

if [ -f ~/.local/lib/python2.7/site-packages/powerline/bindings  /bash/powerline.sh ]; then
source ~/.local/lib/python2.7/site-packages/powerline/bindings/bash/powerline.sh
fi


# 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
[ -f ~/.fzf.bash ] && source ~/.fzf.bash

Ubuntu 版本是 14.04

答案1

重击源代码说完成重试次数太多。

Bash 参考手册说：

作为完成处理程序执行的 shell 函数可以通过返回退出状态 124 来指示应该重试完成。如果 shell 函数返回 124，并且更改与尝试完成的命令关联的 compspec（作为第一个提供）函数执行时的参数），可编程完成从头开始，尝试为该命令找到新的 compspec。

所以，你可以重现可能的重试循环和：

function _retr_comp { complete -F _retr_comp foo; return 124; }
complete -F _retr_comp foo

类型fooSpaceTab
您应该看到foo -bash: warning: programmable_completion: foo: possible retry loop

尝试找到所有return 124。

还可以尝试：
g++SpaceTab
complete -p g++ # outputs complete -F <FUNCNAME> g++
type <FUNCNAME>
查看您的g++compspec。

更新:
有一个错误弗兹夫。使固定。

修复合并。谢谢朱内冈。

解决方案:

只是升级你的fzf：cd ~/.fzf && git pull && ./install

重新分配您的资源~/.bashrc：source ~/.bashrc

类型：g++spacetab

相关内容