PetruD wrote:Wow you're a musician.

I sing in a choir too.

I'm seeking to develop my own app that does music recording, note recognition and other stuff and I wanted to have Audacity as a playground.
Cool
PetruD wrote:for example, I am now studying the code. What should I do if I stumble on a variable or a function that I don't know where is declared? Do I have to take all the #included files and check them one by one, and maybe the files #included in these as well and so on?
I use "Scite" as my text editor, mostly because it has syntax highlighting for LISP which is useful when writing Nyquist plug-ins, but it has several other neat features as well, such as "Search in files". The "Search" feature can not only look for a string in the current document, but can also search all of the files in a specified directory.
The big boys probably use grep, which is immensely powerful but I don't think my brain is big enough to remember all the command line stuff that Linux can do.
About grep:
http://en.wikipedia.org/wiki/Grep
http://unixhelp.ed.ac.uk/CGI/man-cgi?grep
The big daddy text editor is
Emacs . This also has the ability to search in files. I find Emacs too complicated for my needs, but a lot of programmers use it.
If Emacs is the big daddy, then the big mother is
Vim, which is also widely used.
I'm not qualified to say which is better, and this is not the place for a flame war

(This is one of the more civilised discussions comparing Vim and Emacs:
http://stackoverflow.com/questions/1786 ... m-or-emacs )