From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master 1e3b0f2: Improve doc strings of project.el Date: Sat, 20 Jun 2020 11:55:59 +0300 Message-ID: <83a70yw1y8.fsf@gnu.org> References: <87bllfqj82.fsf@warpmail.net> <83o8pfxhzq.fsf@gnu.org> <83imfnxgt3.fsf@gnu.org> <626efe11-0f9c-081b-11dd-0d61cee8168d@yandex.ru> <83h7v7xf7w.fsf@gnu.org> <831rmayj55.fsf@gnu.org> <6dc2c2ac-8e17-f044-dc78-8c109f936ad2@yandex.ru> <83wo42w83e.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="9275"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philip@warpmail.net, emacs-devel@gnu.org, dgutov@yandex.ru To: Theodor Thornhill Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 20 10:56:43 2020 Return-path: Envelope-to: ged-emacs-devel@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 1jmZIn-0002GX-5h for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 10:56:41 +0200 Original-Received: from localhost ([::1]:41600 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmZIm-0004pq-8U for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 04:56:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55240) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jmZII-0004P3-Iu for emacs-devel@gnu.org; Sat, 20 Jun 2020 04:56:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36907) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmZIH-0003pE-4T; Sat, 20 Jun 2020 04:56:09 -0400 Original-Received: from [176.228.60.248] (port=3209 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jmZIG-0008Am-04; Sat, 20 Jun 2020 04:56:08 -0400 In-Reply-To: (message from Theodor Thornhill on Sat, 20 Jun 2020 07:43:57 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:252425 Archived-At: > Date: Sat, 20 Jun 2020 07:43:57 +0000 > From: Theodor Thornhill > Cc: philip@warpmail.net, emacs-devel@gnu.org > > What if we offer this workflow: > > - the git implementation of the backend offers only file bound alternatives. To me that seems kind of > reasonable, since its task is to track actual files and ignores. > > - in addition, we offer something similar to org-add-to-agenda-files. Then my *xref*, Andriis inferior python, > shells and whatever you want to add can be added. > > - obviously we then need an option to delete files from that new list > > I imagine this being implemented just with a new defvar- project-additional-buffers, or something like that. > > Then switch to buffer just adds them as well. > > Could something like this be viable? I proposed to find a different way of telling which buffer is related to a project, other than by looking at its default-directory. We could design a way of doing that which would then support adding buffers to a project quite easily. But Dmitry doesn't think we should go that way. More to the point, my question is how would adding a buffer to the project be recorded and where, under your proposal?