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#45821: Emacs UDP support on Windows Date: Mon, 02 Jan 2023 19:01:23 +0200 Message-ID: <83lemk27mk.fsf@gnu.org> References: <87turmhvub.fsf@gnus.org> <87ee1992d5.fsf@gmail.com> <87a6bx8olp.fsf@gmail.com> <835ydp2l7p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38986"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rpluim@gmail.com, 45821@debbugs.gnu.org To: Alex Matei Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 02 18:02:45 2023 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 1pCOCz-0009tA-9X for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 02 Jan 2023 18:02:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pCOCW-0004Le-49; Mon, 02 Jan 2023 12:02:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pCOCJ-00049Y-5b for bug-gnu-emacs@gnu.org; Mon, 02 Jan 2023 12:02:06 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pCOCI-0006KP-Lo for bug-gnu-emacs@gnu.org; Mon, 02 Jan 2023 12:02:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pCOCI-0000qO-2I for bug-gnu-emacs@gnu.org; Mon, 02 Jan 2023 12:02:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 02 Jan 2023 17:02:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45821 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 45821-submit@debbugs.gnu.org id=B45821.16726788873178 (code B ref 45821); Mon, 02 Jan 2023 17:02:02 +0000 Original-Received: (at 45821) by debbugs.gnu.org; 2 Jan 2023 17:01:27 +0000 Original-Received: from localhost ([127.0.0.1]:43906 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pCOBj-0000pB-56 for submit@debbugs.gnu.org; Mon, 02 Jan 2023 12:01:27 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60104) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pCOBh-0000oy-IA for 45821@debbugs.gnu.org; Mon, 02 Jan 2023 12:01:25 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pCOBc-00065M-6n; Mon, 02 Jan 2023 12:01:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=51FQIWALxX8fCfvsBKVQBAG/mIA6xPmmkeTmG2Chyfc=; b=girYX0bhAYow2ow2VWpx k3mOk2iLg8u2BXKN0CGJGY9E52saudTg+wcfArjOfgY3h1vaGhlNsHBE1pKWl4/PuPqaB7KUl+Gu/ FMpo0MQR3Sr9CDUULSC/NgKQAg5gVkWegFxDd13U/p4KsVATiecRMlMmTWnDJ2Wr67dUxp83J2Yfc 25FTxX+PBg/c1DNrjYZtf4bVA8PGw6Z6FEJH5gRJwaUjRgXY7wOw/zmXtbkaAJxaq2M1uMxpNOG5Y V55pXb4nUqKgmbnrJV5ioiM/Lwg8WDUcfH6+xJzQ2shF8UMRnVsZbFCURvR/MkpyN2Znqy7orsSn6 gK7YEZHRSK9bFA==; Original-Received: from [87.69.77.57] (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 1pCOBb-0006Us-MP; Mon, 02 Jan 2023 12:01:20 -0500 In-Reply-To: (message from Alex Matei on Mon, 2 Jan 2023 15:59:23 +0000) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:252348 Archived-At: > From: Alex Matei > CC: "rpluim@gmail.com" , "45821@debbugs.gnu.org" > <45821@debbugs.gnu.org> > Date: Mon, 2 Jan 2023 15:59:23 +0000 > > I like the nt/INSTALL.W64 file but somehow I found Step-by-step instructions to build Emacs for Windows 64 > bit with MSYS2 and MinGW-w64. Now `native-comp` supported. (github.com) more useful. I don't see there anything that we don't have. I do see a lot of stuff unrelated to building Emacs per se, something that just sounds like personal preferences of whoever wrote that post. > I was wondering > if we are allowed to add links to such gists / blogposts? (I understand that they can become obsolete at > some point, but a section like useful references would be nice) I don't think we should be responsible for someone else's posts. It is better to maintain our instructions to be accurate and with all the necessary details. > * If you look at the gist, it gives a more detailed step-by-step approach around setting MYSYS > * I am not 100% that the packages listed in nt/INSTALL.W64 are sufficient, on a fresh installation of MYSYS > -> I will have to check if there are any gaps Please do tell if you find anything missing or incorrect, and we will fix those deficiencies. > My problem with patching: > > * I didn’t know how to consume @Robert Pluim’s change ☹ I had to read a blog post (Working with Git and > patches in Emacs (ane.iki.fi)) on how git am works and that I can manually save the text from his change > to a file and then use that file to apply changes to my Emacs branch… > * What made it weird in the beginning was that I only had the information from #45821 - 28.0.50; Add UDP > support for Emacs on Windows - GNU bug report logs and most of the apply patch examples refer to you > having received an email with the patches as an attachment and then performing actions on it (in my > case, I didn’t have any email) > > > > For me, having a good walkthrough with examples is really useful and that’s why I am asking if we can > include links to such blogposts: > > * I benefited from a walkthrough on MYSYS installation + emacs building > * I benefited from a walkthrough on email patches > > I am hoping others could find this useful too when they first take a look at building Emacs themselves. This is just the steep learning curve, something that each one of us has to go through just once. It is impossible to have all this information in our installation instructions.