Re: X=`cat ~/y` completion

[Bart Schaefer <schaefer@brasslantern.com>]

[This is more properly a -workers discussion but I'll continue on -users
because we started here.]

On Jun 3,  5:31am, Daniel Shahaf wrote:
} Subject: X=`cat ~/y` completion
}
} Consider the following two cases:
} 
} % X=`cat $HOME/t<TAB>
} % X=`cat ~/t<TAB>
} 
} In 'zsh -f' + compinit, the former works but the latter doesn't.
} I expect the latter to behave as the former does.
} 
} ---
} 
} The last related discussion seems to be 35515/35539.

I don't think those are related, completing after ~/ works elsewhere.
The real difficulty seems to follow from testing $compstate[quote] on
line 276:

}    276	elif [[ "$pre[1]" = \~ && -z "$compstate[quote]" ]]; then
}    277	
}    278	  # It begins with `~', so [...]

The word on line does begin with tilde, but that's ignored because it is
inside the backticks.

The test could be either != [\'\"] or = (|\`) but I went with the latter
because the former confuses vim syntax highlighting.


diff --git a/Completion/Unix/Type/_path_files b/Completion/Unix/Type/_path_files
index c64ebf5..14c4cc7 100644
--- a/Completion/Unix/Type/_path_files
+++ b/Completion/Unix/Type/_path_files
@@ -273,7 +273,7 @@ if [[ "$pre" = [^][*?#^\|\<\>\\]#(\`[^\`]#\`|\$)*/* && "$compstate[quote]" != \'
   orig="${orig[1,(in:i:)/][1,-2]}"
   donepath=
   prepaths=( '' )
-elif [[ "$pre[1]" = \~ && -z "$compstate[quote]" ]]; then
+elif [[ "$pre[1]" = \~ && "$compstate[quote]" = (|\`) ]]; then
 
   # It begins with `~', so remember anything before the first slash to be able
   # to report it to the completion code. Also get an expanded version of it