Simple Command Lookup

What's the correct format for using g_signal_connect (or is it gdk_signal_connect?) You can at least hope that one of the best and clearest examples will exist in a file somewhere on your hard drive. This is the kind of thing you use grep for, if you don't mind scrolling through the output with less, etc. But TkCodex can be launched with search criteria and a path on the command-line, will deploy at least as fast, and provides a much nicer and more dynamic interface.

In /root/SCRIPTz/c/gtk I have a bunch of source files by me, or garnered from somewhere, plus softlinks to a directory of the source code from Foundations of Gtk+2.0, itself divided into chapter-by-chapter subdirectories, and to /usr/share/gtk-2.0/demo. So I could start TkCodex on the command-line with:

TkCodex /root/SCRIPTz/c/gtk c "g\w*_signal_connect"

Or, since I have /root/SCRIPTz/c/gtk bookmarked, just start from a window manager menu and enter the regular expression in the command window manually.

Be aware that TkCodex does work recursively and follow symbolic links. However, in the command window file list, no path is shown unless there are duplicate filenames. Let's look at the first four files in the file list, which has been sorted according to the number of matches in each file. To do this, just open a window and hit the 1st 4 button:

So it was g_signal_connect after all, and here's four different files with it highlighted and indexed, meaning I could see any of the examples in any file with two mouse clicks! Note that searches done this way (from the command window) are always regular expressions, so they will appear white in the index rather than the normal gray.