From: SourceForge.net <no...@so...> - 2008-05-08 11:11:32
|
Feature Requests item #1959937, was opened at 2008-05-07 21:08 Message generated for change (Settings changed) made by nhorman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=354664&aid=1959937&group_id=4664 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: modify the method of showing the search result Initial Comment: in shell, the representation of the command 'grep' result is acceptible. because it continously reveals the results whenever the string matches, not wait for being finished the search. but in cscope, when I use command 'cs find'. I have to wait for the result util the search is done. it is the only(?) drawback of cscope that I have. so, I suggest a feature to enhance the time of waiting search result. If the number of search result is to be larger than specific number, makes cscope to show the results already found to user, and continue the search task in background job. and a key pressed, then cscope shows the next amounts of search results. I will wait for new version of cscope included that feature. :-) ---------------------------------------------------------------------- >Comment By: Neil Horman (nhorman) Date: 2008-05-08 07:11 Message: Logged In: YES user_id=827328 Originator: NO You're asking for a good deal more than you realize. the find function of cscope under the cover isn't just a child process doing a grep, its cscope itself. Its a single threaded process which is only capable of doing one thing at one time. Its certainly possible to start posting the results of a find operation prior to its completion, but as its written currently, its not possible for cscope to respond to navigation commands while its in progress (i.e. you can slect a displayed item to view, or page the results, or type in another search). To do that we would have to make the application multi-threaded, or multiprocess, and institute enough locking throughout the code base to make it safe. While thats certainly possible, I don't see that its overly helpful. Full text regex searches of the linux kernel take less than a minute on my system, that doesn't seem too bad to me ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=354664&aid=1959937&group_id=4664 |