From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master 1e3b0f2: Improve doc strings of project.el Date: Sat, 11 Jul 2020 15:35:29 +0300 Message-ID: <83lfjqnsa6.fsf@gnu.org> References: <87bllfqj82.fsf@warpmail.net> <83h7v7xf7w.fsf@gnu.org> <831rmayj55.fsf@gnu.org> <6dc2c2ac-8e17-f044-dc78-8c109f936ad2@yandex.ru> <83wo42w83e.fsf@gnu.org> <6762abf5-71c1-aa54-1bac-d4c90c20870b@yandex.ru> <831rmavsuq.fsf@gnu.org> <83a70wv4mj.fsf@gnu.org> <5542db0c-cc0d-2743-87ae-7728a0cc94bb@yandex.ru> <83ftaf2rj2.fsf@gnu.org> <43a8f8d4-83fb-f012-8e1d-c1a618b0ef59@yandex.ru> <83mu4m0vub.fsf@gnu.org> <44f2f1f4-ae34-f0bf-b153-f33b8ee6069f@yandex.ru> <83mu4fvjh3.fsf@gnu.org> <7c2e93d4-8d86-bbbb-77a0-bf5d73051907@yandex.ru> <83imf2t4w4.fsf@gnu.org> <95fd893e-0da5-4cdc-a3e8-3c22af750aae@yandex.ru> <837dvfs6wg.fsf@gnu.org> <8bc1f381-248f-5cee-c3c6-a29d411a2f74@yandex.ru> <837dvbphs0.fsf@gnu.org> <83365zp78d.fsf@gnu.org> <831rlipmgg.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25666"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philip@warpmail.net, theo@thornhill.no, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 11 14:36:12 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 1juEjk-0006ac-Gq for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jul 2020 14:36:12 +0200 Original-Received: from localhost ([::1]:49924 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1juEjj-0006k6-Jk for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jul 2020 08:36:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1juEjG-0006D7-Uk for emacs-devel@gnu.org; Sat, 11 Jul 2020 08:35:42 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55186) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1juEjF-0007Yl-MZ; Sat, 11 Jul 2020 08:35:41 -0400 Original-Received: from [176.228.60.248] (port=2522 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1juEjD-0008WV-Vk; Sat, 11 Jul 2020 08:35:41 -0400 In-Reply-To: (message from Dmitry Gutov on Sat, 11 Jul 2020 14:29:04 +0300) 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:252862 Archived-At: > Cc: theo@thornhill.no, philip@warpmail.net, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Sat, 11 Jul 2020 14:29:04 +0300 > > > Having commands to add or remove files from the project would allow us > > to advertise those commands as the supported means of doing so. We > > could also have a command to "refresh" the project, for those who for > > some reasons will prefer doing that externally. > > These are options, of course. But this will make Emacs project support > more high-maintenance than in "other editors". > > Take a random modern editor, open an existing project in it (it will > show up in the side panel, usually). Then create a new file in its root > directory using some external means. If it's not ignored by existing > configuration, it will automatically show in the project drawer as well. > > We should support that. As long as it makes sense, yes. But when it starts requiring us to jump through hoops, we don't need to be afraid of doing things differently. > > but if this is what you think the doc > > string should say, then I will fix it again to be better. > > That sounds threatening. You are always interpreting what I say in the worst possible way, for some reason. > Like I said, you're welcome to suggest a better phrasing, for this and > the other command (as long as the descriptions remain accurate). Go > ahead and commit the new versions, if you like. Done.