4 ms·
I compile the source with a good IDE, e.g. Visual Studio, so I can: 1. set breakpoints 2. right-click on an identifier and "Go to Definition" 3. search in
by NonEUCitizen 15y ago
I compile the source with a good IDE, e.g. Visual Studio, so I can:
1. set breakpoints
2. right-click on an identifier and "Go to Definition"
3. search in entire "Project" or "Solution"
I've found helpful on Unix systems:
U1. grep -R ...
U2a. ls -lR > lslr.txt
[if tree is big, this is slow]
U2b. view lslr.txt in an editor
[no longer slow, even if tree is big]
- nmb 15y agoThanks for the tips. My recent projects have been in Python or JS, but I've been looking into things like PyDev or PyCharm so I can do stuff like this. Thus far I haven't been using anything much more heavyweight than a text editor. When I code in Java I'm used to doing this stuff already, but the codebase sizes for those projects tend to be much larger.
- agscala 15y agoRegarding ls -lR, why not save the hassle of saving output to a file, and just pipe it to less instead? `ls -lR | less` Also I'd highly recommend installing ack-grep for searching instead of using grep -R.