-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make file completion broken in 2.7 #4967
Comments
I'd imagine this is due to #112 - 68527ff only changes "--description".
That's because, before 112, when I'm not too familiar with make - why is a file valid here? In general, when does make accept files? Would it be sufficient to allow files after a "="? |
Make itself never accepts files as arguments, it accepts the name of the target which may be a file, but is often a file that doesn't yet exist (so file-based completions are useless). Any Depending on how smart our makefile target listing is, it may be best to just drop |
Our make completions call
That actually seems to be handled! With a |
Oh, I didn't realize we were using |
File completion for Makefile arguments became broken in 2.7 (tested on both OSX and Ubuntu)
To reproduce, create a dummy Makefile:
in 2.6, typing
make test F=<TAB>
brings up autocomplete. In 2.7, it doesn't.Removing
complete -x -c make -a "(__fish_complete_make_targets (commandline -c))" --description "Target"
from the make completion "solves" this problem, but I don't think that's the correct fix.I asked in the gitter channel, and the suggesting was that #68527f broke this and I should open this issue.
The text was updated successfully, but these errors were encountered: