From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57469-done@debbugs.gnu.org, dimech@gmx.com, gregory@heytings.org
Subject: bug#57469: Missing information about all the modes that fall under prog-mode.
Date: Mon, 29 Aug 2022 16:33:15 +0000 [thread overview]
Message-ID: <07GQh0aJdHdMxJUo6wAyc0g0q43iNFer5O7puiyJAGMLL9-MXGcKNCkkHLQQGKwHZzCJyXVyTav9TbCtOyQvAs6aH8bveNqwY4l3iP4uv8o=@proton.me> (raw)
In-Reply-To: <83v8qbw5w7.fsf@gnu.org>
------- Original Message -------
On Monday, August 29th, 2022 at 1:12 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Mon, 29 Aug 2022 11:53:40 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: Christopher Dimech dimech@gmx.com, 57469-done@debbugs.gnu.org, gregory@heytings.org
> >
> > I like the idea of calling a function. At least get information only about built-in
> > language major modes. Would still be much better than current situation.
>
>
> The language modes that come with Emacs change frequently, so keeping
> that list up to date would be a significant maintenance burden. No,
> thanks.
>
> You should just keep in mind that every mode for something that looks
> like a programming language inherits from prog-mode.
Gregory manages to compile a list. How was that done?
next prev parent reply other threads:[~2022-08-29 16:33 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 [this message]
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
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='07GQh0aJdHdMxJUo6wAyc0g0q43iNFer5O7puiyJAGMLL9-MXGcKNCkkHLQQGKwHZzCJyXVyTav9TbCtOyQvAs6aH8bveNqwY4l3iP4uv8o=@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=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).