mirror of
https://github.com/git/git.git
synced 2024-11-19 02:13:55 +01:00
c6929ff239
Recent enhancements to git-completion.bash provide intelligent path completion for git commands. Such completions do not provide the '/' at the end of directories for recent versions of bash; instead, bash itself will add the trailing slash to directories to the result provided by git-completion.bash. However, the completion for tcsh uses the result of the bash completion script directly, so it either needs to add the necessary slash itself, or needs to ask the bash script to keep the trailing slash. Adding the slash itself is difficult because we have to check the each path in the output of the bash script to see if it is meant to be a directory or something else. For example, assuming there is a directory named 'commit' in the current directory, then, when completing git add commit<tab> we would need to add a slash, but for git help commit<tab> we should not. Figuring out such differences would require adding much intelligence to the tcsh completion script. Instead, it is simpler to ask the bash script to keep the trailing slash. This patch does this. Also, tcsh does not handle the colon as a completion separator so we remove it from the list of separators. Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
120 lines
4.2 KiB
Tcsh
120 lines
4.2 KiB
Tcsh
#!tcsh
|
|
#
|
|
# tcsh completion support for core Git.
|
|
#
|
|
# Copyright (C) 2012 Marc Khouzam <marc.khouzam@gmail.com>
|
|
# Distributed under the GNU General Public License, version 2.0.
|
|
#
|
|
# When sourced, this script will generate a new script that uses
|
|
# the git-completion.bash script provided by core Git. This new
|
|
# script can be used by tcsh to perform git completion.
|
|
# The current script also issues the necessary tcsh 'complete'
|
|
# commands.
|
|
#
|
|
# To use this completion script:
|
|
#
|
|
# 1) Copy both this file and the bash completion script to ${HOME}.
|
|
# You _must_ use the name ${HOME}/.git-completion.bash for the
|
|
# bash script.
|
|
# (e.g. ~/.git-completion.tcsh and ~/.git-completion.bash).
|
|
# 2) Add the following line to your .tcshrc/.cshrc:
|
|
# source ~/.git-completion.tcsh
|
|
# 3) For completion similar to bash, it is recommended to also
|
|
# add the following line to your .tcshrc/.cshrc:
|
|
# set autolist=ambiguous
|
|
# It will tell tcsh to list the possible completion choices.
|
|
|
|
set __git_tcsh_completion_original_script = ${HOME}/.git-completion.bash
|
|
set __git_tcsh_completion_script = ${HOME}/.git-completion.tcsh.bash
|
|
|
|
# Check that the user put the script in the right place
|
|
if ( ! -e ${__git_tcsh_completion_original_script} ) then
|
|
echo "git-completion.tcsh: Cannot find: ${__git_tcsh_completion_original_script}. Git completion will not work."
|
|
exit
|
|
endif
|
|
|
|
cat << EOF > ${__git_tcsh_completion_script}
|
|
#!bash
|
|
#
|
|
# This script is GENERATED and will be overwritten automatically.
|
|
# Do not modify it directly. Instead, modify git-completion.tcsh
|
|
# and source it again.
|
|
|
|
source ${__git_tcsh_completion_original_script}
|
|
|
|
# Remove the colon as a completion separator because tcsh cannot handle it
|
|
COMP_WORDBREAKS=\${COMP_WORDBREAKS//:}
|
|
|
|
# For file completion, tcsh needs the '/' to be appended to directories.
|
|
# By default, the bash script does not do that.
|
|
# We can achieve this by using the below compatibility
|
|
# method of the git-completion.bash script.
|
|
__git_index_file_list_filter ()
|
|
{
|
|
__git_index_file_list_filter_compat
|
|
}
|
|
|
|
# Set COMP_WORDS in a way that can be handled by the bash script.
|
|
COMP_WORDS=(\$2)
|
|
|
|
# The cursor is at the end of parameter #1.
|
|
# We must check for a space as the last character which will
|
|
# tell us that the previous word is complete and the cursor
|
|
# is on the next word.
|
|
if [ "\${2: -1}" == " " ]; then
|
|
# The last character is a space, so our location is at the end
|
|
# of the command-line array
|
|
COMP_CWORD=\${#COMP_WORDS[@]}
|
|
else
|
|
# The last character is not a space, so our location is on the
|
|
# last word of the command-line array, so we must decrement the
|
|
# count by 1
|
|
COMP_CWORD=\$((\${#COMP_WORDS[@]}-1))
|
|
fi
|
|
|
|
# Call _git() or _gitk() of the bash script, based on the first argument
|
|
_\${1}
|
|
|
|
IFS=\$'\n'
|
|
if [ \${#COMPREPLY[*]} -gt 0 ]; then
|
|
echo "\${COMPREPLY[*]}" | sort | uniq
|
|
else
|
|
# No completions suggested. In this case, we want tcsh to perform
|
|
# standard file completion. However, there does not seem to be way
|
|
# to tell tcsh to do that. To help the user, we try to simulate
|
|
# file completion directly in this script.
|
|
#
|
|
# Known issues:
|
|
# - Possible completions are shown with their directory prefix.
|
|
# - Completions containing shell variables are not handled.
|
|
# - Completions with ~ as the first character are not handled.
|
|
|
|
# No file completion should be done unless we are completing beyond
|
|
# the git sub-command. An improvement on the bash completion :)
|
|
if [ \${COMP_CWORD} -gt 1 ]; then
|
|
TO_COMPLETE="\${COMP_WORDS[\${COMP_CWORD}]}"
|
|
|
|
# We don't support ~ expansion: too tricky.
|
|
if [ "\${TO_COMPLETE:0:1}" != "~" ]; then
|
|
# Use ls so as to add the '/' at the end of directories.
|
|
RESULT=(\`ls -dp \${TO_COMPLETE}* 2> /dev/null\`)
|
|
echo \${RESULT[*]}
|
|
|
|
# If there is a single completion and it is a directory,
|
|
# we output it a second time to trick tcsh into not adding a space
|
|
# after it.
|
|
if [ \${#RESULT[*]} -eq 1 ] && [ "\${RESULT[0]: -1}" == "/" ]; then
|
|
echo \${RESULT[*]}
|
|
fi
|
|
fi
|
|
fi
|
|
fi
|
|
|
|
EOF
|
|
|
|
# Don't need this variable anymore, so don't pollute the users environment
|
|
unset __git_tcsh_completion_original_script
|
|
|
|
complete git 'p,*,`bash ${__git_tcsh_completion_script} git "${COMMAND_LINE}"`,'
|
|
complete gitk 'p,*,`bash ${__git_tcsh_completion_script} gitk "${COMMAND_LINE}"`,'
|