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

Error: Expected lua string #238

Closed
lucax88x opened this issue Jan 13, 2022 · 3 comments
Closed

Error: Expected lua string #238

lucax88x opened this issue Jan 13, 2022 · 3 comments

Comments

@lucax88x
Copy link

Happens even with latest version.

Not sure about that, but if keymap.rhs is nil, this will give the following error.

I'll try to propose a simple PR for this one.

Error detected while processing VimEnter Autocommands for "*":                                                                          
E5108: Error executing lua .../pack/packer/start/which-key.nvim/lua/which-key/keys.lua:532: Expected lua string                         
stack traceback:                                                                                                                        
        [C]: in function 't'                                                                                                            
        .../pack/packer/start/which-key.nvim/lua/which-key/keys.lua:532: in function 'update_keymaps'                                   
        .../pack/packer/start/which-key.nvim/lua/which-key/keys.lua:420: in function 'update'                                           
        .../pack/packer/start/which-key.nvim/lua/which-key/init.lua:98: in function 'load'                                              
        [string ":lua"]:1: in main chunk    

I'm gonna provide a quick

@wookayin
Copy link

wookayin commented Feb 3, 2022

Why did you close this? is this not happening to you any more?

@lucax88x
Copy link
Author

lucax88x commented Feb 3, 2022

Because there was a duplicate pr (#223) that got merged

@wookayin
Copy link

wookayin commented Feb 3, 2022

Good to know, thanks! (I was earlier getting a similar issue) So this seems to have been fixed.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants