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: emacs-27 561e9fb: Improve documentation of project.el commands Date: Mon, 23 Mar 2020 16:29:11 +0200 Message-ID: <83o8snb0w8.fsf@gnu.org> References: <20200321112658.6254.3414@vcs0.savannah.gnu.org> <20200321112700.1883720E43@vcs0.savannah.gnu.org> <64df0421-3dd1-d2af-7f3a-94499d7a86ff@yandex.ru> <83pnd4cw22.fsf@gnu.org> <1e1dbc65-f232-dcdf-969b-a34cb3276914@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="77627"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 23 15:29:58 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 1jGO5V-000K4L-E7 for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Mar 2020 15:29:57 +0100 Original-Received: from localhost ([::1]:34530 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jGO5U-0004ka-Gp for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Mar 2020 10:29:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40372) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jGO4i-0003cJ-1V for emacs-devel@gnu.org; Mon, 23 Mar 2020 10:29:09 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53941) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jGO4h-0003NH-Tu; Mon, 23 Mar 2020 10:29:07 -0400 Original-Received: from [176.228.60.248] (port=4392 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jGO4g-0005xV-Q2; Mon, 23 Mar 2020 10:29:07 -0400 In-Reply-To: <1e1dbc65-f232-dcdf-969b-a34cb3276914@yandex.ru> (message from Dmitry Gutov on Sun, 22 Mar 2020 23:24:13 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:245715 Archived-At: > Cc: emacs-devel@gnu.org > From: Dmitry Gutov > Date: Sun, 22 Mar 2020 23:24:13 +0200 > > > Yes, I was aware of that. But since saying that a project is a > > collection of arbitrary files would make the issue harder to > > understand, > > Regardless of how we define a project, this heading can say "Commands > for handling files in a project" without a loss of clarify, I believe. It isn't about clarity, I think, it's about making the feature less abstract and more lucrative to our audience. > > I decided to compromise, as I believe currently no one > > really uses this for non-program files. If this ever becomes a > > practical problem, we can always rephrase. > > You're probably responding to my second quote here. But why not say > "Command for handling files in a project"? Again, no real loss of > clarity, this sentence is not a definition. For the same reason: to be more attractive to the reader. > >> And is "hierarchy of directories" a better term than "directory tree"? > > > > I think it's the same thing. Wed use both interchangeably in our > > documentation. Why, you think "directory tree" will be easier to > > understand or something? > > This choice of words gives me a somewhat more complicated mental image, > like a sparse collection of subdirectories, where some are included, and > some are not. Which kind of comes out to the same thing, but in a more > complex way. That's not what I had in mind, but these commands do support sparse trees as well: it's all about what are "the project files", isn't it? Would "directory tree hierarchy" solve your problems here?