On Thu, Feb 21, 2008 at 1:19 PM, Albert Santoni <[EMAIL PROTECTED]> wrote:
> directly. The most useful tool I've found for diving into a large
> codebase is grep. For example, if I want to find out where the library
> code is, I'll run something like "grep -i library *.cpp", and take a
> careful look at the output.
>
> (I would say that starting to use grep effectively was a turning point
> in my open source career, hah) :)
>
That's one third of my C++ IDE right now...
grep --color=yes -nH "pattern" *.cpp
and the next third is this,
alias nano='smart_nano'
function smart_nano() {
if [ ! -z "${1}" ] && [ ! -z "`echo ${1}|cut -d: -f2|grep -e '^[0-9]*$'`"
]; then
/usr/bin/nano -w +$(echo ${1}|cut -d: -f2|grep -e '^[0-9]*$') $(echo
${1}|cut -d: -f1)
else
/usr/bin/nano -w $*
fi
}
which takes "/somefile.cpp:333: blah pattern blah" from grep and has nano
open somefile.cpp to that line #
And the last bit is colordiff, colormake, source-highlight, etc... etc...
--
__
--- == __/ t.O ==--
http://stacktrace.org/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
