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
Hi, thanks for the awesome work that makes me more productive everyday.
I'm asking if we can make the integration with xref and capf user configurable options? Since I'm using many similar packages (gtags, cscope, eglot, etc), I don't want each of them adding itself into the xref/capf backend list that might conflict with each other. Currently I'm using a hack to just remove those backend when ggtags-mode is enable. E.g.
And it works for me without noticeable issue. Base on this, my naive assumption will be that we just need to provide some defcustoms and check the value in https://github.com/leoliu/ggtags/blob/master/ggtags.el#L2209 for whether we are going to enable xref/cape integration or not? I'm not an elisp expert so I'm might be wrong. What do you think?
The text was updated successfully, but these errors were encountered:
BooAA
changed the title
Make integration with xref and capf a defcustom
Make integration with xref and capf user configurable
Mar 26, 2023
Hi, thanks for the awesome work that makes me more productive everyday.
I'm asking if we can make the integration with xref and capf user configurable options? Since I'm using many similar packages (gtags, cscope, eglot, etc), I don't want each of them adding itself into the xref/capf backend list that might conflict with each other. Currently I'm using a hack to just remove those backend when ggtags-mode is enable. E.g.
And it works for me without noticeable issue. Base on this, my naive assumption will be that we just need to provide some
defcustoms
and check the value in https://github.com/leoliu/ggtags/blob/master/ggtags.el#L2209 for whether we are going to enable xref/cape integration or not? I'm not an elisp expert so I'm might be wrong. What do you think?The text was updated successfully, but these errors were encountered: