From b0dee52a9b248a7dd12cdad62908ce8c379a38a9 Mon Sep 17 00:00:00 2001 From: Marco Hinz Date: Tue, 8 Mar 2016 13:52:55 +0100 Subject: [PATCH] Cscope: only supports C, C++, Java --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 39cee1e..84b28d8 100644 --- a/README.md +++ b/README.md @@ -1640,9 +1640,9 @@ which is fine for scripts, but when doing it on the fly, I find it easier to use #### Cscope -[Cscope](http://cscope.sourceforge.net/) is a better -[ctags](http://ctags.sourceforge.net/) and supports [quite some -languages](http://ctags.sourceforge.net/languages.html). +[Cscope](http://cscope.sourceforge.net/) does more things than +[ctags](http://ctags.sourceforge.net/), but only supports C (and C++ and Java to +some extent). Whereas a tags file only knows where a symbol was defined, a cscope database knows much more about your data: @@ -1670,10 +1670,10 @@ This will create 3 files: `cscope{,.in,.po}.out` in the current working directory. Think of them as your database. Unfortunately `cscope` only analyzes `*.[c|h|y|l]` files by default. If you want -to use cscope for a Ruby project instead, do this: +to use cscope for a Java project instead, do this: ```sh -$ find . -name "*.rb" > cscope.files +$ find . -name "*.java" > cscope.files $ cscope -bq ```