From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 59610@debbugs.gnu.org
Subject: bug#59610: 29.0.50; Makefiles mentioned twice in `(emacs) Program Modes'
Date: Sat, 26 Nov 2022 16:22:06 +0200 [thread overview]
Message-ID: <83o7stssmp.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm_HLBw16NJVys6jugfUeO8uaZmCYdS+VYGrbbvMbVv6Q@mail.gmail.com> (message from Stefan Kangas on Sat, 26 Nov 2022 05:55:11 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 26 Nov 2022 05:55:11 -0800
>
> Severity: wishlist
>
> This node (info "(emacs) Program Modes") mentions makefiles twice:
>
> Emacs has programming language modes for Lisp, Scheme, the
> Scheme-based DSSSL expression language, Ada, ASM, AWK, C, C++, Fortran,
> Icon, IDL (CORBA), IDLWAVE, Java, Javascript, M4, Makefiles, Metafont
> ^^^^^^^^^
> (TeX’s companion for font creation), Modula2, Object Pascal,
> Objective-C, Octave, Pascal, Perl, Pike, PostScript, Prolog, Python,
> Ruby, Simula, SQL, Tcl, Verilog, and VHDL. An alternative mode for Perl
> is called CPerl mode. Modes are also available for the scripting
> languages of the common GNU and Unix shells, and MS-DOS/MS-Windows ‘BAT’
> files, and for makefiles, DNS master files, and various sorts of
> ^^^^^^^^^
> configuration files.
>
> Is it redundant to mention it twice in the same paragraph?
Yes, the second one should be deleted. Thanks.
> (BTW, I also note a difference in capitalization, but I don't know which
> is preferred.)
The first one. The second one is most probably a historical accident.
next prev parent reply other threads:[~2022-11-26 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 13:55 bug#59610: 29.0.50; Makefiles mentioned twice in `(emacs) Program Modes' Stefan Kangas
2022-11-26 14:22 ` Eli Zaretskii [this message]
2022-11-26 14:57 ` Stefan Kangas
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=83o7stssmp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59610@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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).