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: Adding git-commit highlight mode? Date: Thu, 02 Jan 2025 23:01:47 +0200 Message-ID: <86frm1hqv8.fsf@gnu.org> References: <37733be4476e1c2b6e873c967c79cb0035959a9e.camel@yandex.ru> <86wmfdhwg7.fsf@gnu.org> <0347118b217c57e4e62018547883fad5f1d1e63e.camel@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8603"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Hi-Angel@yandex.ru, emacs-devel@gnu.org, jonas@bernoul.li To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 02 22:03:06 2025 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 1tTSLR-00024C-GO for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jan 2025 22:03:05 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tTSKl-0007zN-0g; Thu, 02 Jan 2025 16:02:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tTSKi-0007yo-SQ for emacs-devel@gnu.org; Thu, 02 Jan 2025 16:02:21 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tTSKg-00089q-7R; Thu, 02 Jan 2025 16:02:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=JpjCEh1WUjjGh04xpVRqlBkUkh43ih3MyLxxU4Tembo=; b=AS0qaOkuuGNhxCVP8w8V jK8Q8KdrZaSzqrm5prlgSrUlMjKDJxoSMZcGc5jHf5Fwl7bTfY8qx5U5uyVwMqLA/tdOTgriukF1F j8R4F0VaE1TwKm2v10fG9MltG+ojfp+V1TSvRAiFVquKKxnGma/0VCAwvkoAp07CL4oPftRa82ih2 LYf8FHWUEs+sxVreAdHSSriulViHUlBprjPdwJVso95UPC2GAPR8CiaqDBap9zPjeOvQ8rAONjcV/ Wh45utNsjED4t33g61rh5fwrwWPC8jjigOXhnZIyEjhBOJjKm/QIFkgBK+2ddMPzoNPIKz+PBQqap N9UG4kTq5weJfA==; In-Reply-To: (message from Stefan Kangas on Thu, 2 Jan 2025 14:10:22 -0600) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327596 Archived-At: > From: Stefan Kangas > Date: Thu, 2 Jan 2025 14:10:22 -0600 > Cc: emacs-devel@gnu.org, Jonas Bernoulli > > > I thought of deriving from text-mode. I don't know much of change-log- > > mode besides what it says in the mode title and now that I'm looking at > > mode description it also sounds pretty vague. So… I could derive it > > from change-log-mode if you think it's useful, but I'd rely on your > > judgment here 😊 > > `change-log-mode` implements the anachronistic ChangeLog format favored > by GNU. That "anachronistic format" allows plain text, so I don't quite see how using change-log-mode as the parent mode will cause us lose anything? What's the harm in getting everything text-mode descendants can do, plus support for "anachronistic" formats?