From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Emacs for Windows Date: Sun, 12 Oct 2014 13:53:48 +0200 Message-ID: <87lholld0z.fsf@wanadoo.es> References: <874mvcc1jh.fsf@gmail.com> <83d2a0bfwu.fsf@gnu.org> <83y4so9jjy.fsf@gnu.org> <87bnpimxal.fsf@wanadoo.es> <83siiu8ux9.fsf@gnu.org> <877g06mw9n.fsf@wanadoo.es> <83oati8uek.fsf@gnu.org> <8738aumvf9.fsf@wanadoo.es> <83mw928sd0.fsf@gnu.org> <87ppdyl7iw.fsf@wanadoo.es> <83a95195rx.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413114870 26012 80.91.229.3 (12 Oct 2014 11:54:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Oct 2014 11:54:30 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Oct 12 13:54:24 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XdHjE-0007ex-BX for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Oct 2014 13:54:24 +0200 Original-Received: from localhost ([::1]:56954 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdHjD-0007aL-Td for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Oct 2014 07:54:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdHiz-0007aF-22 for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 07:54:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdHir-0007hg-9c for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 07:54:08 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:48925) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdHir-0007ha-30 for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 07:54:01 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XdHip-0007Un-43 for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 13:53:59 +0200 Original-Received: from 198.red-79-158-173.staticip.rima-tde.net ([79.158.173.198]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Oct 2014 13:53:59 +0200 Original-Received: from ofv by 198.red-79-158-173.staticip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Oct 2014 13:53:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 91 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 198.red-79-158-173.staticip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:Z/XFcJsxidOJJJAV8i0obamn7nE= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:100447 Archived-At: Eli Zaretskii writes: >> Guile is not available as a native package. > > Then what is > > https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-guile > > ? The fact that a PKGBUILD exists for MinGW-w64 (or MSYS2) does not mean that it is considered ready for consumption. Until it does appear on the pacman database at the user's end, the binary package is not available. >> It depends on the MSYS2 Posix layer. > > Sorry, I don't understand what that means. Are you saying it's an > MSYS2 build, rather than a native MinGW build? Yes. [snip] >> Hunspell es available as a native package: > > The main problem with the upstream sources, which affects Unix as > well, is that Hunspell reports offsets in bytes, not in characters, so > the Emacs ispell.el interface barfs unless you use a single-byte > encoding (whereas the default is to use UTF-8 with Aspell and > Hunspell). So this means this port is not useful for Emacs users. Thanks for the info. From now on I'll resist the temptation of switching to hunspell. >> bison is available as a MSYS2 package and as a MinGW-w64 package (the >> "native" counterpart.) For the later, the recipe and patches are here: >> >> https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-bison > > In a hidden place, I see. Why hidden? It is stored along the rest of the MinGW-w64 packages and it is listed on `pacman -Ss bison' as well. [snip] >> Gawk as a MSYS2 package: > > Since Gawk builds with MinGW out of the box, even without the need to > run the configure script, not having a MinGW64 port for it is strange, > to say the least. > >> Same for flex. > > Without Flex, you don't have a complete development environment, so > again, not offering a MinGW Flex sounds like an omission that should > be fixed. Except for building a few third party packages (i.e. GCC which doesn't require them anymore for building the released tarballs) I never use flex/bison myself nor perceived that its usage is ubiquitous. YMMV. >> Please note that the project is a just months old and there is no >> central authority for ensuring that the submitted build recipes are >> sound. If it builds, it is accepted and then they wait for bug reports. >> If the package is too broken, it is retracted until someone fixes it. > > My point is that the amount of hype this project generates among its > fans is not entirely justified by the evident omissions and (IMO) > insufficient QA. If there are omissions is because so far nobody cared enough about the omitted packages and the insufficient QA is the consequence of an heterogeneous community and the impossibility for the maintainers to check that every package works as it should. These are ailments that improve with age as the community grows and matures. I remember the experience of setting up the environment for building Emacs on Windows. It was so painful that I used the same setup and libraries for many years, frozen on a virtual machine. Now, starting from scratch, I can obtain all the necessary and optional (*) requirements for building Emacs on a few minutes. Everything up to date and on a working condition, as far as my experience goes. Same for my C++ development enviroment (**). So the hype is justified, IMO. * IIRC there is a problem witn the xpm package. It is installed but Emacs' configure script doesn't detect it. Maybe the package is incomplete or installed on the wrong place. ** Except Emacs itself, which I wouldn't use anyways because I have local patches.