From: Jim Porter <jporterbugs@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Hi-Angel@yandex.ru, emacs-devel@gnu.org, jonas@bernoul.li
Subject: Re: Adding git-commit highlight mode?
Date: Thu, 2 Jan 2025 21:26:44 -0800 [thread overview]
Message-ID: <54c3a22c-b539-5e40-7f7a-82705366aadf@gmail.com> (raw)
In-Reply-To: <CADwFkm=iBtZmGsEw6riD6r63PF7ynXOSFA9V3p+sTquq1rZcVA@mail.gmail.com>
On 1/2/2025 1:38 PM, Stefan Kangas wrote:
> Instead of inheriting from it, I'd propose creating an optional minor
> mode, that users can enabled when they need to, plus a globalized mode
> for those that want it on always. That would also expand it to be
> useful also with Magit's `git-commit-mode`, for example, which I'd
> personally welcome. (FWIW, I happen to think that the paragraph filling
> rules would be the most interesting feature in such a minor mode.)
You took the words out of my mouth. :) I'm not sure about all the
details here, but some way of "embedding" change-log-mode into other
major modes would be really helpful. Maybe there are other ways to do
this instead, like multi-major-mode support (e.g. in html-mode and the
like), but I think it makes sense not to *require* change-log-mode if it
could get in the way for users who don't write commits like that.
next prev parent reply other threads:[~2025-01-03 5:26 UTC|newest]
Thread overview: 37+ 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 [this message]
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-15 15:59 ` Konstantin Kharlamov
2025-01-18 18:06 ` Jim Porter
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
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=54c3a22c-b539-5e40-7f7a-82705366aadf@gmail.com \
--to=jporterbugs@gmail.com \
--cc=Hi-Angel@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=stefankangas@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 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).