From: Christopher Dimech <dimech@gmx.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: 57469@debbugs.gnu.org, uzibalqa <uzibalqa@proton.me>
Subject: bug#57469: Missing information about all the modes that fall under prog-mode.
Date: Mon, 29 Aug 2022 12:29:28 +0200 [thread overview]
Message-ID: <trinity-d56143ef-202a-4570-af9a-7944d7f7e3f8-1661768968710@3c-app-mailcom-bs10> (raw)
In-Reply-To: <a77ca586b6b818fa0db9@heytings.org>
> Sent: Monday, August 29, 2022 at 9:13 PM
> From: "Gregory Heytings" <gregory@heytings.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: 57469@debbugs.gnu.org, "uzibalqa" <uzibalqa@proton.me>
> Subject: Re: bug#57469: Missing information about all the modes that fall under prog-mode.
>
>
> >
> > 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.
> antlr-mode asm-mode autoconf-mode awk-mode bat-mode cfengine2-mode
> cfengine3-mode c++-mode c-mode cperl-mode css-mode dcl-mode dsssl-mode
> edebug-eval-mode elisp-byte-code-mode emacs-lisp-mode erts-mode f90-mode
> fortran-mode gdb-script-mode gnus-edit-form-mode gnus-kill-file-mode
> gnus-score-mode help-fns--edit-value-mode icon-mode idl-mode idlwave-mode
> java-mode js-json-mode js-jsx-mode js-mode ld-script-mode less-css-mode
> lisp-data-mode lisp-interaction-mode lisp-mode m2-mode m4-mode
> makefile-automake-mode makefile-bsdmake-mode makefile-gmake-mode
> makefile-imake-mode makefile-makepp-mode makefile-mode mercury-mode
> meta-common-mode metafont-mode metapost-mode mixal-mode objc-mode
> octave-mode opascal-mode pascal-mode perl-mode pike-mode plstore-mode
> prolog-mode ps-mode python-mode ruby-mode scheme-mode scss-mode sh-mode
> sieve-mode simula-mode sql-mode tcl-mode vera-mode verilog-mode vhdl-mode
>
next prev parent reply other threads:[~2022-08-29 10:29 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 [this message]
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
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=trinity-d56143ef-202a-4570-af9a-7944d7f7e3f8-1661768968710@3c-app-mailcom-bs10 \
--to=dimech@gmx.com \
--cc=57469@debbugs.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).