Keymaps conflicts

[feranpre]

Hi, this is a very VERY interesting plugin. I work with R but I'm thinking about moving to pandas, and at the same time I want to get rid of Rstudio and stay with nvim.

The problem is that the keymaps cannot be disabled, as far as I can see, and you have binded to execute line and it's driving me crazy

Is there a way to remove the binds and use my own? I can bind more keys to execute cells and so on, but I can't remove the binds all together.

Thx for the work

[alhazacod]

Same problem here, i use nvchad and i can't use nvimtree because the enter key is al ready mapped for nvim-jukit and it just try to execute the line.

[thadryanjs]

Same problem here, i use nvchad and i can't use nvimtree because the enter key is al ready mapped for nvim-jukit and it just try to execute the line.

This happened to me with Neotree as well. I worked around it by adding vim.g.jukit_mappings = 0 to my global.lua file in my config (more in the readme). It disables all the mappings though, so you have to create the ones you want afterwards.

I think remapping enter might be a little overzealous but I'm very excited to see where this project goes overall.

[luk400]

You should be able to just remap it using e.g.

nnoremap <YOURKEYBINDING> :call jukit#send#line()<cr>

in your vim config (or the equivalent command in your lua config), does that not work?
Otherwise you can disable ALL default keybindings by setting the g:jukit_mappings variable to 0, as @thadryanjs has mentioned.

[thadryanjs]

You should be able to just remap it using e.g.

nnoremap <YOURKEYBINDING> :call jukit#send#line()<cr>

in your vim config (or the equivalent command in your lua config), does that not work? Otherwise you can disable ALL default keybindings by setting the g:jukit_mappings variable to 0, as @thadryanjs has mentioned.

This works for me. Thank you!