From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#55930: 29.0.50; Removing some items from Emacs FAQ for MS Windows Date: Tue, 14 Jun 2022 14:59:52 +0300 Message-ID: <838rpztpzb.fsf@gnu.org> References: <86fsk9buyr.fsf@gnu.org> <83edztvid5.fsf@gnu.org> <86tu8o6hwx.fsf@gnu.org> <83a6agvldj.fsf@gnu.org> <86sfo891q0.fsf@gnu.org> <83y1y0u37f.fsf@gnu.org> <86a6afmwdr.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9809"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55930@debbugs.gnu.org To: Arash Esbati Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 14 14:01:19 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o15EU-0002BE-Tn for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Jun 2022 14:01:19 +0200 Original-Received: from localhost ([::1]:56516 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o15ET-0001ef-Cs for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Jun 2022 08:01:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o15EE-0001ZW-Ad for bug-gnu-emacs@gnu.org; Tue, 14 Jun 2022 08:01:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39359) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o15EE-0003lV-1n for bug-gnu-emacs@gnu.org; Tue, 14 Jun 2022 08:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o15EE-0008Uu-04 for bug-gnu-emacs@gnu.org; Tue, 14 Jun 2022 08:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Jun 2022 12:01:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55930 X-GNU-PR-Package: emacs Original-Received: via spool by 55930-submit@debbugs.gnu.org id=B55930.165520801632601 (code B ref 55930); Tue, 14 Jun 2022 12:01:01 +0000 Original-Received: (at 55930) by debbugs.gnu.org; 14 Jun 2022 12:00:16 +0000 Original-Received: from localhost ([127.0.0.1]:33256 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o15DT-0008Tk-OH for submit@debbugs.gnu.org; Tue, 14 Jun 2022 08:00:16 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:51890) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o15DO-0008SH-UV for 55930@debbugs.gnu.org; Tue, 14 Jun 2022 08:00:14 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33640) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o15DJ-0003Rs-HI for 55930@debbugs.gnu.org; Tue, 14 Jun 2022 08:00:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=hUJXQDvE0o1AjrXbIcoieBWTAgHnEt63Tj4SfYEz2u4=; b=dvh+1v6Mf+7D Ni6LPl5iDiUKniY7tvilzuDTcQyVzwmNAmgnDZroT2kF+UWSQMVtXL2F2jRUVbLPxKHJgDxEiabJ6 lGJ9+LIikDL3FwJKNHTOggZ4oduEf888ZWRJvFNMgIVSmYvEvHLRL2oE6CKfD4QMhCxvtHvcQACr8 6Ub4wd1r3xuDw5x0BsPrXQ1ZizYRR2K+n5ITdedRpQ/zrjjWvrlJ4o1Ro6rLfQifrjtqyqmAfqIhN tXx258AlBK3hsWkF/pDs+xNLOZp8KDlyNLq0aOC2hLIxjB1p8gAwL6PzQTBJ2VSQKby1WKtWxBQDG OHDlDHTGxdX2fFxh7wf1iQ==; Original-Received: from [87.69.77.57] (port=1409 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o15DI-0007XJ-A0; Tue, 14 Jun 2022 08:00:04 -0400 In-Reply-To: <86a6afmwdr.fsf@gnu.org> (message from Arash Esbati on Tue, 14 Jun 2022 11:23:28 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:234482 Archived-At: > From: Arash Esbati > Cc: 55930@debbugs.gnu.org > Date: Tue, 14 Jun 2022 11:23:28 +0200 > > Thanks. Next iteration is attached. Any comments welcome. Below. > -To compile Emacs on Windows, you will need the MinGW port of GCC and > -Binutils, the MinGW runtime and development environment, and the MSYS > -suite of tools. For the details, see the file @file{nt/INSTALL} in > -the Emacs source distribution. > +To compile Emacs on Windows, you will need either the MinGW-w64 port > +of GCC and Binutils, the MinGW-w64 runtime and development > +environment, and the MSYS2 suite of tools, or the MinGW port of GCC > +and the MSYS suite of tools. For the details, see the files > +@file{nt/INSTALL.W64} or @file{nt/INSTALL} in the Emacs source > +distribution. Instead of saying everything twice, once for MinGW64 and then for MinGW, I'd prefer to say it once for MinGW64, and mention MinGW only in one or two places, where the we explain the difference. That would be consistent with our recommendation to use MinGW64 except in rare exceptions, and will also avoid annoying repetition. > +Choosing the right environment from the ones mentioned above depends > +on your requirements and the Windows version you're using. The list > +below should give some guidance: > + > +@itemize @w{} > +@item > +MinGW-w64 and MSYS2 (requires 64-bit Windows 7 or newer) > + > +@itemize > +@item > +You want to build a 64-bit Emacs executable. > +@item > +You want to build a 32-bit Emacs executable and want to use a newer > +version of GCC than 9.x. > +@item > +You want to have access to recent versions of other libraries for > +displaying images, TLS etc@. out of the box. > +@end itemize > + > +@item > +MinGW and MSYS > +@itemize > +@item > +You're using a 32-bit version of Windows. > +@item > +You're using a Windows version prior to Windows 7. > +@end itemize > +@end itemize This again treats the two flavors of MinGW as equal, which I think is not what we want. My suggestion is to make it shorter and more to the point by saying something like We recommend that you use MinGW64, unless you need to build Emacs for running on versions of MS-Windows before Windows 7. I see no reason to say more or give more detailed list of considerations. > Latest versions of GDB might refuse to load the init file for security > reasons, unless you customize GDB; alternatively, use an explicit > -@kbd{source ./gdbinit} command after entering GDB. > -} in that directory, to define some extra commands for working with > -lisp while debugging, and set up breakpoints to catch abnormal > -aborts. > +@kbd{source ./gdbinit} command after entering GDB. } in that > +directory, to define some extra commands for working with lisp while > +debugging, and set up breakpoints to catch abnormal aborts. This looks like unnecessary whitespace change, perhaps caused by refilling the text? The newline before the closing "}" of @footnote is deliberate and shouldn't be removed, as it makes it easier to realize where the footnote ends. > @@ -1645,8 +1679,8 @@ Attachments with Gnus > In your @env{HOME} directory create a file called @file{.mailcap}, > with contents like the following: > @example > -application/zip "C:/Program Files/7-Zip/7zFM.exe" > -video/* "C:/Program Files/VideoLAN/VLC/vlc.exe" > +application/zip; "C:/Program Files/7-Zip/7zFM.exe" > +video/*; "C:/Program Files/VideoLAN/VLC/vlc.exe" > @end example Is that semi-colon really necessary? Did the Gnus syntax change? > Another possibility is Hunspell, which is available from > @uref{https://sourceforge.net/projects/ezwinports/files/?source=navbar, > -the ezwinports site}. > +the ezwinports site}. If you're using the MSYS2 distribution, you can > +install a recent version of either GNU Aspell or Hunspell through the > +package manager Pacman. @xref{Other useful ports}. Is Hunspell offered by MSYS2 a MinGW64 program or an MSYS program? If the latter, we should at least warn people about potential issues with I/O incompatibilities. Thanks.