From: Robert Pluim <rpluim@gmail.com>
To: Alex Matei <matei.alexandru@live.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"45821@debbugs.gnu.org" <45821@debbugs.gnu.org>
Subject: bug#45821: Emacs UDP support on Windows
Date: Wed, 04 Jan 2023 10:32:19 +0100 [thread overview]
Message-ID: <878riik5lo.fsf@gmail.com> (raw)
In-Reply-To: <DB9PR02MB73378761CE4485E2784CE28585F49@DB9PR02MB7337.eurprd02.prod.outlook.com> (Alex Matei's message of "Tue, 3 Jan 2023 20:22:58 +0000")
>>>>> On Tue, 3 Jan 2023 20:22:58 +0000, Alex Matei <matei.alexandru@live.com> said:
Alex> Here are the 2 patches that can be applied, in order:
Alex> * 0001 -> the original patch from the email thread, that I used
Alex> * 0002 -> the additions that I made locally
Alex> Note: TLS mostly works, but I’ve observed some weird behavior in the process list for EWW
Alex> * It almost feels like sometimes we hit snags in navigating to some HTTPS endpoints because the existing connections never get closes
Alex> * I think we need to make some investigations/ changes to the socket lifetime / close behavior to fix the class of issues we are seeing in EWW, where sometimes the page load hangs, and yes, you can load it after a couple of refreshes (‘g’ key binding) but then you see something really interesting if you take a look at the process list
Alex> * You will notice that some of the connection never
Alex> close (properly) and hang around!
Hmm, Iʼve not noticed anything like that, but I donʼt use Emacs on
windows regularly. Is this emacs-28 or emacs-29 or master? (I ask,
since emacs-29 did some reworking of some of the TLS code).
Alex> * If anyone has any good pointers of what are good
Alex> functions to look at, please let me know; I will take a
Alex> look at this later in the day, and navigate the reader
Alex> thread and everything around it..
Alex> [cid:image003.png@01D91F6E.1C5C1280]
Alex> p.s. I didn’t find an obvious way of merging the two patches in magit, hence the 2 individual patches 😊 – I guess I can just rebase the commits into one..
Either rebase, or if youʼve 'git apply' the changes from the second
patch you can add them in to the first patch using 'c e' (commit
extend). Of course you then need to to 'c w' to fix the commit
message, so rebase is the way to do it in one step.
Robert
--
next prev parent reply other threads:[~2023-01-04 9:32 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 18:08 bug#45821: 28.0.50; Add UDP support for Emacs on Windows Lars Ingebrigtsen
2021-01-12 18:38 ` Eli Zaretskii
2021-01-13 9:17 ` Robert Pluim
2021-07-20 15:41 ` Lars Ingebrigtsen
2021-09-27 16:47 ` Robert Pluim
2021-09-27 17:45 ` Robert Pluim
2021-10-04 17:47 ` Robert Pluim
2021-10-04 17:59 ` Eli Zaretskii
2021-09-27 18:45 ` Eli Zaretskii
2021-10-11 11:56 ` Stefan Kangas
2021-10-11 12:06 ` Robert Pluim
2022-05-03 18:56 ` bug#45821: Emacs UDP support " Alex Matei
2022-05-04 7:35 ` Robert Pluim
2022-05-04 11:50 ` Alex Matei
2022-05-04 12:32 ` Robert Pluim
2022-09-11 11:26 ` bug#45821: 28.0.50; Add UDP support for Emacs " Lars Ingebrigtsen
2023-01-01 23:01 ` bug#45821: Emacs UDP support " Alex Matei
2023-01-02 0:47 ` Alex Matei
2023-01-02 10:22 ` Robert Pluim
2023-01-02 12:41 ` Eli Zaretskii
2023-01-02 13:29 ` Robert Pluim
2023-01-02 13:38 ` Eli Zaretskii
2023-01-02 22:56 ` Alex Matei
2023-01-03 8:51 ` Robert Pluim
2023-01-03 20:22 ` Alex Matei
2023-01-04 9:32 ` Robert Pluim [this message]
2023-01-04 10:15 ` Alex Matei
2023-01-04 10:50 ` Robert Pluim
2023-01-05 19:06 ` Alex Matei
2023-01-05 20:53 ` Alex Matei
2023-01-05 21:01 ` Alex Matei
2023-01-06 7:56 ` Robert Pluim
2023-01-07 11:24 ` Robert Pluim
2023-01-08 15:31 ` Alex Matei
2023-01-08 15:42 ` Robert Pluim
2023-01-08 15:43 ` Alex Matei
2023-01-08 16:00 ` Alex Matei
2023-01-08 16:08 ` Eli Zaretskii
2023-01-08 16:10 ` Alex Matei
2023-01-10 12:41 ` Alex Matei
2023-01-10 13:56 ` Robert Pluim
2023-01-11 13:09 ` Alex Matei
2023-01-11 13:23 ` Alex Matei
2023-01-12 9:22 ` Robert Pluim
2023-01-12 10:08 ` Eli Zaretskii
2023-01-12 10:14 ` Alex Matei
2023-01-12 10:24 ` Robert Pluim
2023-01-12 10:46 ` Eli Zaretskii
2023-01-12 10:57 ` Alex Matei
2023-01-12 10:59 ` Alex Matei
2023-01-12 11:03 ` Eli Zaretskii
2023-01-12 11:12 ` Alex Matei
2023-01-12 11:21 ` Robert Pluim
2023-01-12 11:23 ` Alex Matei
2023-01-12 11:18 ` Robert Pluim
2023-01-12 12:25 ` Eli Zaretskii
2023-01-12 13:28 ` Robert Pluim
2023-01-28 21:17 ` Alex Matei
2023-01-29 6:13 ` Eli Zaretskii
2023-01-02 10:10 ` Robert Pluim
2023-01-02 16:01 ` Alex Matei
2023-01-03 13:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 19:18 ` Alex Matei
2023-01-02 12:07 ` Eli Zaretskii
2023-01-02 15:59 ` Alex Matei
2023-01-02 17:01 ` Eli Zaretskii
2023-01-02 17:57 ` Alex Matei
2023-01-02 19:07 ` Alex Matei
2023-01-02 19:22 ` Eli Zaretskii
2023-01-02 19:24 ` Alex Matei
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=878riik5lo.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=45821@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=matei.alexandru@live.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).