From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Marcus Harnisch Newsgroups: gmane.emacs.help Subject: Re: Navigating an enormous code base Date: Thu, 28 Apr 2022 08:42:55 +0200 Message-ID: References: <877d7aq5qy.fsf@cock.li> <87bkwmo56v.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33356"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Apr 28 09:16:26 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1njyO1-0008WM-TY for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 28 Apr 2022 09:16:25 +0200 Original-Received: from localhost ([::1]:49476 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1njyO0-000258-Cu for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 28 Apr 2022 03:16:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49620) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1njxrk-0006xp-Ce for help-gnu-emacs@gnu.org; Thu, 28 Apr 2022 02:43:06 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:47210) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1njxri-0003ho-TU for help-gnu-emacs@gnu.org; Thu, 28 Apr 2022 02:43:04 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1njxrh-0007vT-3P for help-gnu-emacs@gnu.org; Thu, 28 Apr 2022 08:43:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ Content-Language: en-GB In-Reply-To: Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 6 X-Spam_score: 0.6 X-Spam_bar: / X-Spam_report: (0.6 / 5.0 requ) BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:137056 Archived-At: On 28/04/2022 00.59, John Yates wrote: > Start with feeding a completion interface: > > * Do you index on demand? If no, then when? And how do you > keep the index upto date? As far as my work pattern with Global/ggtags is concerned, I create a full index rarely. Usually only when the repository can be expected to have changed significantly (pull, merge with upstream, etc). Global can do single-file updates, which I think ggtags executes in ‘after-save-hook’ or something, so your own changes will be tracked. Creating the database with the sqlite3 backend is supposed to perform much better with these partial updates. Since I spend most of my time in my little niche this is sufficient for my purposes and even if there have been small updates outside, the location I will be taken to is close enough most of the time (and a little reminder for creating a full index). > * Indexing the entire workspace will result in an intractably > large index. So how do you partition it? I don't bother and don't partition the project (comprising of 10k files, and 50+ nested subprojects) The total size of the DBs is about 60MB (files: 2, tags: 20, references: 38). > * Is the user restricted to querying a single partition of the > index? If yes, then that feels painfully restrictive. If no, > how does that user indicate which partition indices to combine? > How is combining accomplished? See above. > * How are duplicate filenames handled? By storing path names. Why don't you give it a whirl and see whether this suits you?