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

Completion of chroma/-* #157

Closed
vaeth opened this issue Sep 2, 2019 · 4 comments
Closed

Completion of chroma/-* #157

vaeth opened this issue Sep 2, 2019 · 4 comments
Labels

Comments

@vaeth
Copy link

@vaeth vaeth commented Sep 2, 2019

On my system, if I type chroma/[TAB], I get completion offered for chroma/-alias.ch chroma/-autoload.ch etc.

I conjecture that somehow the path to chroma is leaked to the completion system and simultaneously the .ch is for some reason recognized as an executable extension, though especially for the latter I found no obvious reason.

@psprint

This comment has been minimized.

Copy link
Contributor

@psprint psprint commented Sep 16, 2019

How does it manifest that the files are seen as executable ones? Screenshot maybe?

@vaeth

This comment has been minimized.

Copy link
Author

@vaeth vaeth commented Sep 17, 2019

In my completion configuration, I expected that chrom[TAB][TAB] essentially expands only to chromium, but I get:

% chrom[TAB][TAB]
(external command)
(shell function)
(alias)
chroma/-alias.ch      chroma/-docker.ch      chroma/-git.ch     chroma/-lab.ch    chroma/-node.ch        chroma/-printf.ch  chroma/-source.ch      chroma/-vim.ch      chroma/main-chroma.ch
chroma/-autoload.ch   chroma/-example.ch     chroma/-grep.ch    chroma/-make.ch   chroma/-ogit.ch        chroma/-ruby.ch    chroma/-ssh.ch         chroma/-whatis.ch   chromedriver                        
chroma/-autorandr.ch  chroma/-fast-theme.ch  chroma/-hub.ch     chroma/-nice.ch   chroma/-perl.ch        chroma/-scp.ch     chroma/-subcommand.ch  chroma/-which.ch    chromium                            
chroma/-awk.ch        chroma/-fpath_peq.ch   chroma/-ionice.ch  chroma/-nmcli.ch  chroma/-precommand.ch  chroma/-sh.ch      chroma/-subversion.ch  chroma/-zplugin.ch  chromium-browser
@psprint

This comment has been minimized.

Copy link
Contributor

@psprint psprint commented Oct 11, 2019

Ah, yes, that's because the chroma functions are auto-loaded with the directory in their name. That's a good catch, I think that I'll be willing to rename the directory to _chroma to prevent this from happening. Maybe anyone interested in accomplishing a Hacktoberfest 2019 step with such pull-request?

@psprint

This comment has been minimized.

Copy link
Contributor

@psprint psprint commented Oct 21, 2019

I thought that this shouldn't wait and renamed the functions – from chroma/* to :chroma/*, according to an emerging (currently only my own) methodology of preceding the hooks' names with a colon.

@psprint psprint closed this Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.