unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: 57469@debbugs.gnu.org
Subject: bug#57469: Missing information about all the modes that fall under prog-mode.
Date: Mon, 29 Aug 2022 08:38:43 +0000	[thread overview]
Message-ID: <a77ca586b6e173eaceef@heytings.org> (raw)
In-Reply-To: <ecdYXTBwDffdXUiSvtRiBlT8IH9BsRjxTHbcHW6k8EtVjEFs0oP-i432HtKgHS5kEba5UmaGNv63fUq61YytsLftTCVKmqNnlQhH4QbYgto=@proton.me>


>
> Your elaboration does not bring to light anything valuable to users.
>

I misunderstood your question, that's all.

>
> When one uses prog-mode-hook , which major modes are affected?  The 
> manuals do not say.
>

All major modes that derive from prog-mode, that is, all major modes with 
which program sources are edited.  For example, c-mode, sh-mode, 
fortran-mode and perl-mode.





  reply	other threads:[~2022-08-29  8:38 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 [this message]
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

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=a77ca586b6e173eaceef@heytings.org \
    --to=gregory@heytings.org \
    --cc=57469@debbugs.gnu.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).