From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Hi-Angel@yandex.ru, emacs-devel@gnu.org, jonas@bernoul.li
Subject: Re: Adding git-commit highlight mode?
Date: Thu, 02 Jan 2025 23:01:47 +0200 [thread overview]
Message-ID: <86frm1hqv8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkzy4O7V-+p=1k6K5scBvUa4VfeZ0MkDet-o4rmFGU=AQ@mail.gmail.com> (message from Stefan Kangas on Thu, 2 Jan 2025 14:10:22 -0600)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 2 Jan 2025 14:10:22 -0600
> Cc: emacs-devel@gnu.org, Jonas Bernoulli <jonas@bernoul.li>
>
> > 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?
next prev parent reply other threads:[~2025-01-02 21:01 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 [this message]
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
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=86frm1hqv8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Hi-Angel@yandex.ru \
--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).