unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Hi-Angel@yandex.ru, emacs-devel@gnu.org
Subject: Re: Adding git-commit highlight mode?
Date: Fri, 03 Jan 2025 08:45:19 +0200	[thread overview]
Message-ID: <868qrsief4.fsf@gnu.org> (raw)
In-Reply-To: <875xmwykuk.fsf@aarsen.me> (message from Arsen Arsenović on Thu, 02 Jan 2025 22:19:47 +0100)

> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: Konstantin Kharlamov <Hi-Angel@yandex.ru>,  emacs-devel@gnu.org
> Date: Thu, 02 Jan 2025 22:19:47 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> >> Cc: emacs-devel@gnu.org
> >> Date: Thu, 02 Jan 2025 22:07:46 +0300
> >> 
> >> On Thu, 2025-01-02 at 21:01 +0200, Eli Zaretskii wrote:
> >> > Do you plan to make this mode be descendant of change-log-mode?
> >> > something else?
> >> 
> >> 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 is also a derivative of text-mode.  Its advantage is
> > that it already provides font-lock for the style of log entries we
> > use.
> 
> A thing that a git commit mode ought to do, however, is set fill-column
> to 72, highlight any content on line 2 as erroneous, and limit the first
> line to 50 characters.  This is conventional in Git:
> https://git-scm.com/docs/git-commit#_discussion
> https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project.html#_commit_guidelines
> 
> Naturally, all of this ought to be configurable, but these are important
> features and sane defaults, and are one of the primary reasons why I
> initially installed magit (though, I now use it for general Git
> interaction while editing).
> 
> As far as I know, some of these guidelines conflict with changelog
> guidelines.

Being a descendant of change-log-mode doesn't mean the derivative mode
cannot change the settings it needs to change.  ChangeLog files are
indented, whereas commit log messages aren't, so some customization of
the whitespace and fill-column will sure be needed.  But, for example,
the change-log-fill-parenthesized-list capability will come in very
handy.



  parent reply	other threads:[~2025-01-03  6:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 18:30 Adding git-commit highlight mode? Konstantin Kharlamov
2025-01-02 19:01 ` Eli Zaretskii
2025-01-02 19:07   ` Konstantin Kharlamov
2025-01-02 20:10     ` Stefan Kangas
2025-01-02 21:01       ` Eli Zaretskii
2025-01-02 21:38         ` Stefan Kangas
2025-01-03  5:26           ` Jim Porter
2025-01-02 21:40       ` Konstantin Kharlamov
2025-01-03  5:29         ` Jim Porter
2025-01-03 13:08       ` Jonas Bernoulli
2025-01-02 20:11     ` Eli Zaretskii
2025-01-02 21:19       ` Arsen Arsenović
2025-01-02 21:53         ` Stefan Kangas
2025-01-02 22:27           ` Arsen Arsenović
2025-01-03 21:02           ` Sean Whitton
2025-01-04  7:17             ` Eli Zaretskii
2025-01-04  9:52               ` Sean Whitton
2025-01-03  6:45         ` Eli Zaretskii [this message]
2025-01-02 19:17 ` Jim Porter
2025-01-02 19:19   ` Konstantin Kharlamov
2025-01-02 20:17   ` Eli Zaretskii
2025-01-03 21:14   ` Björn Bidar
2025-01-05 14:39     ` Philip Kaludercic
2025-01-05 22:48       ` Konstantin Kharlamov
     [not found]   ` <87r05jbnw2.fsf@>
2025-01-03 22:52     ` Konstantin Kharlamov
2025-01-04  1:22       ` Björn Bidar
     [not found]       ` <87v7uv9xub.fsf@>
2025-01-04  1:45         ` Konstantin Kharlamov
2025-01-05  0:46           ` Björn Bidar
     [not found]           ` <871pxiulxz.fsf@>
2025-01-05  3:55             ` Konstantin Kharlamov
2025-01-04 12:50         ` Jonas Bernoulli
2025-01-04 17:20           ` Jonas Bernoulli
2025-01-05  0:32           ` Björn Bidar
2025-01-05 18:47           ` Jim Porter
2025-01-05  0:42 ` Björn Bidar
     [not found] ` <875xmuum48.fsf@>
2025-01-05  3:49   ` Konstantin Kharlamov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868qrsief4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Hi-Angel@yandex.ru \
    --cc=arsen@aarsen.me \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).