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

Issue with error message with no matching callback #16

Closed
AckslD opened this issue Jun 17, 2021 · 1 comment · Fixed by #17
Closed

Issue with error message with no matching callback #16

AckslD opened this issue Jun 17, 2021 · 1 comment · Fixed by #17
Assignees
Labels
bug Something isn't working

Comments

@AckslD
Copy link

AckslD commented Jun 17, 2021

Describe the bug
Before I had properly configured my company's gitlab ie:

callbacks = {
  ["git.seriouscompany.com"] = require"gitlinker.hosts".get_gitlab_type_url
}

when gitlinker hit this line to print the error message it failed and said that target_host wasn't a string but a number.

E5108: Error executing lua ...pack/packer/start/gitlinker.nvim/lua/gitlinker/hosts.lua:116: bad argument #2 to 'error' (number expected, got string)

To Reproduce
See above.

Expected behavior
Getting the error "No host callback defined for host 'git.seriouscompany.com'"

System (please complete the following information):

  • OS: archlinux
  • neovim --version v0.5.0-dev+1419-gf76f72a27
  • git --version 2.32.0
@AckslD AckslD added the bug Something isn't working label Jun 17, 2021
ruifm added a commit that referenced this issue Jun 17, 2021
@ruifm ruifm closed this as completed in #17 Jun 17, 2021
@ruifm
Copy link
Owner

ruifm commented Jun 17, 2021

Thanks for the report! I think I fixed with #17, feel free to reopen, if it's still not fixed for you.

stevanmilic pushed a commit to stevanmilic/gitlinker.nvim that referenced this issue Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants