From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: master 1e3b0f2: Improve doc strings of project.el Date: Sat, 20 Jun 2020 09:29:45 +0000 Message-ID: <87mu4ym6f6.fsf@thornhill.no> 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> Reply-To: Theodor Thornhill Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="24319"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philip@warpmail.net, emacs-devel@gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 20 11:32:47 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 1jmZrj-0006ES-Pl for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 11:32:47 +0200 Original-Received: from localhost ([::1]:48960 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmZri-0007oF-R0 for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Jun 2020 05:32:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33040) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jmZp4-0004vh-6I for emacs-devel@gnu.org; Sat, 20 Jun 2020 05:30:02 -0400 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]:24563) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jmZp0-0000T6-J1 for emacs-devel@gnu.org; Sat, 20 Jun 2020 05:30:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=protonmail; t=1592645395; bh=4t4TR/wK19v4qlOgT/zN5a0jzkm+uIo7zrEgQZA/8AM=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=aYw3lbJgcOTyRVb7MtDSeGmSFmSGydLzk5PhxPqQbwfWzRAK1X12s3Y2bzU7L6PH6 2/n8Eaoilt0Lt2Oq1PCCbMnjNj/qs/eCfIKkivsuAHUYET0GZ53XYdXKhUBY/L41DM /mfbDBMY27POJaG6e1ccP7KJjTzZ9adknGmsiWd1OVKSktPUqLe2o7jFFnJ+1BJu7U pH59//5UPDTTMyQWs9RIPvxwlUyZf/aL6bZI6uHUub/2i1HlevG9h8mVBZzDtACpp6 t1aZvJJ1/EUjHiWtKSqsHSQDDxVGDBJ14UyC9OnXSXjqeGrv2kqEojse9PKRtF41NT yMthbc4HYsXFw== In-Reply-To: <83a70yw1y8.fsf@gnu.org> Received-SPF: pass client-ip=185.70.40.131; envelope-from=theo@thornhill.no; helo=mail-40131.protonmail.ch X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/20 05:29:56 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action 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:252426 Archived-At: >> 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. =20 My proposal here isn't using default-directory. It would then check (buffer-file-name (cdr buffer)) in project-root. As such it would exclude other 'junk' buffers. After, the persisted other buffers are included as well. > 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? > 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.