From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#61350: Eglot over Tramp freezes with large project Date: Thu, 16 Mar 2023 13:28:07 +0000 Message-ID: <87lejw3jx4.fsf@gmail.com> References: <87y1ootw2t.fsf@gmail.com> <87mt4otyy1.fsf@gmx.de> <87pm9fk6ht.fsf@gmx.de> <87mt4jzf8q.fsf@gmail.com> <87fsabh2z2.fsf@gmx.de> <87edpvxu7w.fsf@gmail.com> <87bkkzgyb8.fsf@gmx.de> <87lek2x09t.fsf@gmail.com> <875yb646d1.fsf@gmx.de> <87fsa7mw9x.fsf@gmx.de> <87fsa7l6o6.fsf@gmx.de> <87a60fl4p7.fsf@gmx.de> <878rfx6bqe.fsf@gmail.com> <8e031bc5-7ac3-620e-b1ca-aaa872b3cdde@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16737"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Thomas Koch , Michael Albinus , Stefan Monnier , 61350@debbugs.gnu.org To: Jim Porter Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 16 14:27:18 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 1pcndW-0004BA-Fc for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 16 Mar 2023 14:27:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pcndJ-0003H7-AG; Thu, 16 Mar 2023 09:27:05 -0400 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 1pcndG-0003Fz-S1 for bug-gnu-emacs@gnu.org; Thu, 16 Mar 2023 09:27:02 -0400 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 1pcndG-0004g4-Io for bug-gnu-emacs@gnu.org; Thu, 16 Mar 2023 09:27:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pcndG-00082w-FW for bug-gnu-emacs@gnu.org; Thu, 16 Mar 2023 09:27:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 16 Mar 2023 13:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61350 X-GNU-PR-Package: emacs Original-Received: via spool by 61350-submit@debbugs.gnu.org id=B61350.167897317730854 (code B ref 61350); Thu, 16 Mar 2023 13:27:02 +0000 Original-Received: (at 61350) by debbugs.gnu.org; 16 Mar 2023 13:26:17 +0000 Original-Received: from localhost ([127.0.0.1]:41480 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pcncX-00081Z-B3 for submit@debbugs.gnu.org; Thu, 16 Mar 2023 09:26:17 -0400 Original-Received: from mail-wr1-f43.google.com ([209.85.221.43]:38752) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pcncU-00081J-Hi for 61350@debbugs.gnu.org; Thu, 16 Mar 2023 09:26:15 -0400 Original-Received: by mail-wr1-f43.google.com with SMTP id o7so1537826wrg.5 for <61350@debbugs.gnu.org>; Thu, 16 Mar 2023 06:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678973168; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=x6bUNIbQYh44qzAIb5TBCu0Gt7HlTmNY2lc2LnScHgg=; b=KBpQnaSF3ByEzR/5FzItwBsAruzdjjAAzMwWtywGJSfnyKpZdB/YE97zJUfLz25mSM WfX+EE9XhbCIUmiQL7HndMCgnyGbFO9GTS3KhKjfg+ZM0zMupOwitSy1gdXfjDNAWrS5 4LNCRfmhTgYlZ9/YqviLiRZlAxt4wwyCiZSV5OhrplIvrj+aHrKOfYZo9ZGoRuXN5ce0 CNpF7HaTgSI26+RqY6RgWGKNUprz3Hoe6zVNlCkwpL6m7n94e0Olsrz0Ok66ZHNpz0wL qpIEI/O2qJsfEzWc9cNx4QBxkjfSi3IoxoJThkQSYmK4ZiRruedvUo+8KPOIM/TbuHdZ 3O9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678973168; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=x6bUNIbQYh44qzAIb5TBCu0Gt7HlTmNY2lc2LnScHgg=; b=71j0TARCx4bMO0+MA2qUVGxvANjpBlirCmg2tWRYZobpKd0yzMR8rHNv3c2Aapz1GY 72w/Yx61ZNQdLPlmp2TwBM2iKjwJgkJUoKt8DTRMwWZBy4lljdulH/in2K2TLWJZfgPh k7Egk4k/uudhjQRDSIniRUTfnOeHKLIVpK8JWxcciaR7NhQbP+pVzjYBY+kuVCJaCtoq m8x3Lw1vUwr3B2uQDn6Pz2ybUQk5z2usnho+EFTFj+kWsN9QeYrDJ5IgclXF4RcGpwXH 7h/SzgWdF5iJI+Yw+itr/Nb9ZuXE4TCa/lV0dS/FSz6+DRQDMXMga/4SgAIKryofSfT8 GJZw== X-Gm-Message-State: AO0yUKXP2fV/L64SpzM5dY7JS0Fu62tVHA9hvwS+FCGL/v+cfbaUfvnn wMHly4gwy21LwM5hcQ7/TDcSJLLdsbI= X-Google-Smtp-Source: AK7set8LOdTiWzSmE2L46F0TznAq5DGXXOAe0hWZm5rF1JDYDpzhAcqNtvKWlXYHqx/FtfrM0gZSuw== X-Received: by 2002:adf:ed04:0:b0:2cf:f061:4910 with SMTP id a4-20020adfed04000000b002cff0614910mr4495694wro.42.1678973168214; Thu, 16 Mar 2023 06:26:08 -0700 (PDT) Original-Received: from krug (87-196-72-142.net.novis.pt. [87.196.72.142]) by smtp.gmail.com with ESMTPSA id a8-20020a5d5088000000b002c7107ce17fsm7343829wrt.3.2023.03.16.06.26.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Mar 2023 06:26:07 -0700 (PDT) In-Reply-To: <8e031bc5-7ac3-620e-b1ca-aaa872b3cdde@gmail.com> (Jim Porter's message of "Wed, 15 Mar 2023 23:24:32 -0700") 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:258015 Archived-At: Jim Porter writes: > On 3/15/2023 2:49 PM, Jo=C3=A3o T=C3=A1vora wrote: >> SLY, jsonrpc.el, and other code is synchronous as well (the completion >> API is synch, as you well know). `accept-p-o` + a filter that invokes >> a closure that throws out of the loop is a great way to do this. >> See jsonrpc-request, for example. No JUST-THIS-ONE, and has >> been working fine in many forms since Emacs 24.3 AFAIK. > > Assuming I understand the context here correctly, this sort of thing > is part of why Chris Wellons' emacs-aio package uses 'run-at-time' for > handling resolved promises[1]: There's a relation, but it's not a direct relation. emacs-aio is a promise/future/cps library which uses timers. I was describing this design pattern for _synch_ requests over Emacs's asynchronous processes (set-process-filter proc (lambda (proc output) (internal-default-process-filter proc output) (when (and (process-get proc 'busy) (buffer-live-p (process-buff= er proc))) (with-current-buffer (process-buffer proc) (when (search-forward ", DAVE.\n") (unwind-protect (throw 'done (buffer-substring (point-min)= (point))) (process-put proc 'busy nil) (delete-region (point-min) (point)))))))) =20=20=20=20 =20=20=20=20 (setq answer-from-proc (catch 'done (process-put proc 'busy t) (process-send-string proc "OPEN THE POD BAY DOO= RS\n") (while (accept-process-output)))) This is very simplified (and untested), but that's the gist. You can then add cancellation, timeouts, etc. Also normally (in SLY and JSONRPC) instead of a single flag 'busy, you look up a table of pending requests This pattern has worked very well for me, for a long time, 10+ years. SLIME used this pattern back in 2000's, there where I saw it (and distilled it). It's similar to what "await" does other languages. >> If the result is ready call the callback in the next event loop turn >> using run-at-time. This is important because it keeps all the >> asynchronous components isolated from one another. They won=E2=80=99t see >> each others=E2=80=99 frames on the call stack, nor frames from aio. This= is >> so important that the Promises/A+ specification is explicit about >> it. > While a solution specific to the problem in this bug likely doesn't > require an entire asynchrony framework, if we get one into Emacs, it > should definitely support this case. Sure, I'd be happy with just using the stuff that's been in Emacs for ages. Jo=C3=A3o