vigemus / tycho.nvim Goto Github PK

Hey!

I'd like to discuss where this should be going eventually, so we can work out how the api should look like and such. I'm not intimately familiar with mappings, but I went through https://neovim.io/doc/user/map.html for some overview. Quite some things.

So, as a first goal I'd define this:

Provide a lua api to the map family where {rhs} is a lua function

If {rhs}, isn't a lua function, it's already pretty usable from vim.api.nvim_command. I assume we can limit ourselves to <Cmd> mappings, because the lua function can easily check for the mode and do nothing if inappropriate. Or is that assuming too much? Am I missing something?

So in it's simplest incarnation, the following should work imho (name of course non-final):

vim.lua_api.lua_map("<F2>", my_lua_function)

Thoughts:

• See which of "buffer", "nowait", "silent", "script", "expr" and
  "unique" we need to incorporate, and in which way. My first intuition is an optional array of strings.
  • Maybe we should forego "" and make a different function vim.lua_api.buf_lua_map where you can choose the buffer (default current; maybe that's not great because "" works on the curbuf, so we'd need to change that temporarily).
  • "script" and "expr" don't make sense in our scope, right?
• Do we need a variant of "SID" to prevent name conflicts? Not sure what that does when used from nvim_command. Same about "Plug".

You said something about reuseability, which is why you set up things the way you did. Can you elaborate on that? I did not really understand what you were after.

My pretty limited imagination says that the next step would be to provide something similiar for user commands, but let's take one step after the other :)

I'm archiving this repository to keep the reference and discussion. I couldn't really devote the right time to it and neovim took a really nice path forward with lua support without needing the investments I was willing to make.