From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 5A34D6DE0164 for ; Wed, 23 Aug 2017 23:49:13 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.489 X-Spam-Level: X-Spam-Status: No, score=0.489 tagged_above=-999 required=5 tests=[AWL=-0.163, SPF_NEUTRAL=0.652] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bkR8Ns6klz2i for ; Wed, 23 Aug 2017 23:49:11 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by arlo.cworth.org (Postfix) with ESMTP id 936166DE00E6 for ; Wed, 23 Aug 2017 23:49:11 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id D7ABE100063; Thu, 24 Aug 2017 09:49:02 +0300 (EEST) From: Tomi Ollila To: Jani Nikula , Yuri Volchkov , notmuch@notmuchmail.org Subject: Re: [PATCH] build: generate cscope and etags source indexes In-Reply-To: <87d17lqzr5.fsf@nikula.org> References: <1503521740-32330-1-git-send-email-yuri.volchkov@gmail.com> <87d17lqzr5.fsf@nikula.org> User-Agent: Notmuch/0.25+52~ga6cef81 (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Aug 2017 06:49:13 -0000 On Thu, Aug 24 2017, Jani Nikula wrote: > On Wed, 23 Aug 2017, Yuri Volchkov wrote: >> Just a handy tool to generate source code indexes for your favorite >> editor. >> >> To make tags for vim run: >> $ make cscope >> To make tags for emacs: >> $ make TAGS >> To make both: >> $ make alltags > > What's the point in adding these to configure? Or, to be honest, to the > build at all? I agree with Jani about configure and build steps, but could tolerate convenience goals like `cscope` and `tags` (and something `global` !) which would build corresponding files for developers to utilize (provided those are accurate enough, we don't want to lessen general quality (from what it is now) of the system due to too bad quality tags files (content-wise)... Tomi (who should get to work with gnu global again...) > > In theory you'll be able to look at $(SRCS) for indexing... but those > are only the .c/.cc files. Are your tools clever enough to follow > #include directives to index the headers as well? > > I guess I'm also biased because I use gnu global [1] instead. And for > that I have a script of my own that basically boils down to: > > $ git ls-files | gtags -f - (... which means I have to try git ls-files --recurse-submodules | gtags -f -) > > which means all files tracked by git get indexed, and global will decide > whether it can index the file or not. > > BR, > Jani. > > [1] https://www.gnu.org/software/global/ > >> >> Signed-off-by: Yuri Volchkov