I am using emacs & helm & helm-gtags on cygwin in combination with global compiled from source for cygwin. I observed the quite annoying behaviour that isearch-forward-regexp significantly lags if a search fails and helm-gtags is activated.
This seems to be somehow caused by helm-gtags-update-tags - isearch-forward-regexp only lags upon failed searches when I saved the current buffer before (i.e. helm-gtags-update-tags has already been called when helm-gtags-auto-update is set) or after explicitly calling helm-gtags-auto-update (if helm-gtags-auto-update is set to nil). However, I have no clue how helm-gtags-auto-update and isearch-forward-regexp interact.
Could anybody out there confirm this behaviour or provide some insights?
I am using emacs & helm & helm-gtags on cygwin in combination with global compiled from source for cygwin. I observed the quite annoying behaviour that
isearch-forward-regexp
significantly lags if a search fails and helm-gtags is activated.This seems to be somehow caused by
helm-gtags-update-tags
-isearch-forward-regexp
only lags upon failed searches when I saved the current buffer before (i.e.helm-gtags-update-tags
has already been called whenhelm-gtags-auto-update
is set) or after explicitly callinghelm-gtags-auto-update
(ifhelm-gtags-auto-update
is set to nil). However, I have no clue howhelm-gtags-auto-update
andisearch-forward-regexp
interact.Could anybody out there confirm this behaviour or provide some insights?
Aside from that helm-gtags really works great!