<story><title>Efficiently Browsing Text or Code (esp. with Emacs)</title><url>http://www.kirubakaran.com/articles/efficiently-browsing-text-or-code.html</url></story><parent_chain></parent_chain><comment><author>tptacek</author><text>Highly, highly recommend hilock-mode for browsing code; hilock does ad-hoc syntax highlighting, so, as you read code and notice patterns, you write regexes for them and let Emacs spot them for you.&lt;p&gt;This turned out to be so useful for code reviews (we do a lot of those) that I &quot;ported&quot; it to a web app that lets us set hilocks that follow us from buffer to buffer (along with xrefs, class/method/fn definition sites, bookmarks, and a lot of other junk).</text></comment>
<story><title>Efficiently Browsing Text or Code (esp. with Emacs)</title><url>http://www.kirubakaran.com/articles/efficiently-browsing-text-or-code.html</url></story><parent_chain></parent_chain><comment><author>wladimir</author><text>It&apos;s 2012 and we&apos;re still navigating source code, which is effectively a nested graph structure, using grep and simple keyword queries.&lt;p&gt;No (reverse) call trees, no high-level views, no help on how data propagates through the program. We could do so much better, especially in static languages. Sometimes it seems like reverse engineering tools that work without source code (such as IDA) do a better job of cross-referencing than tools that have the actual source code.&lt;p&gt;Is there any good/usable point and click code browser / code comprehension tool these days? Or is the state of the art of 1998 still that of today?</text></comment>