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
I find myself using cscope and gtags layers depending on the demands of particular projects I am working on. However, the two layers share some of the same keybindings. I am wondering if the cscope layer could be remapped to some other keybinding so the SPC m g is left for gtags. That way, one can use both layers with no keybindings tramping on each other. Currently had to remap cscope to SPC o c to work with both cscope and gtags layers
Reproduction guide
Start Emacs
Add gtags layer and add cscope layers
open a C/C++ file
Try to run SPC m g
Observed behaviour: cscope ang gtags keybindings are mixed.
Expected behaviour:
To use gtags and cscope without the keybindings getting into each other's way.
I am thinking binding cscope to SPC m c should fix this. It would not interfere with other bindings since the bindings are done per major mode. In this case for C/C++ mode only. I will go ahead and create a pull request.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!
Description
I find myself using
cscope
andgtags
layers depending on the demands of particular projects I am working on. However, the two layers share some of the same keybindings. I am wondering if thecscope
layer could be remapped to some other keybinding so theSPC m g
is left forgtags
. That way, one can use both layers with no keybindings tramping on each other. Currently had to remapcscope
toSPC o c
to work with bothcscope
andgtags
layersReproduction guide
gtags
layer and addcscope
layersSPC m g
Observed behaviour:
cscope
anggtags
keybindings are mixed.Expected behaviour:
To use
gtags
andcscope
without the keybindings getting into each other's way.System Info
The text was updated successfully, but these errors were encountered: