From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Dimech <dimech@gmx.com>
Cc: 57469-done@debbugs.gnu.org, gregory@heytings.org, uzibalqa@proton.me
Subject: bug#57469: Missing information about all the modes that fall under prog-mode.
Date: Mon, 29 Aug 2022 14:36:23 +0300 [thread overview]
Message-ID: <831qszxow8.fsf@gnu.org> (raw)
In-Reply-To: <trinity-d56143ef-202a-4570-af9a-7944d7f7e3f8-1661768968710@3c-app-mailcom-bs10> (message from Christopher Dimech on Mon, 29 Aug 2022 12:29:28 +0200)
> Cc: 57469@debbugs.gnu.org, uzibalqa <uzibalqa@proton.me>
> From: Christopher Dimech <dimech@gmx.com>
> Date: Mon, 29 Aug 2022 12:29:28 +0200
>
> > > OP does not want examples, but the actual list of language major-modes.
> > >
>
> Quite a list. If it is problematic to include in the manual, a built-in lisp function
> could be introduced that returns this list. Would be useful.
Not only is it problematic to include this in the manual, it will also
be inaccurate in every Emacs session out there, because the above list
cannot possibly include all the modes in 3rd-party packages out there.
Users who set such settings in the likes of prog-mode should
understand what they are doing. If they are unsure which modes this
will affect, they should do this in mode hooks of specific modes, noit
in prog-mode.
I'm closing this bug because there's no bug here.
next prev parent reply other threads:[~2022-08-29 11:36 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 [this message]
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
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=831qszxow8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57469-done@debbugs.gnu.org \
--cc=dimech@gmx.com \
--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).