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 13:07:56 +0300 Message-ID: <834kr6vymb.fsf@gnu.org> References: <87bllfqj82.fsf@warpmail.net> <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> <83a70yw1y8.fsf@gnu.org> <87mu4ym6f6.fsf@thornhill.no> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="41269"; 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 12:08:46 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 1jmaQY-000AfT-Ep for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 12:08:46 +0200 Original-Received: from localhost ([::1]:38850 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmaQX-0002Kd-Fy for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 06:08:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39076) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jmaPw-0001Un-5j for emacs-devel@gnu.org; Sat, 20 Jun 2020 06:08:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37352) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmaPv-0005xO-Gi; Sat, 20 Jun 2020 06:08:07 -0400 Original-Received: from [176.228.60.248] (port=3628 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jmaPu-00040w-NP; Sat, 20 Jun 2020 06:08:07 -0400 In-Reply-To: <87mu4ym6f6.fsf@thornhill.no> (message from Theodor Thornhill on Sat, 20 Jun 2020 09:29:45 +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:252427 Archived-At: > Date: Sat, 20 Jun 2020 09:29:45 +0000 > From: Theodor Thornhill > Cc: dgutov@yandex.ru, philip@warpmail.net, emacs-devel@gnu.org > > > 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. > > Maybe we should reconsider the API then? It seems to me like you don't > want this generic interface, and rather would like a more general notion > of what a project is. You want to have a more granular approach, > something akin to bookmark.el. Am I reading you correctly here? Which API did you have in mind? In any case, my proposal was not about the API itself, it was more about the implementation of the API. For example, we could have an implementation of the generic project-files API that consulted some list instead of asking the VCS or the filesystem to provide the files. > > More to the point, my question is how would adding a buffer to the > > project be recorded and where, under your proposal? > > We already are persisting a project list under "user-emacs-directory" in > a readable lisp format. I guess this could be extended to include the > added buffers? Not sure how unwieldy this can get, though. That's one possibility, yes.