From: Stefan Kangas <stefan@marxist.se>
To: Juri Linkov <juri@linkov.net>
Cc: 50674@debbugs.gnu.org
Subject: bug#50674: Major mode for etc/AUTHORS with basic font-locking
Date: Mon, 20 Sep 2021 00:42:54 -0700 [thread overview]
Message-ID: <CADwFkmkDZ3E37T8Y=kmkshC9mN2LehMXi3660UL1vc6HfFh=ug@mail.gmail.com> (raw)
In-Reply-To: <87ee9jpxke.fsf@mail.linkov.net>
Juri Linkov <juri@linkov.net> writes:
> I really see no difference from etc-authors-mode and e.g.
> etc-fstab-generic-mode defined in generic-x.el by define-generic-mode.
> And still it can be autoloaded like c++-mode-syntax-table used to be autoloaded.
That means that a user will see font-locking in some files, only if she
has first visited AUTHORS. In a subsequent Emacs session, the user will
be surprised to see that the font-locking is no longer there.
IOW, I can agree to put it in generic-x.el, but only if we autoload some
other modes in there. Such as the fstab mode. Otherwise this makes no
sense to me.
A natural first step would be to make those modes load unconditionally,
but that proposal has been rejected; see my last two commits to
generic-x.el. Perhaps it will be okay to load only some of the modes
unconditionally.
This would also have to be coupled with the necessary documentation
changes to generic-x.el, to explain that this file is not only about
`define-generic-mode'.
Personally, I'd rather create a new file for small modes than go down
this rabbit hole. generic-x.el is hardly the best library name or
location.
next prev parent reply other threads:[~2021-09-20 7:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 14:12 bug#50674: Major mode for etc/AUTHORS with basic font-locking Stefan Kangas
2021-09-19 15:19 ` Lars Ingebrigtsen
2021-09-19 16:25 ` Eli Zaretskii
2021-09-19 21:58 ` Stefan Kangas
2021-09-21 19:54 ` Stefan Kangas
2021-09-19 16:33 ` Juri Linkov
2021-09-19 17:38 ` Stefan Kangas
2021-09-20 6:41 ` Juri Linkov
2021-09-20 7:42 ` Stefan Kangas [this message]
2021-09-20 9:14 ` Stefan Kangas
2021-09-20 15:24 ` Juri Linkov
2021-09-21 6:12 ` Lars Ingebrigtsen
2021-09-21 6:25 ` Eli Zaretskii
2021-09-21 6:28 ` Lars Ingebrigtsen
2021-09-21 7:57 ` Stefan Kangas
2021-09-21 8:36 ` Eli Zaretskii
2021-09-21 8:58 ` Stefan Kangas
2021-09-21 9:24 ` Eli Zaretskii
2021-09-21 11:18 ` Stefan Kangas
2021-09-21 11:25 ` Eli Zaretskii
2021-09-21 8:28 ` Stefan Kangas
2021-09-21 16:51 ` Lars Ingebrigtsen
2021-09-21 17:56 ` Lars Ingebrigtsen
2021-09-21 18:33 ` Stefan Kangas
2021-09-21 18:41 ` Juri Linkov
2021-09-21 18:56 ` Eli Zaretskii
2021-09-21 19:22 ` Stefan Kangas
2021-09-21 17:28 ` Juri Linkov
2021-09-21 18:33 ` Stefan Kangas
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='CADwFkmkDZ3E37T8Y=kmkshC9mN2LehMXi3660UL1vc6HfFh=ug@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=50674@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).