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: Fri, 19 Jun 2020 18:19:06 +0300 Message-ID: <83eeqbxevp.fsf@gnu.org> References: <87bllfqj82.fsf@warpmail.net> <83o8pfxhzq.fsf@gnu.org> <83imfnxgt3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="14392"; 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 Fri Jun 19 17:20:22 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 1jmIoC-0002x8-5V for ged-emacs-devel@m.gmane-mx.org; Fri, 19 Jun 2020 17:20:00 +0200 Original-Received: from localhost ([::1]:34060 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmIoB-0006Mg-6x for ged-emacs-devel@m.gmane-mx.org; Fri, 19 Jun 2020 11:19:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55054) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jmInY-0005w8-2A for emacs-devel@gnu.org; Fri, 19 Jun 2020 11:19:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48191) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jmInX-0001FN-80; Fri, 19 Jun 2020 11:19:19 -0400 Original-Received: from [176.228.60.248] (port=2158 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jmInW-0000r6-FQ; Fri, 19 Jun 2020 11:19:18 -0400 In-Reply-To: (message from Theodor Thornhill on Fri, 19 Jun 2020 15:02: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:252371 Archived-At: > Date: Fri, 19 Jun 2020 15:02:45 +0000 > From: Theodor Thornhill > Cc: philip@warpmail.net, dgutov@yandex.ru, emacs-devel@gnu.org > > As another provocative thought, should we perhaps consider the > major-mode of the buffer? > > Maybe, but I don’t see how just yet. I thought about this, but a project isn’t generally bound to one major > mode, is it? I’d love some tips here. A project could specify a list of major-modes, couldn't it? That would generally derive from the project's "purpose" or "goal", for lack of a better word. For example, a project where you build a program would have prog-mode or some of its descendants in the list, and perhaps also Texinfo and/or markdown for docs. A project whose purpose is to write an essay or a blog or might use descendants of text-mode. Etc., etc.