From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 57469-done@debbugs.gnu.org, dimech@gmx.com,
Eli Zaretskii <eliz@gnu.org>,
gregory@heytings.org
Subject: bug#57469: Missing information about all the modes that fall under prog-mode.
Date: Tue, 30 Aug 2022 04:05:14 +0000 [thread overview]
Message-ID: <8Aoy4OrTztXTT2nXVdeddLjWtQr-T8BX2N0u0nhwqnij24aDgAFoFGglBmeX0rZI6sT8Byap6VW9QMd8kyWfWv4HZWL5a9siC3aRo75CLv4=@proton.me> (raw)
In-Reply-To: <c3b98d3a398205f2541c9f93d1b92bea@webmail.orcon.net.nz>
------- Original Message -------
On Tuesday, August 30th, 2022 at 2:16 AM, Phil Sainty <psainty@orcon.net.nz> wrote:
> Following up my own comment, grepping the codebase for
> define-derived-mode definitions would require multiple
> passes (in order to establish chains of derivatives leading
> back to prog-mode), so "loading all the things" and testing
> in elisp seems simpler after all.
It is.
prev parent reply other threads:[~2022-08-30 4:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 4:12 bug#57469: Missing information about all the modes that fall under prog-mode uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 5:49 ` Gregory Heytings
2022-08-29 6:05 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 8:38 ` Gregory Heytings
2022-08-29 8:51 ` Christopher Dimech
2022-08-29 9:13 ` Gregory Heytings
2022-08-29 10:29 ` Christopher Dimech
2022-08-29 11:36 ` Eli Zaretskii
2022-08-29 11:53 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 13:12 ` Eli Zaretskii
2022-08-29 16:33 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 21:24 ` Phil Sainty
2022-08-30 2:16 ` Phil Sainty
2022-08-30 4:05 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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='8Aoy4OrTztXTT2nXVdeddLjWtQr-T8BX2N0u0nhwqnij24aDgAFoFGglBmeX0rZI6sT8Byap6VW9QMd8kyWfWv4HZWL5a9siC3aRo75CLv4=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=57469-done@debbugs.gnu.org \
--cc=dimech@gmx.com \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=psainty@orcon.net.nz \
--cc=uzibalqa@proton.me \
/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).