-
Notifications
You must be signed in to change notification settings - Fork 373
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
Path AutoComplete On First Argument #512
Comments
This seems to be still broken for me on bash. Running |
are you using glow from master? I think the fix is not yet released... |
Yes! I think next week! Please do test the master branch if you can, though 🙏 |
Just built it. Tab works great now on paths. 👍🏻 |
Is your feature request related to a problem? Please describe.
It would be nice to see the autocomplete script use the
ShellCompDirectiveDefault
instead ofShellCompDirectiveNoFileComp
on completion of the first argument. It appears that is the default too.It appears like it could be completed with thisI think it can be handled with this doc. And ideally maybeValidArgsFunction
.ShellCompDirectiveFilterFileExt
for.md
files or.markdown
files.I assume the edit would be somewhere here.
glow/main.go
Lines 40 to 48 in 58ec351
I'm not exactly sure how it works but
oh-my-posh
is able to do some of it below. For instance,oh-my-posh.exe print --config
+<TAB>
will complete a path. The code being executed isoh-my-posh.exe __complete print --config ""
to get the path which will showShellDirectiveDefault
.https://github.com/JanDeDobbeleer/oh-my-posh/blob/a0742d640b21d3ffca5af1a4910fe4e329c558ec/src/cli/print.go#L29-L91
Describe the solution you'd like
I would like paths and the sub commands to be auto completed.
Describe alternatives you've considered
Right now, I have the completion turned off as it isn't useful without the path completion. Typical usage is
glow
+<TAB>
into a file.Additional context
Additional context added above.
The text was updated successfully, but these errors were encountered: