* On 2013 10 Dec 00:04 -0600, Thomas Beierlein wrote: > You did a grep for some identifier and afterward want to look at all > the places it is used. So you have to start less or vi or whatever with > all the filenames you found - that maybe a lot of typing. > > With cscope you get the search result as a list you can choose from. > No typing of each found filename.
I suspect that were I more clever git grep would get me the same place. I did play with cscope a bit last night and didn't find it an advantage over git grep. I then tried Kscope and was rather disappointed. I do use git grep with Perl Compatible RE enabled, since Debian now enables it, which makes it easier for me to narrow searches along with colorized output and file names and line numbers enabled. I do like that git grep will not only grep in added/committed files but also will output matches in uncommitted changes in tracked files. I found on Stack Exchange another trick that git grep can search in earlier commits without needing to check out the desired commit and so on. > But to be honest I do use grep, sed and other tools as well. It is > good to have a well filled and sorted toolbag. I haven't spent the time to learn how t use ctags effectively either. Unfortunately, my favorite editor Geany doesn't use native ctags but has its own implementation. While I use Vim for email editing, I like the GUI for C work or Midnight Commander's editor for editing in a shell. So many tools, so little time! 73, de Nate >> -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us _______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
