From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Hi-Angel@yandex.ru, emacs-devel@gnu.org
Subject: Re: Adding git-commit highlight mode?
Date: Thu, 02 Jan 2025 22:17:04 +0200 [thread overview]
Message-ID: <86o70phsxr.fsf@gnu.org> (raw)
In-Reply-To: <083310b3-a288-5c75-c835-84595e134682@gmail.com> (message from Jim Porter on Thu, 2 Jan 2025 11:17:08 -0800)
> Date: Thu, 2 Jan 2025 11:17:08 -0800
> From: Jim Porter <jporterbugs@gmail.com>
>
> On 1/2/2025 10:30 AM, Konstantin Kharlamov wrote:
> > But Emacs seems to be the only widely popular editor that still doesn't
> > provide OOTB at least syntax highlight for git-commit format. So, does
> > anyone have opposition to adding a major mode that would be bound to
> > filenames like `COMMIT_EDITMSG` and others, and would provide the
> > aforementioned highlight?
>
> For what it's worth, I wrote a very simple package to do this for
> myself, since I don't use Magit. (I'm just so used to the Git command
> line that I've never taken the time to mess with Magit.)
>
> https://github.com/jimporter/git-command-modes/
>
> I'm happy to assign copyright to the FSF for this or to upstream this
> into the Emacs tree, or whatever people would like here.
I don't mind adding this, but please make sure the mode(s) for editing
log messages provide at least the features we have in change-log-mode.
Thanks.
next prev parent reply other threads:[~2025-01-02 20:17 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
2025-01-02 19:17 ` Jim Porter
2025-01-02 19:19 ` Konstantin Kharlamov
2025-01-02 20:17 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86o70phsxr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Hi-Angel@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.