You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it's mentioned that there are some confilct with the default. Fine but ctrl +k is a massive conflict and it feels like all of them needs to be remaped somehow.
just to get a list how bad this is do M-x and select "Preferences: Open Keyboard Shortcuts"
then write "ctr k" in the search line at the top of that new window.
this is a huge list of conflicts.
also I don't understant why "alt p" do not show the emacs "ctrl k" beeing at the top it is the one that take priority for real but in this list the sort do not work. I wonder if there is something that the emacs extension does wrong.
There are more errors. vs code does not understand that keyshorts starting with ctrl k can not work and you get tips like from github copilot to do "ctrl k i" or other helpfull things that simply do not work.
Is there anything that can be done about this?
Things that would be nice as a user is if there was some way to list all keybindings that can never actually work as a shorter keybinding will always get the key ? important to know for a user to evaluate if even trying this plugin is worth the effort. if it kill hundreds of other default bindings the cost benefit might be so that its not worth it. but right now I dont even know how much of a mess I created by activating this emacs mode.
Right now I think I have to remove the C-k binding and retain the standart ctrk+k and use selection with C-w as a substitute for C-k
The text was updated successfully, but these errors were encountered:
So it's mentioned that there are some confilct with the default. Fine but ctrl +k is a massive conflict and it feels like all of them needs to be remaped somehow.
just to get a list how bad this is do M-x and select "Preferences: Open Keyboard Shortcuts"
then write "ctr k" in the search line at the top of that new window.
this is a huge list of conflicts.
also I don't understant why "alt p" do not show the emacs "ctrl k" beeing at the top it is the one that take priority for real but in this list the sort do not work. I wonder if there is something that the emacs extension does wrong.
There are more errors. vs code does not understand that keyshorts starting with ctrl k can not work and you get tips like from github copilot to do "ctrl k i" or other helpfull things that simply do not work.
Is there anything that can be done about this?
Things that would be nice as a user is if there was some way to list all keybindings that can never actually work as a shorter keybinding will always get the key ? important to know for a user to evaluate if even trying this plugin is worth the effort. if it kill hundreds of other default bindings the cost benefit might be so that its not worth it. but right now I dont even know how much of a mess I created by activating this emacs mode.
Right now I think I have to remove the C-k binding and retain the standart ctrk+k and use selection with C-w as a substitute for C-k
The text was updated successfully, but these errors were encountered: