Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH v5] git-completion.bash: add support for path completion

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:55:44

Manlio Perillo [off-list ref] writes:
quoted
+	# Skip "git" (first argument)
+	for ((i=1; i < ${#words[@]}; i++)); do
+		word="${words[i]}"
+
+		case "$word" in
+			--)
Sorry, I have incorrectly (again) indented the case labels.
I have now configured my editor to correctly indent this.
Yeah, thanks for spotting.

I wouldn't worry *too* much about the style in this script at this
point, though.  It uses a style on its own that is totally different
from the rest of the system (e.g. "[" instead of "test", semicolon
in "if ...; then", etc.) and it probably is better to emulate the
surrounding code, and leave the style "fixes" to a separate topic,
if we want to (as a contrib/ material that is not POSIX but bash
specific, I do not know if that is even worth it).
quoted
+				# Good; we can assume that the following are only non
+				# option arguments.
+				((c = 0))
+				;;
Here I was thinking to do something like this (not tested):

		-*)
			if [ -n ${2-} ]; then
				# Assume specified git command only
                                # accepts simple options
				# (without arguments)
				((c = 0))

Since git mv only accepts simple options, this will make the use of '--'
not required.
Unless you have a file whose name begins with a dash, perhaps?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help