Skip to content
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

New suggestion system broke path suggestion in bash/zsh #960

Closed
kadel opened this issue Nov 9, 2018 · 7 comments · Fixed by #962
Closed

New suggestion system broke path suggestion in bash/zsh #960

kadel opened this issue Nov 9, 2018 · 7 comments · Fixed by #962
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@kadel
Copy link
Member

kadel commented Nov 9, 2018

[kind/bug]

If I run odo create wildfly --local ./<tab> I don't get path suggestions :(

@kadel kadel added the kind/bug Categorizes issue or PR as related to a bug. label Nov 9, 2018
@mik-dass
Copy link
Contributor

mik-dass commented Nov 9, 2018

@kadel Added a quick PR for this. But the PR currently doesn't work for ~ and ../ but it does work for / and other normal situations

@kadel kadel added priority/Medium Nice to have issue. Getting it done before priority changes would be great. state/Ready labels Nov 12, 2018
@kadel kadel reopened this Nov 12, 2018
@kadel
Copy link
Member Author

kadel commented Nov 12, 2018

Reopening this, as #962 was supposed to fix this only partially. But I couldn't every even that :-(

@anmolbabu anmolbabu self-assigned this Nov 14, 2018
@mik-dass
Copy link
Contributor

mik-dass commented Nov 15, 2018

@kadel @anmolbabu It might be a better idea to fix it upstream in posener/complete. WDYT?

@anmolbabu
Copy link
Contributor

anmolbabu commented Nov 19, 2018

@kadel @anmolbabu It might be a better idea to fix it upstream in posener/complete. WDYT?

@mik-dass Ack Sounds good to me and raised a PR posener/complete#76 on their repo to add fix for ~ but it seems they are differently handling ../(actually /..) for some strange reason otherwise unlike ~ which is a shell symbol, ./ and ../ are very much recognized by golang's file handling apis... I am looking deeper into their code as to why ../ doesn't work and how that can be fixed..

I am just hoping that the first part of fixing ~ goes in quickly 🤞

Cc: @kadel

@anmolbabu
Copy link
Contributor

Ideally, looking at their current code, I doubt posener/complete would work well on windows at the moment 😞

@mik-dass
Copy link
Contributor

@anmolbabu I will try to check on windows if I find a suitable machine

@surajnarwade
Copy link
Contributor

Closing this as we dont have --local flag but we do have --context and suggestions are working for it 🎉

@kadel , reopen if it's not working for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants