all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62194@debbugs.gnu.org, miha@kamnitnik.top
Subject: bug#62194: 30.0.50; Two Eglot-over-Tramp tests are failing on master, passing on emacs-29
Date: Thu, 16 Mar 2023 13:02:01 +0100	[thread overview]
Message-ID: <87ttykj45i.fsf@gmx.de> (raw)
In-Reply-To: <CALDnm50YjHKg+TDJ3yxmnGyrEaZAxqEqSgihzLEbGfKFCo97nQ@mail.gmail.com> ("João Távora"'s message of "Wed, 15 Mar 2023 20:45:47 +0000")

João Távora <joaotavora@gmail.com> writes:

Hi,

> I'm "against" this too, but hard facts here trump arguments and opinion.
> This is exactly what fixes the ControlMaster hang, that's well understood,
> and is really intended. It brings about some other failures but I've just
> confirmed that if you put
>
>    (while (accept-process-output p 0 nil t))
>
> then all's well.
>
> Of course, it's only _one_ of the ways to fix the problem.  If you have another
> more elegant one, but I don't know if signals is a great one.  I'd guess
> SIGWINCH to be somewhat limited in platform support, right?

I'm also against using SIGWINCH at this point. It isn't portable, and it
isn't even known whether it is needed always. The proposed patch wraps
it by

--8<---------------cut here---------------start------------->8---
(when (and (not result) (process-get proc 'shared-socket))
--8<---------------cut here---------------end--------------->8---

But the reason why result is nil could be simply the case that the
remote side hasn't something to tell yet, and we need to wait.

And this would complicate the scenario further. We have already a very
fragile tramp-accept-process-output, which has changed again and again
ove the last 20 years. I *really* would like to see a simple and robust
implementation.

My attempt with the additional process property `shared-socket' has
failed, and I've reverted it.

Pushed to master. The Eglot Tramp tests pass now, so I recommend to
close this bug.

> João

Best regards, Michael.





  reply	other threads:[~2023-03-16 12:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 23:08 bug#62194: 30.0.50; Two Eglot-over-Tramp tests are failing on master, passing on emacs-29 João Távora
2023-03-15  9:40 ` Michael Albinus
2023-03-15 11:45   ` Michael Albinus
2023-03-15 20:24     ` João Távora
2023-03-15 20:36     ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-15 20:45       ` João Távora
2023-03-16 12:02         ` Michael Albinus [this message]
2023-03-16 12:20           ` João Távora
2023-03-16 14:57             ` Michael Albinus
2023-03-16 15:12               ` João Távora
2023-03-16 17:35                 ` Michael Albinus
2023-03-16 17:59                   ` João Távora
2023-03-16 21:18                     ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 21:57                       ` João Távora
2023-03-16 23:38                         ` João Távora
2023-03-17 16:45                         ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 16:47                           ` Eli Zaretskii
2023-03-17 17:22                             ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 17:22                               ` Eli Zaretskii
2023-03-17 10:44                     ` Michael Albinus
2023-03-17 11:19                       ` João Távora
2023-03-18  9:38                         ` Michael Albinus
2023-03-18 11:29                           ` João Távora
2023-03-18 12:23                             ` Michael Albinus
2023-03-18 12:33                               ` João Távora
2023-03-19 12:19                           ` Michael Albinus
2023-03-15 20:16   ` João Távora
2023-03-16 15:02     ` Michael Albinus
2023-03-28 10:51       ` Michael Albinus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttykj45i.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=62194@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=miha@kamnitnik.top \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.