From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Adam Ibrahim Newsgroups: gmane.emacs.bugs Subject: bug#63629: Fwd: bug#63629: 28.3; Emacsclient exits with no error message and breaks terminal when opening a file without permissions Date: Wed, 24 May 2023 08:08:13 -0400 Message-ID: References: <83a5xxr1db.fsf@gnu.org> <83v8gkpk6g.fsf@gnu.org> <83lehengr4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000009538e205fc6f5ce2" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34423"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63629@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 24 14:09:21 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 1q1nIu-0008oD-Or for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 24 May 2023 14:09:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q1nIf-0006yo-EL; Wed, 24 May 2023 08:09: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 1q1nIc-0006yY-Ld for bug-gnu-emacs@gnu.org; Wed, 24 May 2023 08:09:03 -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 1q1nIc-0005Sj-4I for bug-gnu-emacs@gnu.org; Wed, 24 May 2023 08:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q1nIb-0002fd-W1 for bug-gnu-emacs@gnu.org; Wed, 24 May 2023 08:09:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Adam Ibrahim Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 24 May 2023 12:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63629 X-GNU-PR-Package: emacs Original-Received: via spool by 63629-submit@debbugs.gnu.org id=B63629.168493011810235 (code B ref 63629); Wed, 24 May 2023 12:09:01 +0000 Original-Received: (at 63629) by debbugs.gnu.org; 24 May 2023 12:08:38 +0000 Original-Received: from localhost ([127.0.0.1]:42429 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q1nID-0002f1-SN for submit@debbugs.gnu.org; Wed, 24 May 2023 08:08:38 -0400 Original-Received: from mail-ej1-f53.google.com ([209.85.218.53]:62598) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q1nIA-0002em-L6 for 63629@debbugs.gnu.org; Wed, 24 May 2023 08:08:35 -0400 Original-Received: by mail-ej1-f53.google.com with SMTP id a640c23a62f3a-95fde138693so1222935466b.0 for <63629@debbugs.gnu.org>; Wed, 24 May 2023 05:08:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684930108; x=1687522108; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3ltRtTGyn6X96p8IgJGF62ZEb2uStwAMuDOkV6L0s5E=; b=BK3IBnqlSpvl6t3gZ0ywWOTNCNYBXHYVlrhn6MXOl3+8wkTeArgp3kim5u8qS6nz2q REKwtW+Hn7GbQkQk/h7dyg7CoSvplLh4y/MoKQoTuBz/Lcvc9mjdorilFXmAU7h1fEcG aviwS5Kr2ZOUHE3By+N7lkyv7Cdf8ezBhxftHqkaUo1jUhN06kbAgPUhA2ZXp5mNT7+Y r/B9YDHJchq4rVsHjk66/dnvtzlLAtw5JDcrn8yPHeMGW44x2e2gMPw1n0UEl7BMwGpG vyo5Q/40yIXOYUF050Cj8b09WR/0mDCVJ2hIlv8mzO3AhRakPcuPWoMV9oWob5vSddjo 0/Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684930108; x=1687522108; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3ltRtTGyn6X96p8IgJGF62ZEb2uStwAMuDOkV6L0s5E=; b=MV9ZWcwN6sxa5DkOWBqY9iqjIgt/eMqJkY+CN7yTbCfggkD+tb9adSTpqwtIK7Na4B RdnN6gF0zZFvyv5tAOvyz3r07HgkBNgQCotbDNcxk96YEXD79y3vwHmRM3baj4DmXDm4 nVXVlsXpBaZaWGAZ8FL+OoQT0pBhT3pI1j/0T3Zm7OfHAGesbrQF1L48H0mDkACduSfS 1MxbLZhaLI3X4ahLpESqdL7MJI4uAyNASOHw4CoI7JEN1v5ZsMyU2CrukBnN7i/9B3Xk XnngNk1a1hmxKyf9gb7lrJDAPZdoHo6R/i5sxGrMsS00eUGPGwTZREiAmVIjBZ9I9CXH eq/g== X-Gm-Message-State: AC+VfDzX14ibuBtI98nE4pMP8wsI8hwTYSsnpwMVsMIMHhQCPZayv3Rm i/wsNLtEgxFFvb5hiahUuYUavq2lY3iEBn+LU1E= X-Google-Smtp-Source: ACHHUZ4bvPwWX1hV0PcdqSmICvQ/aPp+J2WapPOaOxiR3FzYDjy124+P2gmMjzFOwqVUNbAngSScKyvLjPps5JSznDg= X-Received: by 2002:a17:907:8a20:b0:953:834d:899b with SMTP id sc32-20020a1709078a2000b00953834d899bmr16274574ejc.29.1684930108404; Wed, 24 May 2023 05:08:28 -0700 (PDT) In-Reply-To: <83lehengr4.fsf@gnu.org> 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:262291 Archived-At: --0000000000009538e205fc6f5ce2 Content-Type: text/plain; charset="UTF-8" Makes sense. Thanks. On Wed, May 24, 2023, 06:52 Eli Zaretskii wrote: > > From: Adam Ibrahim > > Date: Tue, 23 May 2023 16:30:14 -0400 > > Cc: 63629@debbugs.gnu.org > > > > I ran the following commands on my phone in termux and in Kitty on my PC > 10 times each and record > > the results. I did it multiple times because the results seem random. > > > > ./src/emacs --fg-daemon -Q > > ./lib-src/emacsclient path/to/no-perms # in a separate terminal, 10 > times > > > > Phone + Termux: 9 out of 10 times, I got the expected results where the > terminal was not broken and I > > saw an error message. on the 10th time there was some weird behavior, > but I haven't been able to > > reproduce it and I don't remember what happened. > > > > PC + Kitty: there were no crashes meaning the terminal wasn't broken > anymore. but 6 out of 10 times > > the error message didn't print. sometimes all I saw was "waiting for > emacs..." and some other times > > all I saw was "...". the other four times was expected behavior colon > the error message printed and the > > terminal wasn't broken. > > > > Note: I have a slightly different environment on my phone compared to > the first time. when I first > > reported the bug I was using the emacs and emacsclient programs located > on my phone. this time I > > used the modified emacs and emacsclient from my desktop over SSH. I > don't know if that changed the > > results. But the bug with unmodified emacs happens just the same over > SSH as with emacs on my > > phone. > > If the only problem you see after the change is that you don't always > see the error message, then it's expected. emacsclient outputs the > error message to stderr, and when there's a client frame on that > display, it is impossible to make sure the error message will always > be shown, before it is erased when the terminal is closed by the > server Emacs process. So the only thing the fix tries to guarantee is > that you will be able to use the terminal after emacsclient exits. If > this happens in all the configurations you tried, then the goal of the > change is achieved, and I don't think we can do much more. > --0000000000009538e205fc6f5ce2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Makes sense. Thanks.

On Wed, May 24, 202= 3, 06:52 Eli Zaretskii <eliz@gnu.org> wrote:
> From: Adam Ibrahim <ibrahimadam193@g= mail.com>
> Date: Tue, 23 May 2023 16:30:14 -0400
> Cc: 63629@debbugs.gnu.org
>
> I ran the following commands on my phone in termux and in Kitty on my = PC 10 times each and record
> the results. I did it multiple times because the results seem random.<= br> >
>=C2=A0 ./src/emacs --fg-daemon -Q
>=C2=A0 ./lib-src/emacsclient path/to/no-perms # in a separate terminal,= 10 times
>
> Phone + Termux: 9 out of 10 times, I got the expected results where th= e terminal was not broken and I
> saw an error message. on the 10th time there was some weird behavior, = but I haven't been able to
> reproduce it and I don't remember what happened.
>
> PC + Kitty: there were no crashes meaning the terminal wasn't brok= en anymore. but 6 out of 10 times
> the error message didn't print. sometimes all I saw was "wait= ing for emacs..." and some other times
> all I saw was "...". the other four times was expected behav= ior colon the error message printed and the
> terminal wasn't broken.
>
> Note: I have a slightly different environment on my phone compared to = the first time. when I first
> reported the bug I was using the emacs and emacsclient programs locate= d on my phone. this time I
> used the modified emacs and emacsclient from my desktop over SSH. I do= n't know if that changed the
> results. But the bug with unmodified emacs happens just the same over = SSH as with emacs on my
> phone.

If the only problem you see after the change is that you don't always see the error message, then it's expected.=C2=A0 emacsclient outputs th= e
error message to stderr, and when there's a client frame on that
display, it is impossible to make sure the error message will always
be shown, before it is erased when the terminal is closed by the
server Emacs process.=C2=A0 So the only thing the fix tries to guarantee is=
that you will be able to use the terminal after emacsclient exits.=C2=A0 If=
this happens in all the configurations you tried, then the goal of the
change is achieved, and I don't think we can do much more.
--0000000000009538e205fc6f5ce2--