SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Features and/or Improvements => Topic started by: rowbearto on October 30, 2013, 09:27:55 PM

Title: Speed up searches and cross-reference
Post by: rowbearto on October 30, 2013, 09:27:55 PM: Speed up searches and cross-reference finding by using multi-threading to take advantage of multiple CPUs searching subsets of the files in parallel.

Much like 'make' has option -j for # of parallel jobs, give the user the option to specify how many parallel jobs, and/or have SE detect # of CPUs. Using option like -j might be nice if the user doesn't want all CPUs tied up, so that SE can remain responsive.
Title: Re: Speed up searches and cross-reference
Post by: davew on July 27, 2015, 04:27:59 PM: Faster searches
Title: Re: Speed up searches and cross-reference
Post by: Clark on July 27, 2015, 04:53:22 PM: Quote from: davew on July 27, 2015, 04:27:59 PM
Faster searches
Do you mean multi-file searches or something else?
Title: Re: Speed up searches and cross-reference
Post by: davew on July 27, 2015, 07:39:42 PM: Quote from: Clark on July 27, 2015, 04:53:22 PM
Quote from: davew on July 27, 2015, 04:27:59 PM
Faster searches
Do you mean multi-file searches or something else?
Yes, multi-file searches.
Title: Re: Speed up searches and cross-reference
Post by: b on August 30, 2016, 07:27:28 PM: git grep is very fast and is nice in that it can look for just the files belonging to the repo, ignoring everything not. I use this heavily as it can be faster than doing multi-file searches within SE.

Would you add this as one of the search types (e.g., maybe <git> along with <workspace> & <project> if git is the it is a the selected Version Control.

Having it as a menu item under Tools | Version Control ( | Search repository ) would be equally useful as well.

This allows for having files in my project/workspace that aren't necessarily in my repo and selectively looking in just those in the current repo and not my entire build space.