Stefan Kangas <stefankangas@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Received: (at 76772) by debbugs.gnu.org; 9 Mar 2025 10:36:04 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sun Mar 09 06:36:04 2025 Received: from localhost ([127.0.0.1]:58540 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1trE0p-0002O8-JO for submit <at> debbugs.gnu.org; Sun, 09 Mar 2025 06:36:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57870) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1trE0n-0002Nc-B8 for 76772 <at> debbugs.gnu.org; Sun, 09 Mar 2025 06:36:01 -0400 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 <eliz@HIDDEN>) id 1trE0h-0004aB-Gv; Sun, 09 Mar 2025 06:35:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=9N9XtqIlhf1zbSCEmgimBYQl818A7m2luDQOcAyMFrI=; b=Mn9xc1TIVi/w cwtyVVB2gqOfDwAUiK/3m/VG0XtoWWOEOyCZckLhFjBl74Y+EBq5bOBMj6WP1ssxYmXhr8MfvXeZe 8M2hcgqajAjFbOK+iUxRZCiJjNKHllCNw/ggrVojzM/bbf0/Z5dms4vwB7ODjvgtWmo5sPGm2eQAq TfNSVZIEZW753AZyB/ot88M+pGUwaKsImZNQ45cqZER8wqUwQE/1G7gxPIwuzE/8rauPnbW3t4DSI RUVfnUZw600WwWBvsnnHcwuHV9dmbMpFwPGIqG7UygsvJAAKPSNP7n/8CZV01hD4bwJdcj6KQrVHO kvfdeQKhaAlUFDCsyFM+ag==; Date: Sun, 09 Mar 2025 12:35:51 +0200 Message-Id: <86pliqfq48.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Artiom Balan <artiombalan331@HIDDEN> In-Reply-To: <CAA8c5q92We1jajUURagmQp8u6XOu_Svxb6P_QhgD46u5di7Tyg@HIDDEN> (message from Artiom Balan on Sat, 8 Mar 2025 10:53:38 +0200) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> <86msdxl2gr.fsf@HIDDEN> <CADwFkmkLAy08du3yeOj9k-320gx5RbSjfKpzCbVDtA9HOd393Q@HIDDEN> <86frjpkz2b.fsf@HIDDEN> <CAA8c5q92We1jajUURagmQp8u6XOu_Svxb6P_QhgD46u5di7Tyg@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, stefankangas@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Artiom Balan <artiombalan331@HIDDEN> > Date: Sat, 8 Mar 2025 10:53:38 +0200 > Cc: Stefan Kangas <stefankangas@HIDDEN>, 76772 <at> debbugs.gnu.org > > > If we want the first client connection to show the important messages > > from the startup phase of the daemon, then warnings is not the only > > thing, and not even the most important thing, that needs to be shown. > > Good point. To generalize, is the only difference between running a regular emacs instance and running an > emacs daemon the fact that the user doesn't see some things? Like, the behavior is the same, but some > things are "shown" in the daemon, which the user can't see. If so, how can we know which are all of these > things? You added errors and echo-area messages. Are there any others? When some code in Emacs shows a message, we don't usually make sure the message is displayed. We call the usual functions like 'message' or pop-to-buffer, and if the selected frame is not shown on display, we leave it at that. So in general, the daemon doesn't show anything, with the exception of critical problems that prevent it from starting (those are written to stderr of the controlling terminal at the moment of daemon startup). > Would the ideal solution be to show in the first emacsclient everything that the regular instance would have > shown? Or maybe a hack that displays the warnings (and errors?) in the first emacsclient would suffice? I think we should have some way of deferring messages until some frame is visible on display. > BTW, how can i get emacs to show errors after startup? I tried to add a `(error "message")` to my init.el, and > starting emacs would show it as a warning: > "Warning (initialization): An error occurred while loading ..." Signaling an error during startup prevents Emacs from starting, so the user will not see any messages at all, which is not useful. Therefore, Emacs handles errors during startup in a special way. If you want Emacs to enter a debugger due to problem in startup and/or init files, use the --debug-init command-line option to start Emacs.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 8 Mar 2025 08:54:00 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Mar 08 03:54:00 2025 Received: from localhost ([127.0.0.1]:52757 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqpwV-0007hZ-Gz for submit <at> debbugs.gnu.org; Sat, 08 Mar 2025 03:54:00 -0500 Received: from mail-wr1-x434.google.com ([2a00:1450:4864:20::434]:51620) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <artiombalan331@HIDDEN>) id 1tqpwT-0007hG-0W for 76772 <at> debbugs.gnu.org; Sat, 08 Mar 2025 03:53:57 -0500 Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-388cae9eb9fso1240236f8f.3 for <76772 <at> debbugs.gnu.org>; Sat, 08 Mar 2025 00:53:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741424031; x=1742028831; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Gk/s+gVPkQ2D/PAGc6mBLJEk7jmq5Rep7TVgWafhEwE=; b=S+vynH51aumEaK/43XTSNZEvH/DXTGbv5sabb0nzsDX0Pu2xORMsf5KgL0CYtuMjEg ySymVzZcKuiUZ5LOtpNjCfcfjsn3/sBn/tpEuDgOYchNY+1DljDfLvN+OIEfb7VC7ohL R1EwA3clp+5CL1O1GkY6tOl7kBGk2UeAIRg7XpHdGvM/FBv746/5f54WLlLS2QPk+a+a QTLlYiaAkQAeURmN2kCspNxAW7KYnjaPcecvXQq+5hgQI2ebwA8PIZQ9hOabMLiWDgne iYitch4Z+r29vmQ6AoQWWZTgMVuE9b/+pM6p/oYUCnYbSEtEsuJqYxSoWBeHYV32d9vA IS9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741424031; x=1742028831; 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=Gk/s+gVPkQ2D/PAGc6mBLJEk7jmq5Rep7TVgWafhEwE=; b=E6jDm57M0IXPI0KR/A0xg8Use6zCR3VRdmeXxDqrPJ63jcoUN3Vwg1LKeumAhG7f8M 2VzDG6vv65mw5WVwR//GYy0khAd20syCLH123C6n9/GSgd0L9/axwC4QVNeGadVNVu/I QXh08UDlmJP3YexyREgeZtbmgaXdlK+8VYKYYYTqSlcgvBZ0tybR9lYv0i/PXpGe4Cwd 7E/R3QDhWXCAB7/dkVNrkTbJWoqVNAVC38w3SjdnP42t3ggigGZJp7IpQkUzGnWVaUDJ 7HYulrdKuRtsD9kD2JE+HvSZ9xRcRMUrk6LpgsAPhxUxShcMK8gfo9TP2QPxRSKj4LTI wJJQ== X-Forwarded-Encrypted: i=1; AJvYcCWwhf82oV0Ri+S2+KRWHht/V/I9rgqxX6Emp8gxj7KHZbp5QmbQVPAUlJOsDrB0Kfugvaqo0g==@debbugs.gnu.org X-Gm-Message-State: AOJu0YzCxguHfn28lReF92UFxsiJOnrF6DQUK9To7OggSA4H+GlT1xJe dtnQKLKqdLMg2Bo1tfNbhoxTQSY12rVDne2lyR7LriEgSGUinoggxeEpXkDPAKZJfcRRuv2ipn2 K6DfehtDNjVWRY1vQAQVkwbUQ5rI= X-Gm-Gg: ASbGncuQCOfJ9XuZteOIsS5GshjPg14sg+wDz2AwyW/ng/SmcpnFBfyc3ky6zGPzR0a ckxAr7B23wg4lCdLb7srsE9pmr66bILaa5viYptpAHq/zQWwlB1TKDZWdnPAogoqhsUN2VnXlu3 Xc5EUC7ri23flIjJIz6uq+ojQlPa0= X-Google-Smtp-Source: AGHT+IHOut0L/76uFvce+/WkHtWGVyELWUkLvJQF46CSuGPlkQfYG1p46jZZsAVe7mJiOzkVdaPG03eMg9f+AFiXcXo= X-Received: by 2002:a05:6000:144d:b0:391:2ab1:d4b8 with SMTP id ffacd0b85a97d-39132d20ceemr3577963f8f.1.1741424030392; Sat, 08 Mar 2025 00:53:50 -0800 (PST) MIME-Version: 1.0 References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> <86msdxl2gr.fsf@HIDDEN> <CADwFkmkLAy08du3yeOj9k-320gx5RbSjfKpzCbVDtA9HOd393Q@HIDDEN> <86frjpkz2b.fsf@HIDDEN> In-Reply-To: <86frjpkz2b.fsf@HIDDEN> From: Artiom Balan <artiombalan331@HIDDEN> Date: Sat, 8 Mar 2025 10:53:38 +0200 X-Gm-Features: AQ5f1Jpnrevn8S1936xiGgt6EwyOGwsrQGQPgvChcNrbVWR6DacS46UuOJNUchk Message-ID: <CAA8c5q92We1jajUURagmQp8u6XOu_Svxb6P_QhgD46u5di7Tyg@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN> Content-Type: multipart/alternative; boundary="000000000000bc2878062fd0e0bd" X-Spam-Score: 0.3 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, Stefan Kangas <stefankangas@HIDDEN> X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.7 (/) --000000000000bc2878062fd0e0bd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > But talking only about > *Warnings* makes little sense to me, since displaying that upon the > first connection already needs some minimal infrastructure we don't > have, and if we are going to develop such infrastructure, let's do it > right from the get-go. I see you're a proponent of consistency and doing the right thing ;) > If we want the first client connection to show the important messages > from the startup phase of the daemon, then warnings is not the only > thing, and not even the most important thing, that needs to be shown. Good point. To generalize, is the only difference between running a regular emacs instance and running an emacs daemon the fact that the user doesn't see some things? Like, the behavior is the same, but some things are "shown" in the daemon, which the user can't see. If so, how can we know which are all of these things? You added errors and echo-area messages. Are there any others? Would the ideal solution be to show in the first emacsclient everything that the regular instance would have shown? Or maybe a hack that displays the warnings (and errors?) in the first emacsclient would suffice? BTW, how can i get emacs to show errors after startup? I tried to add a `(error "message")` to my init.el, and starting emacs would show it as a warning: "Warning (initialization): An error occurred while loading ..." > AFAIU, some people start emacs-server from, for example, systemd, and > only ever pop up an Emacs frame with emacsclient. They might never see > the warnings. Yes, that's how I do it. It's interesting that you could also start the server by first starting emacs regularly, and then running (server-start). I might consider trying this out. On Fri, Mar 7, 2025 at 10:46=E2=80=AFAM Eli Zaretskii <eliz@HIDDEN> wrote: > > From: Stefan Kangas <stefankangas@HIDDEN> > > Date: Fri, 7 Mar 2025 08:08:13 +0000 > > Cc: artiombalan331@HIDDEN, 76772 <at> debbugs.gnu.org > > > > Eli Zaretskii <eliz@HIDDEN> writes: > > > > >> AFAIU, some people start emacs-server from, for example, systemd, an= d > > >> only ever pop up an Emacs frame with emacsclient. They might never > see > > >> the warnings. > > >> > > >> If we expect people to manually check the *Warnings* buffer, this > sounds > > >> to me as the same as saying either > > >> 1. warnings are not important to display, or > > >> 2. warnings are not important to display to users that use > > >> emacs-server+emacsclient > > >> > > >> If our reply is (2), which sounds more plausible, then I think that > must > > >> be justified somehow. > > > > > > If we want the first client connection to show the important messages > > > from the startup phase of the daemon, then warnings is not the only > > > thing, and not even the most important thing, that needs to be shown. > > > We should also show any errors and important echo-area messages, sinc= e > > > that's what the user will get when he/she starts Emacs normally with > > > the same init files and command-line arguments. This requires some > > > infrastructure we don't currently have, AFAIK. If you or someone els= e > > > want to work on such an infrastructure, I won't object to then using > > > it as part of the first client connection. But talking only about > > > *Warnings* makes little sense to me, since displaying that upon the > > > first connection already needs some minimal infrastructure we don't > > > have, and if we are going to develop such infrastructure, let's do it > > > right from the get-go. > > > > Fully agreed on all of the above. > > > > This sounds to me like: patches welcome to implement the above. > > Yes. > --000000000000bc2878062fd0e0bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><span class=3D"gmail-im">> But talking only about<= br> > *Warnings* makes little sense to me, since displaying that upon the<br= > > first connection already needs some minimal infrastructure we don'= t<br> > have, and if we are going to develop such infrastructure, let's do= it<br> > right from the get-go.<br><br></span></div><div><span class=3D"gmail-i= m">I see you're a proponent of consistency and doing the right thing ;= )</span></div><div><span class=3D"gmail-im"><br>> If we want the first c= lient connection to show the important messages<br> > from the startup phase of the daemon, then warnings is not the only<br= > > thing, and not even the most important thing, that needs to be shown.<= br><br></span></div><div>Good point. To generalize, is the only difference = between running a regular emacs instance and running an emacs daemon the fa= ct that the user doesn't see some things? Like, the behavior is the sam= e, but some things are "shown" in the daemon, which the user can&= #39;t see. If so, how can we know which are all of these things? You added = errors and echo-area messages. Are there any others?<br><br></div><div>Woul= d the ideal solution be to show in the first emacsclient everything that th= e regular instance would have shown? Or maybe a hack that displays the warn= ings (and errors?) in the first emacsclient would suffice? <br><br></div><d= iv>BTW, how can i get emacs to show errors after startup? I tried to add a = `(error "message")` to my init.el, and starting emacs would show = it as a warning: <br>"Warning (initialization): An error occurred whil= e loading ..."<br></div><div><br>> AFAIU, some people start emacs-s= erver from, for example, systemd, and<br>> only ever pop up an Emacs fra= me with emacsclient.=C2=A0 They might never see<br>> the warnings.<br> <= br></div>Yes, that's how I do it. It's interesting that you could a= lso start the server by first starting emacs regularly, and then running (s= erver-start). I might consider trying this out.</div><br><div class=3D"gmai= l_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri= , Mar 7, 2025 at 10:46=E2=80=AFAM Eli Zaretskii <<a href=3D"mailto:eliz@= gnu.org">eliz@HIDDEN</a>> wrote:<br></div><blockquote class=3D"gmail_qu= ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20= 4);padding-left:1ex">> From: Stefan Kangas <<a href=3D"mailto:stefank= angas@HIDDEN" target=3D"_blank">stefankangas@HIDDEN</a>><br> > Date: Fri, 7 Mar 2025 08:08:13 +0000<br> > Cc: <a href=3D"mailto:artiombalan331@HIDDEN" target=3D"_blank">arti= ombalan331@HIDDEN</a>, <a href=3D"mailto:76772 <at> debbugs.gnu.org" target= =3D"_blank">76772 <at> debbugs.gnu.org</a><br> > <br> > Eli Zaretskii <<a href=3D"mailto:eliz@HIDDEN" target=3D"_blank">el= iz@HIDDEN</a>> writes:<br> > <br> > >> AFAIU, some people start emacs-server from, for example, syst= emd, and<br> > >> only ever pop up an Emacs frame with emacsclient.=C2=A0 They = might never see<br> > >> the warnings.<br> > >><br> > >> If we expect people to manually check the *Warnings* buffer, = this sounds<br> > >> to me as the same as saying either<br> > >> 1. warnings are not important to display, or<br> > >> 2. warnings are not important to display to users that use<br= > > >>=C2=A0 =C2=A0 emacs-server+emacsclient<br> > >><br> > >> If our reply is (2), which sounds more plausible, then I thin= k that must<br> > >> be justified somehow.<br> > ><br> > > If we want the first client connection to show the important mess= ages<br> > > from the startup phase of the daemon, then warnings is not the on= ly<br> > > thing, and not even the most important thing, that needs to be sh= own.<br> > > We should also show any errors and important echo-area messages, = since<br> > > that's what the user will get when he/she starts Emacs normal= ly with<br> > > the same init files and command-line arguments.=C2=A0 This requir= es some<br> > > infrastructure we don't currently have, AFAIK.=C2=A0 If you o= r someone else<br> > > want to work on such an infrastructure, I won't object to the= n using<br> > > it as part of the first client connection.=C2=A0 But talking only= about<br> > > *Warnings* makes little sense to me, since displaying that upon t= he<br> > > first connection already needs some minimal infrastructure we don= 't<br> > > have, and if we are going to develop such infrastructure, let'= ;s do it<br> > > right from the get-go.<br> > <br> > Fully agreed on all of the above.<br> > <br> > This sounds to me like: patches welcome to implement the above.<br> <br> Yes.<br> </blockquote></div> --000000000000bc2878062fd0e0bd--
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 7 Mar 2025 08:47:06 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Fri Mar 07 03:47:06 2025 Received: from localhost ([127.0.0.1]:46929 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqTMI-0008Vh-16 for submit <at> debbugs.gnu.org; Fri, 07 Mar 2025 03:47:06 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:52040) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tqTMF-0008VD-UV for 76772 <at> debbugs.gnu.org; Fri, 07 Mar 2025 03:47:04 -0500 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 <eliz@HIDDEN>) id 1tqTMA-00007k-F2; Fri, 07 Mar 2025 03:46:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=O7b44m5zUX5hLBhC73POYlQv3iI8XLSp5Xyb4OUVLfc=; b=dJxjWnxjJ0uN 0703XpkP06+id1ltSatbsDv2v6Bzx8TbyCj7dKjNJluH+OVEG/GMGc5OSv5P8OD6TiSA4/UxTrTzN P46FckS2FLj6RstMk/nLkJZ8EY1JdwvEWwkI0K/Q4P+Icx2xy+prryKjXFbOG//6Fy32aUD2+57I7 oD9UDPLvjaCaFPxDVGFQgi7Vam89oh3CongTmaqsjQRMNtUvcErA/28Xttgj3xBzkkiOKJdZL/Swo YeyDW+auSXWetJIotN62PBjvty4JotNV1NHPmllPi9eWiyS2gfHpN5iy/Wobwo7ATWzgb2lcujdCi MowC4d6sx+6HpDNA34yzlQ==; Date: Fri, 07 Mar 2025 10:46:52 +0200 Message-Id: <86frjpkz2b.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <CADwFkmkLAy08du3yeOj9k-320gx5RbSjfKpzCbVDtA9HOd393Q@HIDDEN> (message from Stefan Kangas on Fri, 7 Mar 2025 08:08:13 +0000) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> <86msdxl2gr.fsf@HIDDEN> <CADwFkmkLAy08du3yeOj9k-320gx5RbSjfKpzCbVDtA9HOd393Q@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, artiombalan331@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Stefan Kangas <stefankangas@HIDDEN> > Date: Fri, 7 Mar 2025 08:08:13 +0000 > Cc: artiombalan331@HIDDEN, 76772 <at> debbugs.gnu.org > > Eli Zaretskii <eliz@HIDDEN> writes: > > >> AFAIU, some people start emacs-server from, for example, systemd, and > >> only ever pop up an Emacs frame with emacsclient. They might never see > >> the warnings. > >> > >> If we expect people to manually check the *Warnings* buffer, this sounds > >> to me as the same as saying either > >> 1. warnings are not important to display, or > >> 2. warnings are not important to display to users that use > >> emacs-server+emacsclient > >> > >> If our reply is (2), which sounds more plausible, then I think that must > >> be justified somehow. > > > > If we want the first client connection to show the important messages > > from the startup phase of the daemon, then warnings is not the only > > thing, and not even the most important thing, that needs to be shown. > > We should also show any errors and important echo-area messages, since > > that's what the user will get when he/she starts Emacs normally with > > the same init files and command-line arguments. This requires some > > infrastructure we don't currently have, AFAIK. If you or someone else > > want to work on such an infrastructure, I won't object to then using > > it as part of the first client connection. But talking only about > > *Warnings* makes little sense to me, since displaying that upon the > > first connection already needs some minimal infrastructure we don't > > have, and if we are going to develop such infrastructure, let's do it > > right from the get-go. > > Fully agreed on all of the above. > > This sounds to me like: patches welcome to implement the above. Yes.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Stefan Kangas <stefankangas@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Stefan Kangas <stefankangas@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Received: (at 76772) by debbugs.gnu.org; 7 Mar 2025 08:08:23 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Fri Mar 07 03:08:23 2025 Received: from localhost ([127.0.0.1]:46821 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqSko-0003gU-QF for submit <at> debbugs.gnu.org; Fri, 07 Mar 2025 03:08:23 -0500 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]:49184) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <stefankangas@HIDDEN>) id 1tqSkl-0003g3-V8 for 76772 <at> debbugs.gnu.org; Fri, 07 Mar 2025 03:08:20 -0500 Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-5e5cd420781so2506133a12.2 for <76772 <at> debbugs.gnu.org>; Fri, 07 Mar 2025 00:08:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741334894; x=1741939694; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=uNWCOmEF7oomjM/0+tFFIuOC5nqW0h4uxAxoMw+swgI=; b=FQntBOOPiePB5PypDXOvbJdfPWvsyPCR5uxpmQA8AqMsBavWxMhvl+kX6CR7pX1d2Q LGQtw7Zdq7dy0Ia4HOf9EWA7Urg+TE4PpEhu0rOjZMjSF+0TlxA9P60i9SslSK5FgMMo 48Lngu+licMsVaKM7pihNBQpxRuto6Zis4YXDVV6P9u39KzDt6W3lwqkYsIHit2zUHCL nZDvwQjSMtS5SApV0//FrscrJHb5gWIee8snh3Iyeb/mux0mRCFFVUCuJiK4kV7H2Ag5 4o/mJD5btMsUzShctU7t7rP+EjrY5p7Us900XaBKqqj77Inf9YZeD4tja0CoamnzRCyM BtMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741334894; x=1741939694; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=uNWCOmEF7oomjM/0+tFFIuOC5nqW0h4uxAxoMw+swgI=; b=XVJDxvnQdzOTurVDBYhlRvmiOqBRmVKC28EGXs3ta0Joy335glFl6E5dAixLjAF0Dt rniaYiazxN+iSaP0SAk554dfq6t0h/6E0kzo3Sh/ulQCCdBRyusxH76e4S/ZYMQbjkRb 1jicP3ILGDGw67+hoknU7KrITMealb6kZWA9qqbfrVH72TwBSLCRiWaedCUMO3V7b11O OtbZnA+Yaz4mjRCMECxI8qG8dOvd537EWVNWWTVswqsMqIaZBMLyXPhGS8HhWgKfrJJd 0jMiKembtqRmOHD5rYq0CQ1Wdc7st8I17LrQ3kMEA2BBex2L+2bbzUYhUOEMydbKiWiz w1Yg== X-Forwarded-Encrypted: i=1; AJvYcCXZvHVSArhQqR3aY0GCSts2vMUhjWmnEPEbjmBBeE/OYzLS/SpmhrJg0bAAwVBhCqTqJMH0FQ==@debbugs.gnu.org X-Gm-Message-State: AOJu0YxwF2C8mxhY5C/pMdRSTI00aYbMheOcD8r+NUx7yxwCZVdY0Rsj yZhtMrtvs0m2YhcZ9cfBzYqn1qwUDmvMDwSHDGAk322/HE1ltdbK/5AC9XugxGoIkBhLD+Nxsr9 QPcszJPFUZHPwX3/5/snY+kCON+s= X-Gm-Gg: ASbGncsMqzNhtoluA2lWLKHfAKVJ0H3i/mlEQEN+pYWmDlBLzcyLP2MpeVg14u6uNVe kMaAJeBILbBs+v/CSC4fcpWGXPT3xRP2tLAkv33Lao/iuTp4uz8Ci1CWTs10jftcbSowBxULfZ6 Id4izsusGdyqrdaBj6pPyKbX12bQ== X-Google-Smtp-Source: AGHT+IHO4ihgYtkqBccPoJjSQXK2r2G8ZC7OWkS5Ng0VmIB0j7POc3YC8Pf/Wcdj+zP4Kv1FkIeQOOUXV5mKP7uEvQ8= X-Received: by 2002:a05:6402:520c:b0:5e5:c0e7:f43a with SMTP id 4fb4d7f45d1cf-5e5e21050b2mr2927647a12.0.1741334893448; Fri, 07 Mar 2025 00:08:13 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Fri, 7 Mar 2025 08:08:13 +0000 From: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <86msdxl2gr.fsf@HIDDEN> References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> <86msdxl2gr.fsf@HIDDEN> MIME-Version: 1.0 Date: Fri, 7 Mar 2025 08:08:13 +0000 X-Gm-Features: AQ5f1Jq4rREQUAxKY93vtOEY9lx14Tr8l4C58GSWzOngSBRtO0uFWVWu1NJ7ppc Message-ID: <CADwFkmkLAy08du3yeOj9k-320gx5RbSjfKpzCbVDtA9HOd393Q@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN> Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, artiombalan331@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) Eli Zaretskii <eliz@HIDDEN> writes: >> AFAIU, some people start emacs-server from, for example, systemd, and >> only ever pop up an Emacs frame with emacsclient. They might never see >> the warnings. >> >> If we expect people to manually check the *Warnings* buffer, this sounds >> to me as the same as saying either >> 1. warnings are not important to display, or >> 2. warnings are not important to display to users that use >> emacs-server+emacsclient >> >> If our reply is (2), which sounds more plausible, then I think that must >> be justified somehow. > > If we want the first client connection to show the important messages > from the startup phase of the daemon, then warnings is not the only > thing, and not even the most important thing, that needs to be shown. > We should also show any errors and important echo-area messages, since > that's what the user will get when he/she starts Emacs normally with > the same init files and command-line arguments. This requires some > infrastructure we don't currently have, AFAIK. If you or someone else > want to work on such an infrastructure, I won't object to then using > it as part of the first client connection. But talking only about > *Warnings* makes little sense to me, since displaying that upon the > first connection already needs some minimal infrastructure we don't > have, and if we are going to develop such infrastructure, let's do it > right from the get-go. Fully agreed on all of the above. This sounds to me like: patches welcome to implement the above.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 7 Mar 2025 07:33:38 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Fri Mar 07 02:33:38 2025 Received: from localhost ([127.0.0.1]:46741 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqSDC-00025h-7k for submit <at> debbugs.gnu.org; Fri, 07 Mar 2025 02:33:38 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57262) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tqSD9-00025T-CN for 76772 <at> debbugs.gnu.org; Fri, 07 Mar 2025 02:33:35 -0500 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 <eliz@HIDDEN>) id 1tqSD3-0004b5-SX; Fri, 07 Mar 2025 02:33:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Tx3lZlTdcxGZhZ1cqXB5itfOcswZVDlbBnn15W0kvho=; b=Crf0dwfjOk8G wKBzoShCPzR1+v5m0ELGkwbYUCRfp1cbPRlynZqRdlOmeUAHEscgare9vqXy9Zv/FOOz4QxPvT5Fw YIN3DXHmFzsUq/nteMUyrM/QDtLQou75MMyObmlNoG2zr0IqWnFlvhFAxIabdg5ww6sKrveVJEvtL ShKgia7vSiviLKYDDx+r87buAQ8pBZNYJ6ZWjln10mP81KNBhLGaIi3Z1i4lKFhCaWVAxK7fzP4n4 GpScWK5IYvwMMLpy/EGn3/MJfMIvjoXl9tPSzm1tRmYIFpt3VanV9Kveb/ouMmpj39qtAjyLnTPqB g7Tj7LLHloRGTVPuTaBNUQ==; Date: Fri, 07 Mar 2025 09:33:24 +0200 Message-Id: <86msdxl2gr.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> (message from Stefan Kangas on Fri, 7 Mar 2025 01:28:34 +0000) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, artiombalan331@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Stefan Kangas <stefankangas@HIDDEN> > Date: Fri, 7 Mar 2025 01:28:34 +0000 > Cc: artiombalan331@HIDDEN, 76772 <at> debbugs.gnu.org > > Eli Zaretskii <eliz@HIDDEN> writes: > > >> > The *Warnings* buffer is there, it's just that the client frame > >> > doesn't show it. Why should it? how should it know you want that > >> > particular buffer displayed without any indication from you? > >> > >> We show it unconditionally in regular Emacs sessions, so it is at the > >> very least surprising that it is not displayed in the scenario described > >> above. > > > > When emacsclient connects, the new frame that it starts shows what > > emacsclient tells the server to display, and if it doesn't, then the > > default is the current buffer. The server never displays anything > > without being told, and emacsclient cannot know what were the > > command-line arguments with which the daemon was invoked. > > > > In general, the client frame shows what emacsclient tells it to show, > > not something from the time the daemon started. > > > > So I think the analogy cannot work, at least due to technical reasons > > if not in principle. > > AFAIU, some people start emacs-server from, for example, systemd, and > only ever pop up an Emacs frame with emacsclient. They might never see > the warnings. > > If we expect people to manually check the *Warnings* buffer, this sounds > to me as the same as saying either > 1. warnings are not important to display, or > 2. warnings are not important to display to users that use > emacs-server+emacsclient > > If our reply is (2), which sounds more plausible, then I think that must > be justified somehow. If we want the first client connection to show the important messages from the startup phase of the daemon, then warnings is not the only thing, and not even the most important thing, that needs to be shown. We should also show any errors and important echo-area messages, since that's what the user will get when he/she starts Emacs normally with the same init files and command-line arguments. This requires some infrastructure we don't currently have, AFAIK. If you or someone else want to work on such an infrastructure, I won't object to then using it as part of the first client connection. But talking only about *Warnings* makes little sense to me, since displaying that upon the first connection already needs some minimal infrastructure we don't have, and if we are going to develop such infrastructure, let's do it right from the get-go.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 7 Mar 2025 01:28:44 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 20:28:44 2025 Received: from localhost ([127.0.0.1]:46040 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqMW3-0004Nz-Ar for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 20:28:44 -0500 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]:57419) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <stefankangas@HIDDEN>) id 1tqMW1-0004Ni-0Y for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 20:28:42 -0500 Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-5e4ad1d67bdso2006813a12.2 for <76772 <at> debbugs.gnu.org>; Thu, 06 Mar 2025 17:28:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741310915; x=1741915715; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=Sd7j/ngOJITSluLTSjHqq54ivP66oeNqfciRMInbtDw=; b=heHvB4tDop4GgED4YaK4oxE50iVgJ8fPPSyv+1pD9i53F8SAWxO/ymrAu/P3fsp4ue cIKQFfF5O5BiafPeI7j2WYQZHPiB5XMFEbY8kMNoelwULWTdjVBdKJO/2KJUGsX5sWRr 0OKmfMhmu3C1fUVMaGY47Z7/+GdXplpzCmvPnzJQYMhOLNOYwqHOrvi3V1FRhQyYKbJw Kwgho0PUwTgvkBRCmMOOoYXoPcyB6XMxq7HmERySqWloulq6VXFo9a0G1sW5SEIJ54aV hICzPD33C9N/1H/4YWf5Opw4b/sTqQ5zsqX7jJjDEDdKhVM2lu8TZdDMTiv8YACGWxTL yGyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741310915; x=1741915715; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Sd7j/ngOJITSluLTSjHqq54ivP66oeNqfciRMInbtDw=; b=Q0gU63rW6Jqk6ruott8xEy3//l/xWuimUQiTbeHVaFvtBPeHEnXcZ7x6Sf76PPeQyk KUd2PXYzWxO5+T41SMxPT754ZR+yn3hnDfanAByDQ3rj2G9qRkWB+TFEHnmW+LmKgXo+ yx9ccSuVs+F24IZLjJ3sy/tpwh1nHx8jswa2dfqhiiprkOLeMEtqhqwN4qSYBH5LnucI Xsy7xiaodAWU826gBsVYKQ/1oMW8ohE379fdYOWEInXzk9uBvINTWxt/LsrmLssgu91W ROBqI09RFaE1h/z9S8NgxKcrNqLPtft9fy9/NumBDaB6Kn8XIFsEDqP7FaAFJTwtUUxz 2W4g== X-Forwarded-Encrypted: i=1; AJvYcCVlOMeWDCzlY4/T86EI5qd6qrxHw4DTNY6IuXKp2d9TjYC5Tx/aq1rs9Yti3AQCJKZ4wcyBeA==@debbugs.gnu.org X-Gm-Message-State: AOJu0YyFL2yG2ynpthrzbQGc3dJxvswyyJ6+PNRGJiEtYSP7sRkecgon +LN5uz63E7wLCMRbH3RBP9rcQ9vfch7Uz66tuGTyo+ORfWKclLglkdBUtjG5d52WQeb1JiVtrG4 h+eNg00AJwQKp+itAH2NHJUw8Jy0= X-Gm-Gg: ASbGnctHVsvhYtHmlddK9aMK2MEKldtv9ecH1QP1iJBqtIdlpKGxtglnC184MyHXI6J 5pwOjBb1SxiBX0s4aqUd95k6hMBHEKpbEMMR96WP6Fr8y9yMJQyFcxCbuskSwSUhRJqtYFsozoe PO5RJNi58vT/dU8O/wMfmPLJleNQ== X-Google-Smtp-Source: AGHT+IFHK0htduWb5ZTNNWiYuStSpXMUIDdwj1ZrKbISvENjkJmwVQyTGrHQyV8qnA+Yh5FHGWxHy1wx0LapqW6RZ+E= X-Received: by 2002:a05:6402:270f:b0:5de:cbed:c955 with SMTP id 4fb4d7f45d1cf-5e5e2309644mr1313033a12.17.1741310914631; Thu, 06 Mar 2025 17:28:34 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Fri, 7 Mar 2025 01:28:34 +0000 From: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <86frjqmeec.fsf@HIDDEN> References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> MIME-Version: 1.0 Date: Fri, 7 Mar 2025 01:28:34 +0000 X-Gm-Features: AQ5f1JpKku0GEe4Ihmdy5vwV7hyW9e180lfsU9pyyvnfV6mLq-3nFDPKXtU8dlQ Message-ID: <CADwFkmn+vdfvoXj98WNaDG5rO35iEk2sym0hkZy6QxRCK_RK1Q@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN> Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, artiombalan331@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) Eli Zaretskii <eliz@HIDDEN> writes: >> From: Stefan Kangas <stefankangas@HIDDEN> >> Date: Thu, 6 Mar 2025 01:25:37 -0800 >> Cc: 76772 <at> debbugs.gnu.org >> >> Eli Zaretskii <eliz@HIDDEN> writes: >> >> > tags 76772 notabug >> > thanks >> > >> >> From: Artiom Balan <artiombalan331@HIDDEN> >> >> Date: Wed, 5 Mar 2025 23:47:26 +0200 >> >> >> >> Steps to reproduce: >> >> 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" >> >> 2. Notice the warning is displayed >> >> 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \"message\"))" >> >> 4. Open a client: emacsclient -c >> >> 5. Notice the warning is not displayed >> >> >> >> I expected that the warnings buffer would be displayed in the exact >> >> same way in the emacsclient as in the first scenario. >> > >> > Thanks. >> > >> > The *Warnings* buffer is there, it's just that the client frame >> > doesn't show it. Why should it? how should it know you want that >> > particular buffer displayed without any indication from you? >> >> We show it unconditionally in regular Emacs sessions, so it is at the >> very least surprising that it is not displayed in the scenario described >> above. > > When emacsclient connects, the new frame that it starts shows what > emacsclient tells the server to display, and if it doesn't, then the > default is the current buffer. The server never displays anything > without being told, and emacsclient cannot know what were the > command-line arguments with which the daemon was invoked. > > In general, the client frame shows what emacsclient tells it to show, > not something from the time the daemon started. > > So I think the analogy cannot work, at least due to technical reasons > if not in principle. AFAIU, some people start emacs-server from, for example, systemd, and only ever pop up an Emacs frame with emacsclient. They might never see the warnings. If we expect people to manually check the *Warnings* buffer, this sounds to me as the same as saying either 1. warnings are not important to display, or 2. warnings are not important to display to users that use emacs-server+emacsclient If our reply is (2), which sounds more plausible, then I think that must be justified somehow.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 14:54:21 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 09:54:21 2025 Received: from localhost ([127.0.0.1]:42148 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqCc8-0007Fs-Fg for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:54:20 -0500 Received: from mail-wr1-x432.google.com ([2a00:1450:4864:20::432]:55391) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <artiombalan331@HIDDEN>) id 1tqCc6-0007Fa-Ah for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:54:19 -0500 Received: by mail-wr1-x432.google.com with SMTP id ffacd0b85a97d-3912e96c8e8so402850f8f.2 for <76772 <at> debbugs.gnu.org>; Thu, 06 Mar 2025 06:54:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741272852; x=1741877652; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9Cx7pfcHDvdHxWWn8Ko32NAbiDd3C/K57jhf1QgGIXc=; b=Ht5aRMnBGqbz2hwD45c0YXel6lqWKEni9C8sBTADRuckj26lH4sbjLGWkFDSLRQqY9 rn2GGcNV153ce+Du/aG9cSvv/1d63UzQqLjZTxza5ww9kppSjB5hct987psVAfrn3U/+ peKf2ysk5OwM21ML1Ehs6ElOwrJVw6+lx2nUnLC4mvfvQ8A/tGRqJDLHpsqIJyagEYM3 4R1y1A4vLCOsVyYy1S0n/mcj4DA3QGo4WEG9G2k0KxI3aaxZu7Hjq8CVRrAUffytar5O YL6r2hHUcURM7CTX7kGmmO8HTBhqyj4AUtkAuX8uY2mB0irhr/032LFw3MFhN88EKUxq wBqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741272852; x=1741877652; 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=9Cx7pfcHDvdHxWWn8Ko32NAbiDd3C/K57jhf1QgGIXc=; b=U+avcV3I9TMPzj8twhzhQwDKVkOvuf5LYZ3tPUeU75DuYiFYZXTRjOqN+x80vM9aiC +zgMujinn6yNzD6qS7qt36pvZkDfTYd+EJjZ0CwW77y5js/p50JPdaQRZgRUsDcTJb1k gGNdPOpvQt7cI1hEJHxJhwlijZa7JvOC3zOQPaoyx4Y4FunOZkaZhC8V5TbZNTpBvtTT s3kRIACSa8NPLNPUttRrtmD0CUvWs44JXs6nsF5eIhIBmxii1Yp3xr0lqVbsEYRC2x4/ 2ZQ4HHMzmhZVg1RGrPIdVac1ezzTkzTmHbM5gnNvpZzDh4yr5wkLO264cJSt8JuvvQUv B3hA== X-Forwarded-Encrypted: i=1; AJvYcCX4z7gFh2G+XzdIhyfLlvrk1ZnpaTP8jCJTkjlUe/hdpweX0yMB1uVpbDuOpgSGQjTMbO5SXw==@debbugs.gnu.org X-Gm-Message-State: AOJu0YxIndP0KYYEZEuRZb5jrU6bU4jjGxWgtlJ5eucfqsSaffSeDDru Mlduns073rv7a0Y2TcVU7QY247FUpVK/kpej+5XIVaIN1urQbXfgSRfLNinNRxpJyElGdj/chfF qlpvUSKys6avb/o/in0JLYzDIVjE= X-Gm-Gg: ASbGncuJJ1QlomcPdeLXu0GJn3XVZPOzEy12KB4InWmt9K5mdjiSHJBA4vLLAfBeljs zr4oCmly6MIk3g62L2LJD4GykS8buwHB3zCikgh+dNhz7UBoS1JgBMFnmddr3/JgX3XZcihCseg i1KkzPchbGl43rTBBSoSTOzoM= X-Google-Smtp-Source: AGHT+IHYYf93nmXnmeFGkiDU6mWSSf9pGrSd7GleZmrjQNWaocg98g49eXQWPRfu9aP2ohFFNzuEQ3h9rQtJAQBAjx0= X-Received: by 2002:a5d:584b:0:b0:391:ccf:2d1b with SMTP id ffacd0b85a97d-3911f7d2578mr5733553f8f.49.1741272851676; Thu, 06 Mar 2025 06:54:11 -0800 (PST) MIME-Version: 1.0 References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CAA8c5q9uHNim7TOqVhRLfAS3GkrTPCR8RhiuBise0vmwdvghxA@HIDDEN> <868qpimd95.fsf@HIDDEN> In-Reply-To: <868qpimd95.fsf@HIDDEN> From: Artiom Balan <artiombalan331@HIDDEN> Date: Thu, 6 Mar 2025 16:53:59 +0200 X-Gm-Features: AQ5f1JrdOLAEhGCqB_W9ERjpevFlXlb-Jp4lUZwnpKK8_ETbX2dDmbhWHzL0TGA Message-ID: <CAA8c5q_sgWxT9o2a0iQATvG8qM-5yEhzM7rHXVigWv4UO7WWTg@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN> Content-Type: multipart/alternative; boundary="000000000000c80b4f062fadad2c" X-Spam-Score: 0.3 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, stefankangas@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.7 (/) --000000000000c80b4f062fadad2c Content-Type: text/plain; charset="UTF-8" > Why is it a problem to look in *Messages* and *Warnings*, if you are interested in any messages there? The problem is that warnings can pop up unexpectedly, and if you're not automatically notified of them you will simply miss them. On Thu, Mar 6, 2025, 4:43 PM Eli Zaretskii <eliz@HIDDEN> wrote: > > From: Artiom Balan <artiombalan331@HIDDEN> > > Date: Thu, 6 Mar 2025 16:33:08 +0200 > > Cc: Stefan Kangas <stefankangas@HIDDEN>, 76772 <at> debbugs.gnu.org > > > > With the --eval I tried to simulate an error happening during the > execution of the init.el, for example. > > Understood. > > > I don't understand why it shouldn't be the case (at least in principle) > that the client automatically displays the > > warnings that were emitted during the server startup. How else should > you be notified of the warnings? Are > > you supposed to remember to display it manually or hack your way around > it? > > The client frames display messages and warnings triggered by showing > what emacsclient told the server to execute and show. Anything else > needs to be explicitly requested to show on display, since the daemon > has no idea that the client connection is related in any way to the > message or warning or any other buffer Emacs pops due to what happened > in the server itself, _before_ the client connected. > > Why is it a problem to look in *Messages* and *Warnings*, if you are > interested in any messages there? > --000000000000c80b4f062fadad2c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><p dir=3D"ltr">> Why is it a problem to look in *Messa= ges* and *Warnings*, if you are interested in any messages there?<br> </p><p dir=3D"ltr">The problem is that warnings can pop up unexpectedly, an= d if you're not automatically notified of them you will simply miss the= m.</p><p dir=3D"ltr"><br></p><p dir=3D"ltr"><br></p> <br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu= , Mar 6, 2025, 4:43 PM Eli Zaretskii <<a href=3D"mailto:eliz@HIDDEN" ta= rget=3D"_blank" rel=3D"noreferrer">eliz@HIDDEN</a>> wrote:<br></div><bl= ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #= ccc solid;padding-left:1ex">> From: Artiom Balan <<a href=3D"mailto:a= rtiombalan331@HIDDEN" rel=3D"noreferrer noreferrer" target=3D"_blank">ar= tiombalan331@HIDDEN</a>><br> > Date: Thu, 6 Mar 2025 16:33:08 +0200<br> > Cc: Stefan Kangas <<a href=3D"mailto:stefankangas@HIDDEN" rel=3D= "noreferrer noreferrer" target=3D"_blank">stefankangas@HIDDEN</a>>, <= a href=3D"mailto:76772 <at> debbugs.gnu.org" rel=3D"noreferrer noreferrer" targe= t=3D"_blank">76772 <at> debbugs.gnu.org</a><br> > <br> > With the --eval I tried to simulate an error happening during the exec= ution of the init.el, for example. <br> <br> Understood.<br> <br> > I don't understand why it shouldn't be the case (at least in p= rinciple) that the client automatically displays the<br> > warnings that were emitted during the server startup. How else should = you be notified of the warnings? Are<br> > you supposed to remember to display it manually or hack your way aroun= d it? <br> <br> The client frames display messages and warnings triggered by showing<br> what emacsclient told the server to execute and show.=C2=A0 Anything else<b= r> needs to be explicitly requested to show on display, since the daemon<br> has no idea that the client connection is related in any way to the<br> message or warning or any other buffer Emacs pops due to what happened<br> in the server itself, _before_ the client connected.<br> <br> Why is it a problem to look in *Messages* and *Warnings*, if you are<br> interested in any messages there?<br> </blockquote></div></div> --000000000000c80b4f062fadad2c--
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 14:43:14 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 09:43:14 2025 Received: from localhost ([127.0.0.1]:42117 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqCRO-0006jp-2x for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:43:14 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:33488) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tqCRL-0006jb-Dm for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:43:11 -0500 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 <eliz@HIDDEN>) id 1tqCRF-0005kl-5e; Thu, 06 Mar 2025 09:43:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Dz8UH5JKxlF2ZPD3NIEFBq3Qx6h5ApHr2q/dDcYm7z4=; b=cwF+2fGYKxhj i8+EFuew5nwCaQ5h0p1AS5gP0lSLkKk+vIMtw8xuiZfAEyQ1a+cCiusmdW/ieam65IaE1qG0rXR8y tNcHtUspie8CZWOXT4eFIszTSXpHgukbOVRalV4Kl6oN5MkLCz6PxTjfuA+i1SNe7eY/F00Y5835c 6fM7H2Q9s9oqyolrH8x2Nwy1UnX8k7i0LTfu9XKDqzRi+FfgbUVLINyrTu3G2bPkoaZicQT0hce2u Y6cqGDyf78RgKNLXlSSvMbAjbK6lQNSZzYNCCbxvamTu8bVtZfR424nrxEotknQrfKEVTcFh+gfHY 2d6R+w/X0wz4sB5lUIq0fw==; Date: Thu, 06 Mar 2025 16:42:46 +0200 Message-Id: <868qpimd95.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Artiom Balan <artiombalan331@HIDDEN> In-Reply-To: <CAA8c5q9uHNim7TOqVhRLfAS3GkrTPCR8RhiuBise0vmwdvghxA@HIDDEN> (message from Artiom Balan on Thu, 6 Mar 2025 16:33:08 +0200) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> <CAA8c5q9uHNim7TOqVhRLfAS3GkrTPCR8RhiuBise0vmwdvghxA@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, stefankangas@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Artiom Balan <artiombalan331@HIDDEN> > Date: Thu, 6 Mar 2025 16:33:08 +0200 > Cc: Stefan Kangas <stefankangas@HIDDEN>, 76772 <at> debbugs.gnu.org > > With the --eval I tried to simulate an error happening during the execution of the init.el, for example. Understood. > I don't understand why it shouldn't be the case (at least in principle) that the client automatically displays the > warnings that were emitted during the server startup. How else should you be notified of the warnings? Are > you supposed to remember to display it manually or hack your way around it? The client frames display messages and warnings triggered by showing what emacsclient told the server to execute and show. Anything else needs to be explicitly requested to show on display, since the daemon has no idea that the client connection is related in any way to the message or warning or any other buffer Emacs pops due to what happened in the server itself, _before_ the client connected. Why is it a problem to look in *Messages* and *Warnings*, if you are interested in any messages there?
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 14:33:30 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 09:33:30 2025 Received: from localhost ([127.0.0.1]:42104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqCHx-0006Gv-Pi for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:33:30 -0500 Received: from mail-wr1-x42e.google.com ([2a00:1450:4864:20::42e]:42150) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <artiombalan331@HIDDEN>) id 1tqCHu-0006Ge-8C for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:33:27 -0500 Received: by mail-wr1-x42e.google.com with SMTP id ffacd0b85a97d-390f69e71c8so516955f8f.0 for <76772 <at> debbugs.gnu.org>; Thu, 06 Mar 2025 06:33:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741271600; x=1741876400; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zDH55+PUr/yubzRJG1fVmYZZPH1xTRFZA148AgGy/tY=; b=KM6PGwo8K3+KTF1EVWQU/rAVzdylhmX6EIvYw+swUWl9FCWCfRAbQkiolR3p3zJG0c Af3/LMOuMFjn2zv6LlZs1ugAh6f0Jb8TF2f/d8d3jZOM4bP8hGShQ2XmApVMGM6kgyvz Qil9003DjAOZRA543DvS1YZ7b198zRm5t8q2Nxg3z/U30N+lRKdLiM2u9sssGVopNMTW TyS1lPVUzdNrKkqsBK9ulnjpi1befDzSqmOtOpIKf90W4Yxnee5TJlECpswXFwigZF0w FdbEDdt5N3dbjQOAgIZQdWYZ3evoI/8pctFhAKH3ZFAPIF7pUgTwg/QqylYWbq8dwiCx H8+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741271600; x=1741876400; 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=zDH55+PUr/yubzRJG1fVmYZZPH1xTRFZA148AgGy/tY=; b=cC9Ac/S/7pA3ujSgC4itgZkCpoMPGCIPfqe3ht88rlPs8zSpVVk249mWC/7W3StP5H ZMkVGBbc1G2hfJtZvGiwyAvV05CFzMv39oL/AcGcnLpyoPkSgw/H/9mMMTB3EaOJgy9f z01IsDh1LKhTyGVdpaJuB343FqA87FwEE9mxTD4nD+8MXF4TguQWx3BROBLX1HCk3p/A Rt1I3JO/xXvJhG7D/bglENEKF89Bxct+fdnFNuPhIq3DB8OGoSxtQRny+b19RT77lmdq I27fJ1Sz8sXGT41Jn0AR9LiXNuvuo1QtaAa42jkxTgavXEGBZldgMCOxvUJg6oLdoc7w 3Lbw== X-Forwarded-Encrypted: i=1; AJvYcCUNqcXfsQ1FDZehZHlO8HD8fbd5Wr44nk0d+Wzq1CfaAlqNegabrdir8ElVd/0X4/El8Nclvg==@debbugs.gnu.org X-Gm-Message-State: AOJu0YwiIY5vH7u2WrbnHhmWL72dIrTGmt0Sl1dQCBaT7WsYaYrSHbip b4Yr31nwxfFrc3iJk4L8+Nsu9znR7No9oAOWWLQm8ZjikPowLm4SwWdA0c7Wf+b0OMyt/VGHNno tMDW1D3UglqnzBPxNuehWafeKWp4= X-Gm-Gg: ASbGnctgwVyzAap0JjFzTTqz3/PZ06pFK4XjUS9frZenZqCYEtHwPWINrbNqfq5wWMD XMBwvheFLlkHcbappVMebSJondsVdQN2Mta7AnXkS6KWvKafI003Rf5BESYFrr5bQG4CTq9BKbj K07pXW+yBZltyN2aeQ1m0m0v0= X-Google-Smtp-Source: AGHT+IEvgWgamCTWcGEYqmCGZP0jESBVFtk1WI1rYU9hqiE/c9GZmPj00ibkV8E9VxqaI4V6WiFPwA6a15QC5UxZdNg= X-Received: by 2002:a05:6000:2185:b0:390:f9e0:f0d0 with SMTP id ffacd0b85a97d-391296d3d3bmr2104709f8f.6.1741271599959; Thu, 06 Mar 2025 06:33:19 -0800 (PST) MIME-Version: 1.0 References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> <86frjqmeec.fsf@HIDDEN> In-Reply-To: <86frjqmeec.fsf@HIDDEN> From: Artiom Balan <artiombalan331@HIDDEN> Date: Thu, 6 Mar 2025 16:33:08 +0200 X-Gm-Features: AQ5f1JprURDPbTv5nojvXOJsjmYPHtK6RWYTW1CPKKDBi8VPsXcNUYSnmCBT-6A Message-ID: <CAA8c5q9uHNim7TOqVhRLfAS3GkrTPCR8RhiuBise0vmwdvghxA@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN> Content-Type: multipart/alternative; boundary="0000000000002c5a15062fad63c6" X-Spam-Score: 0.3 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, Stefan Kangas <stefankangas@HIDDEN> X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -0.7 (/) --0000000000002c5a15062fad63c6 Content-Type: text/plain; charset="UTF-8" With the --eval I tried to simulate an error happening during the execution of the init.el, for example. I don't understand why it shouldn't be the case (at least in principle) that the client automatically displays the warnings that were emitted during the server startup. How else should you be notified of the warnings? Are you supposed to remember to display it manually or hack your way around it? On Thu, Mar 6, 2025, 4:18 PM Eli Zaretskii <eliz@HIDDEN> wrote: > > From: Stefan Kangas <stefankangas@HIDDEN> > > Date: Thu, 6 Mar 2025 01:25:37 -0800 > > Cc: 76772 <at> debbugs.gnu.org > > > > Eli Zaretskii <eliz@HIDDEN> writes: > > > > > tags 76772 notabug > > > thanks > > > > > >> From: Artiom Balan <artiombalan331@HIDDEN> > > >> Date: Wed, 5 Mar 2025 23:47:26 +0200 > > >> > > >> Steps to reproduce: > > >> 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" > > >> 2. Notice the warning is displayed > > >> 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning > 'type \"message\"))" > > >> 4. Open a client: emacsclient -c > > >> 5. Notice the warning is not displayed > > >> > > >> I expected that the warnings buffer would be displayed in the exact > > >> same way in the emacsclient as in the first scenario. > > > > > > Thanks. > > > > > > The *Warnings* buffer is there, it's just that the client frame > > > doesn't show it. Why should it? how should it know you want that > > > particular buffer displayed without any indication from you? > > > > We show it unconditionally in regular Emacs sessions, so it is at the > > very least surprising that it is not displayed in the scenario described > > above. > > When emacsclient connects, the new frame that it starts shows what > emacsclient tells the server to display, and if it doesn't, then the > default is the current buffer. The server never displays anything > without being told, and emacsclient cannot know what were the > command-line arguments with which the daemon was invoked. > > In general, the client frame shows what emacsclient tells it to show, > not something from the time the daemon started. > > So I think the analogy cannot work, at least due to technical reasons > if not in principle. > --0000000000002c5a15062fad63c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><p dir=3D"ltr">With the --eval I tried to simulate an err= or happening during the execution of the init.el, for example. </p> <p dir=3D"ltr">I don't understand why it shouldn't be the case (at = least in principle) that the client automatically displays the warnings tha= t were emitted during the server startup. How else should you be notified o= f the warnings? Are you supposed to remember to display it manually or hack= your way around it? </p></div> <br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu= , Mar 6, 2025, 4:18 PM Eli Zaretskii <<a href=3D"mailto:eliz@HIDDEN" ta= rget=3D"_blank" rel=3D"noreferrer">eliz@HIDDEN</a>> wrote:<br></div><bl= ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #= ccc solid;padding-left:1ex">> From: Stefan Kangas <<a href=3D"mailto:= stefankangas@HIDDEN" rel=3D"noreferrer noreferrer" target=3D"_blank">ste= fankangas@HIDDEN</a>><br> > Date: Thu, 6 Mar 2025 01:25:37 -0800<br> > Cc: <a href=3D"mailto:76772 <at> debbugs.gnu.org" rel=3D"noreferrer norefer= rer" target=3D"_blank">76772 <at> debbugs.gnu.org</a><br> > <br> > Eli Zaretskii <<a href=3D"mailto:eliz@HIDDEN" rel=3D"noreferrer no= referrer" target=3D"_blank">eliz@HIDDEN</a>> writes:<br> > <br> > > tags 76772 notabug<br> > > thanks<br> > ><br> > >> From: Artiom Balan <<a href=3D"mailto:artiombalan331@gmail= .com" rel=3D"noreferrer noreferrer" target=3D"_blank">artiombalan331@gmail.= com</a>><br> > >> Date: Wed, 5 Mar 2025 23:47:26 +0200<br> > >><br> > >> Steps to reproduce:<br> > >> 1. Run emacs: emacs -Q --eval "(display-warning 'typ= e \"message\"))"<br> > >> 2. Notice the warning is displayed<br> > >> 3. Start emacs server: emacs -Q --fg-daemon --eval "(dis= play-warning 'type \"message\"))"<br> > >> 4. Open a client: emacsclient -c<br> > >> 5. Notice the warning is not displayed<br> > >><br> > >> I expected that the warnings buffer would be displayed in the= exact<br> > >> same way in the emacsclient as in the first scenario.<br> > ><br> > > Thanks.<br> > ><br> > > The *Warnings* buffer is there, it's just that the client fra= me<br> > > doesn't show it.=C2=A0 Why should it? how should it know you = want that<br> > > particular buffer displayed without any indication from you?<br> > <br> > We show it unconditionally in regular Emacs sessions, so it is at the<= br> > very least surprising that it is not displayed in the scenario describ= ed<br> > above.<br> <br> When emacsclient connects, the new frame that it starts shows what<br> emacsclient tells the server to display, and if it doesn't, then the<br= > default is the current buffer.=C2=A0 The server never displays anything<br> without being told, and emacsclient cannot know what were the<br> command-line arguments with which the daemon was invoked.<br> <br> In general, the client frame shows what emacsclient tells it to show,<br> not something from the time the daemon started.<br> <br> So I think the analogy cannot work, at least due to technical reasons<br> if not in principle.<br> </blockquote></div> --0000000000002c5a15062fad63c6--
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 14:18:16 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 09:18:16 2025 Received: from localhost ([127.0.0.1]:42047 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqC3E-0005Ns-28 for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:18:16 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:54438) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tqC3A-0005NS-IR for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:18:13 -0500 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 <eliz@HIDDEN>) id 1tqC34-0002FX-10; Thu, 06 Mar 2025 09:18:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=fNkS0POBGxkE0Pzy1Scvw1YHMMWtvN2AKchqkHhHC7s=; b=cwDfgBW9gZgp cLoh+H7q6OTkfriJO19FDk+lloqbgiSgCoEfAOCrLz6O3WlGBccRJrVoAIv0jmQ3qXd6Cv7c43LEp 1+I+MdbiPbjU9Avj6VqCKrxhKn2VVtmbVX/7hklDBBq7u23GTQLeOpEvr2yE34YIoVGwesBLxCERd MUa0ScWre0wASZSew9xUutg2yZHo6pKbM84V+2NQ+Ceelnh8pCWSYGotEYRCrsNRzfLxYRvZFnnqj oK73eYTaA1KYQkSafTepzNPxL7kBoZhmSI6dIOiqMYP6d4ZLHemWWzdU77MddSEXSBwntvTAyob49 f8Xn9r/RC177FPm7fpiuAw==; Date: Thu, 06 Mar 2025 16:18:03 +0200 Message-Id: <86frjqmeec.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> (message from Stefan Kangas on Thu, 6 Mar 2025 01:25:37 -0800) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org, artiombalan331@HIDDEN X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Stefan Kangas <stefankangas@HIDDEN> > Date: Thu, 6 Mar 2025 01:25:37 -0800 > Cc: 76772 <at> debbugs.gnu.org > > Eli Zaretskii <eliz@HIDDEN> writes: > > > tags 76772 notabug > > thanks > > > >> From: Artiom Balan <artiombalan331@HIDDEN> > >> Date: Wed, 5 Mar 2025 23:47:26 +0200 > >> > >> Steps to reproduce: > >> 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" > >> 2. Notice the warning is displayed > >> 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \"message\"))" > >> 4. Open a client: emacsclient -c > >> 5. Notice the warning is not displayed > >> > >> I expected that the warnings buffer would be displayed in the exact > >> same way in the emacsclient as in the first scenario. > > > > Thanks. > > > > The *Warnings* buffer is there, it's just that the client frame > > doesn't show it. Why should it? how should it know you want that > > particular buffer displayed without any indication from you? > > We show it unconditionally in regular Emacs sessions, so it is at the > very least surprising that it is not displayed in the scenario described > above. When emacsclient connects, the new frame that it starts shows what emacsclient tells the server to display, and if it doesn't, then the default is the current buffer. The server never displays anything without being told, and emacsclient cannot know what were the command-line arguments with which the daemon was invoked. In general, the client frame shows what emacsclient tells it to show, not something from the time the daemon started. So I think the analogy cannot work, at least due to technical reasons if not in principle.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 14:13:44 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 09:13:44 2025 Received: from localhost ([127.0.0.1]:42038 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tqByp-00058V-Nr for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:13:44 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:51556) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tqBym-00058F-NM for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 09:13:41 -0500 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 <eliz@HIDDEN>) id 1tqByh-0001SO-8g; Thu, 06 Mar 2025 09:13:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=gVANPBThP5qRR6EIT+wxnihS7xEEH0fHAcuWjZ1QIjc=; b=ZAfmQ6JA4h1J XqSkinDsUH8t+DBdKiRFAZU9AxWiAj66Yt/vyl2BkOgMZtasHTJx83hVRzGKY5IVkJnV3DEb5G2fN gt1MHKmeFyjMOhrmnEhdpUTVRq8t1WDfPrrYZi5YzNXCuTjNhzkFDXmBFbI94dYJxwPQOL5vL+Muk 0JzuFSkmDupXgjWxwx5XJ2znlRvjtlCu3/nzH9Xc0lBgRABKmmdKwBunyvmePl1j6BoJkb9UiTIld SuoW+fz3wJwpQoTLnk/QdMmIQmJfiLkCAw+jtPLuYmYSMtMspttXqrKoKdCKOLc8seAdqD6X3+l0w kohhDa1kVv+avbDa4ZTLZQ==; Date: Thu, 06 Mar 2025 16:13:31 +0200 Message-Id: <86ikommelw.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Artiom Balan <artiombalan331@HIDDEN> In-Reply-To: <CAA8c5q_2GunpRe-HCc1fEqd4kpDZ8VrFmf6jPCYSXBq5h58uQg@HIDDEN> (message from Artiom Balan on Thu, 6 Mar 2025 10:56:29 +0200) Subject: Re: bug#76772: References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <CAA8c5q_2GunpRe-HCc1fEqd4kpDZ8VrFmf6jPCYSXBq5h58uQg@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) > From: Artiom Balan <artiombalan331@HIDDEN> > Date: Thu, 6 Mar 2025 10:56:29 +0200 > > > The *Warnings* buffer is there, it's just that the client frame doesn't show it. > Sorry, yes that's what I meant. > > > Why should it? > For the same reason that the warnings buffer is displayed in a regular emacs instance if there have been any > warnings emitted during startup. Emacs displays it because that's the first command it executes after starting. By contrast, in the daemon case, there's no relation between the --eval argument when starting the daemon and the client frame displayed because emacsclient connected, these events could be many minutes apart. > > how should it know you want that particular buffer displayed without any indication from you? > I think the warnings buffer should be displayed in the first emacsclient created after startup (if there are any > warnings). Then the following clients shouldn't display the warnings buffer, because the user has already > seen it. I don't think your expectations are correct, but let's hear what others think.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 09:25:52 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 04:25:52 2025 Received: from localhost ([127.0.0.1]:41559 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tq7UC-00078w-Ax for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 04:25:52 -0500 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]:44432) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <stefankangas@HIDDEN>) id 1tq7U8-00078e-Tv for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 04:25:45 -0500 Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5e0813bd105so618647a12.1 for <76772 <at> debbugs.gnu.org>; Thu, 06 Mar 2025 01:25:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741253138; x=1741857938; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=3lQhlAD1bHw4jGkY4nUxSA0sPFJ3sBPdN8TTFfk+daw=; b=c25DrTdctTeba5Dx1TnK8hWEAHZcXx4EyTqmiToY8XmFruG55GGnOeh/4n5CRveRcF 1rOODU3vh/tOcJRz9YsfSA2JMMf2oSTmw0v0kwG3FASb4Umlxi6xvtiFotJjTfZh6qnj uVExhWa8cKXTWIERjpK4AES+jeJrv7yDMrR7DMIn/cHdWpZJN0us3STi9troeGPvIsTT vHVMXqsLlIMg1WebHgRsu4kuZpJCAZMh/mJ+3AWbW8zxviQvd4I70r98dsBPS2ov6+sa td4x/ie9yMkOSR2/9xUFQhLHxsDJr/8Di177mIG77bh6/zt13Pyx0lM/838KohGlD4Hb /SiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741253138; x=1741857938; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3lQhlAD1bHw4jGkY4nUxSA0sPFJ3sBPdN8TTFfk+daw=; b=fsBjPAC+Ae5BPNffReMpw+bdLWndq1qTPebcmT79+FwItbzuVItVxYxlklUud9nrzq VXyit9j4kDS2eJ69tKdUymqLosBWWTwqs24d/LKnkRksT6v48DvI83gZ4z8JJEqdr28R JkI3xXMXYNwTRIy0PNQDPjy6/74orv145v2gLjT23vyQliZcsIGNGeub66CA0wlIx5D/ bDjYgJL3E65ef0lhtVJeCCtoiWZcIsEJhsk4Kpa82xRs4E3OZ9hnognV30oih4Atceh/ bqjQeFGR6Ef+2FMuN+RlZ2VdbLgGwhQUGHxG30MnRF+fn6vq07XIovuerGKiSIfMt0Zc 6GyA== X-Gm-Message-State: AOJu0YzbDy10m8o8NOkwFb/7jX+1JVSRQ0jJD23nCSHHX08DNXOgBE4Q ar0Wzrn8C3XNmEvTumAtOtlPPQm/YfrvE8FAPtZiEZTYB9LGjFPvcHE29RV3NTz77NydfqTyS/6 wc0KjwvAry5mRSo7sjjhhZ7Ao1nP75YCl X-Gm-Gg: ASbGnctC6h1WS73k09D494n4szfDpGqinRbew4GLLRSR5hknTBHKSvqSo48iceLQMV+ xLRC6BhdeYoKyo8KDmfiGhLS0GjaWx01JrFmWUxLlEIG7lF53CSdyHLQfL/ii0O2MyHuLCG0q7M RhK8eEzUERGlR67l8xyFGHXP+Z8Q== X-Google-Smtp-Source: AGHT+IEzQ3eCtQCy3b1AKP1imfEzm00L/L/HNc6yj5CoaBKWF6kMkKbGjOnAKHS2wyf0nJrRgd2Yp6lJwfTAVEwk9AY= X-Received: by 2002:a05:6402:2787:b0:5e4:d5f2:9748 with SMTP id 4fb4d7f45d1cf-5e59f4fd15cmr7063732a12.27.1741253137907; Thu, 06 Mar 2025 01:25:37 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 6 Mar 2025 01:25:37 -0800 From: Stefan Kangas <stefankangas@HIDDEN> In-Reply-To: <864j06o9d0.fsf@HIDDEN> References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> <864j06o9d0.fsf@HIDDEN> MIME-Version: 1.0 Date: Thu, 6 Mar 2025 01:25:37 -0800 X-Gm-Features: AQ5f1JqWeHTwpnKGChjdUOz8iC4I04BaUiXU4yuBzso1UODya83dS9yIpJme--Y Message-ID: <CADwFkm=bXSOMMhP_fi_A56-jquXy8eb9=gcjth3yOZ2CkVEApw@HIDDEN> Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: Eli Zaretskii <eliz@HIDDEN>, Artiom Balan <artiombalan331@HIDDEN> Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -1.0 (-) Eli Zaretskii <eliz@HIDDEN> writes: > tags 76772 notabug > thanks > >> From: Artiom Balan <artiombalan331@HIDDEN> >> Date: Wed, 5 Mar 2025 23:47:26 +0200 >> >> Steps to reproduce: >> 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" >> 2. Notice the warning is displayed >> 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \"message\"))" >> 4. Open a client: emacsclient -c >> 5. Notice the warning is not displayed >> >> I expected that the warnings buffer would be displayed in the exact >> same way in the emacsclient as in the first scenario. > > Thanks. > > The *Warnings* buffer is there, it's just that the client frame > doesn't show it. Why should it? how should it know you want that > particular buffer displayed without any indication from you? We show it unconditionally in regular Emacs sessions, so it is at the very least surprising that it is not displayed in the scenario described above. I would have expected Emacs to make an effort to display it to me. > Try this, and you will see the warning in the client frame: > > emacsclient -c --eval "(display-buffer \"*Warnings*\")" > > I don't see a bug here.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.
Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 08:56:51 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 03:56:51 2025
Received: from localhost ([127.0.0.1]:41458 helo=debbugs.gnu.org)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
id 1tq72B-0002c6-0J
for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 03:56:51 -0500
Received: from mail-wr1-x42e.google.com ([2a00:1450:4864:20::42e]:42244)
by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
(Exim 4.84_2) (envelope-from <artiombalan331@HIDDEN>)
id 1tq728-0002bd-2G
for 76772 <at> debbugs.gnu.org; Thu, 06 Mar 2025 03:56:48 -0500
Received: by mail-wr1-x42e.google.com with SMTP id
ffacd0b85a97d-390eebcc331so240917f8f.1
for <76772 <at> debbugs.gnu.org>; Thu, 06 Mar 2025 00:56:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1741251401; x=1741856201; darn=debbugs.gnu.org;
h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
:date:message-id:reply-to;
bh=qJvD+uOR8hY3yt5MlDXtyES96nL17KtrzPFFvfPBSgY=;
b=clBcKYGJ+PoFOEJA95ju1nLbho0/lC60HsFZDxbIHpgMJ6PDzBKXTtmbGyNG7eIxAx
fCIYJLouiNpkOMtOLazIro+aIsYjSyomchxS6UUdyU639980+e3uLWG0Uzbb5lzVqyh5
dbk4XS7tQlnM2mECZqkIGdDBLK/o4zM9n48NXy5M1ZhsB6AMzWelMc0AtpLlRx03vHK8
As9DjMNm0+nHR8mH0qdIgCKqzRMc+goce2bJ/DwQyIs17W7nmxst0EwyTyhqZv1r2NtD
rWucP9c1rfPfCmx+JfprZPoCvYRcG5bvpzlbckBXEoRvtp/pR9d3Oasjc1xJ+KlHun1N
NV7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1741251401; x=1741856201;
h=to:subject:message-id:date:from:mime-version:x-gm-message-state
:from:to:cc:subject:date:message-id:reply-to;
bh=qJvD+uOR8hY3yt5MlDXtyES96nL17KtrzPFFvfPBSgY=;
b=dxGyjpfJJRR3F8myWAvjzrOEIG7LFooz1dwWwpOHLn7CP/Vgnq0VqKFriDFssXq3VM
Y4CNILxxrDfCnQ9i2Dp38tiEEVx1r7A86UWRJOWDuJmqwAiULfF1fOB91ReDtt2ufnO0
CcuI6FJEZaKwHyJzx4109NgQmGV7yxP3a6NWnueWhLmiYDamrUj6tCSnT5tS5OwvPpPQ
vekQVCpjXvi7IaABayrdIn9P0dz1+kwSXtpejVXJ7vk5QrtTogFj6oGL5tIHyrWprEWy
rktSjd2+uuJJQFEB81GFLR4B1UTRl9RnyNtBaY7Sv4wZgpinwKCzQ2RuGImQ4v3e669F
Zsrw==
X-Gm-Message-State: AOJu0YyEZg3N6jAqJjHMbOk0vE2RxYqTxJwal1c5e8ta+1Vs270C1wiE
fRJO30EnLhaCGbYDCLAD4cXyhXGtrkLXPyuPxueXXfSuGFuQoF3kDBh+CWiRaHefhORqj5HU6bB
fh2uNjC2N9jGrfmZSzfV36xZq5DqzwifOlyI=
X-Gm-Gg: ASbGnct8zS7vDawrXtPQFOyAJaxlSRvbAbc4HH4OfT4Vv/BfE5Niye6BXpfk22kXYE2
yU+KPNsl0doPeTSI5/ipORNAarxFaq989MAdMUlQwgWptjvWklfPLIRmOcNWktfYZrvOvWy3HmW
eftwIeUAYGIqbGq05dZmKWvopr6bw=
X-Google-Smtp-Source: AGHT+IHYdmqdgpkFXuL7/XgXCq6OBFbphnPSJLu1N1k6FjSGBVq/RSLdPnlsSJNx11kDQanE/3uY1JoyRyiibVgTj1s=
X-Received: by 2002:a5d:6daa:0:b0:390:df83:1f22 with SMTP id
ffacd0b85a97d-39129850682mr1917605f8f.25.1741251401100; Thu, 06 Mar 2025
00:56:41 -0800 (PST)
MIME-Version: 1.0
From: Artiom Balan <artiombalan331@HIDDEN>
Date: Thu, 6 Mar 2025 10:56:29 +0200
X-Gm-Features: AQ5f1JoZlP6T3gmAXUuUMn8shMa3nCIrLwLNaXrxkgNtk1cfKGDXKSpRuotKHMo
Message-ID: <CAA8c5q_2GunpRe-HCc1fEqd4kpDZ8VrFmf6jPCYSXBq5h58uQg@HIDDEN>
Subject:
To: 76772 <at> debbugs.gnu.org
Content-Type: multipart/alternative; boundary="0000000000003a420d062fa8afe6"
X-Spam-Score: 2.3 (++)
X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: > The *Warnings* buffer is there, it's just that the client
frame doesn't show it. Sorry, yes that's what I meant. > Why should it? For
the same reason that the warnings buffer is displayed in a regular emacs
instance if there have been any warnings emitted during startup.
Content analysis details: (2.3 points, 10.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends
in digit (artiombalan331[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (artiombalan331[at]gmail.com)
0.0 HTML_MESSAGE BODY: HTML included in message
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/,
no trust [2a00:1450:4864:20:0:0:0:42e listed in]
[list.dnswl.org]
2.0 BLANK_SUBJECT Subject is present but empty
X-Debbugs-Envelope-To: 76772
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: 1.3 (+)
X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: > The *Warnings* buffer is there, it's just that the client
frame doesn't show it. Sorry, yes that's what I meant. > Why should it? For
the same reason that the warnings buffer is displayed in a regular emacs
instance if there have been any warnings emitted during startup.
Content analysis details: (1.3 points, 10.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/,
no trust
[2a00:1450:4864:20:0:0:0:42e listed in]
[list.dnswl.org]
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends
in digit (artiombalan331[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (artiombalan331[at]gmail.com)
0.0 HTML_MESSAGE BODY: HTML included in message
2.0 BLANK_SUBJECT Subject is present but empty
-1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list
manager
--0000000000003a420d062fa8afe6
Content-Type: text/plain; charset="UTF-8"
> The *Warnings* buffer is there, it's just that the client frame doesn't
show it.
Sorry, yes that's what I meant.
> Why should it?
For the same reason that the warnings buffer is displayed in a regular
emacs instance if there have been any warnings emitted during startup.
> how should it know you want that particular buffer displayed without any
indication from you?
I think the warnings buffer should be displayed in the first emacsclient
created after startup (if there are any warnings). Then the following
clients shouldn't display the warnings buffer, because the user has already
seen it.
--0000000000003a420d062fa8afe6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div>> The *Warnings* buffer is there, it's ju=
st that the client frame doesn't show it.<br>Sorry, yes that's what=
I meant.<br><br>> Why should it?<br></div>For the same reason that the =
warnings buffer is displayed in a regular emacs instance if there have been=
any warnings emitted during startup.<br><br>> how should it know you wa=
nt that particular buffer displayed without any indication from you?<br></d=
iv>I think the warnings buffer should be displayed in the first emacsclient=
created after startup (if there are any warnings). Then the following clie=
nts shouldn't display the warnings buffer, because the user has already=
seen it.</div>
--0000000000003a420d062fa8afe6--
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Eli Zaretskii <eliz@HIDDEN>
to control <at> debbugs.gnu.org.
Full text available.Received: (at 76772) by debbugs.gnu.org; 6 Mar 2025 08:24:14 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Thu Mar 06 03:24:13 2025 Received: from localhost ([127.0.0.1]:41351 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tq6Wb-0006Hs-JB for submit <at> debbugs.gnu.org; Thu, 06 Mar 2025 03:24:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:47892) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1tq6WZ-0006Hc-4H; Thu, 06 Mar 2025 03:24:11 -0500 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 <eliz@HIDDEN>) id 1tq6WS-0000mO-EM; Thu, 06 Mar 2025 03:24:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=3N1ocr3BChB7Glv3TOkbrqRQ6EiyxQvYylzylaNKNbc=; b=ByLykfUaEOsy 7k8c72DLV2NJ41AZlVg3b7GFIRxVmJMgIOjh5lWSzzGveK3sIsM0Axa960mTxzDAqcGRmm967N5BQ yEBih1PkaENlhzNJrQNAS8+iPo1s0/TS0T8vMiwIYJ5BdTIg4nATaVff5u1DU2VoIE7zo1W3xuKst nysxg3hm83bnv2QnK12KGK6gbZ7BEtOX1wP0in0834dqLHQLt9x7rOW+oW5xOk2Y/ndpoa7+wTCWR l85EQlNVRW8A/me6Fs1quao4ZZRW19BUAMkb8bsVi3dICbfKCJ6fL4bNqWVWvIFV2PN3Yanf31VuG 6Ll7FWN6tVaGvMWRCJ0lvg==; Date: Thu, 06 Mar 2025 10:23:55 +0200 Message-Id: <864j06o9d0.fsf@HIDDEN> From: Eli Zaretskii <eliz@HIDDEN> To: Artiom Balan <artiombalan331@HIDDEN> In-Reply-To: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> (message from Artiom Balan on Wed, 5 Mar 2025 23:47:26 +0200) Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted during daemon startup References: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 76772 Cc: 76772 <at> debbugs.gnu.org X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: -3.3 (---) tags 76772 notabug thanks > From: Artiom Balan <artiombalan331@HIDDEN> > Date: Wed, 5 Mar 2025 23:47:26 +0200 > > Steps to reproduce: > 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" > 2. Notice the warning is displayed > 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \"message\"))" > 4. Open a client: emacsclient -c > 5. Notice the warning is not displayed > > I expected that the warnings buffer would be displayed in the exact > same way in the emacsclient as in the first scenario. Thanks. The *Warnings* buffer is there, it's just that the client frame doesn't show it. Why should it? how should it know you want that particular buffer displayed without any indication from you? Try this, and you will see the warning in the client frame: emacsclient -c --eval "(display-buffer \"*Warnings*\")" I don't see a bug here.
bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.Received: (at submit) by debbugs.gnu.org; 6 Mar 2025 04:47:06 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Wed Mar 05 23:47:06 2025 Received: from localhost ([127.0.0.1]:40836 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1tq38T-00037i-KS for submit <at> debbugs.gnu.org; Wed, 05 Mar 2025 23:47:05 -0500 Received: from lists.gnu.org ([2001:470:142::17]:38394) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <artiombalan331@HIDDEN>) id 1tpwah-0005Jx-0w for submit <at> debbugs.gnu.org; Wed, 05 Mar 2025 16:47:47 -0500 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 <artiombalan331@HIDDEN>) id 1tpwab-0000dq-HC for bug-gnu-emacs@HIDDEN; Wed, 05 Mar 2025 16:47:41 -0500 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <artiombalan331@HIDDEN>) id 1tpwaa-0000kv-3q for bug-gnu-emacs@HIDDEN; Wed, 05 Mar 2025 16:47:41 -0500 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-43bc48ff815so200375e9.0 for <bug-gnu-emacs@HIDDEN>; Wed, 05 Mar 2025 13:47:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741211258; x=1741816058; darn=gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UBIyGKwqkwmbXiC/dG5HVMby0t6rqbeMPG0LtbBc4mk=; b=bBmlZ50xCoMvHwNsOkVPBsm778hEap3HdOViDSi9ZsphoAHX16ZxufZ2G1O5ucWDZx H0W4aXgqVn3OWdFzKCYoga4wO4bPIhfq4uHMcoZysdY1xOoU9jwn7zLPRcmLz+EeKDH9 3YUBbJcL70mBA6MPNnrFRleBpvc6Ek8BsUJfUJkZSvEPTqN3WNofqoZiz415Z2guCrQC oAezqYT0kbHkRz/8PJrJ0MmPxrbXZ8MZBUwGwbykWqhF5DC0GkS21vF7fzi9UTaYu0ab xXKskKtDLfktNoWrdUe4nO/8F0dOld3Z2P4BSOZBsDja5gZRuvVsAKGtmUpnBWp3qxAR l2wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741211258; x=1741816058; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UBIyGKwqkwmbXiC/dG5HVMby0t6rqbeMPG0LtbBc4mk=; b=H+yfN+CTEzz+wJRhYy8CgmGadGJXQDG5ryzkCycOScDsoar/bCyuocrSGJSewTnK8c AaVRgBe9jSz772AtXNCIeSmuEOf8jXcAIx5VqOPlVr29UIMpagnkLPz2Y6A48InZTDe2 Vf51LDiOi4qGNDg9AhVMZ92S4nxYc5bmb48YyGFp3xXryZVirC6mJ+4Ly0KOQiYDtF3e PEpctqVH582lLavHz3XIBUL+Twjz1huZrOwaXL8RiWomWuc52qb5DykQoHgfXuQfqFs1 dKaBjNnyYY0c8HKhYlCw0c2v1qnmKmfCPy+8BGj1M+4VqbJZNG05/4ehl3YsR1bUjjzi 2mMQ== X-Gm-Message-State: AOJu0Yxo8hY9OD5b8/++0IUOz7/O2a/uPeGdgWp7fDhlxQMkaR9LcDfK KK74zC5+iAEUr92Uw2rQK1jW6PUCmqw6XucrTpfZX938zgBz93b6l709ElVaMV6srEQ3ywPXpTE OnVADjZoPVX+ZbkyU8O+SA5cGOJFjKCJwXbo= X-Gm-Gg: ASbGncvWivdFBVtiB1JqOu3ujXfrNYDJ5mh1u8PMt5SiDBYVwf+mfeLnBPeMHDIFvop F3IxUo5UtqODIUPSyb9I7D9lO4WGtmJgzEIb84fsycxAV4RqjRS4oAI/B4c+iJRkV8henY+2JkI ve/lQ1SsksLDPzj3kx9W/3H8xioU4= X-Google-Smtp-Source: AGHT+IFP01NeRD5MS+U474bLjo3xLSH1cm93K+UEx7q3cKgEqhlwv5fh9WhDRsnKyrNKStHt9/hs8nwdt5iwIfgX5ao= X-Received: by 2002:a05:600c:314c:b0:439:9434:4f3b with SMTP id 5b1f17b1804b1-43bdb3a800bmr6707205e9.8.1741211257795; Wed, 05 Mar 2025 13:47:37 -0800 (PST) MIME-Version: 1.0 From: Artiom Balan <artiombalan331@HIDDEN> Date: Wed, 5 Mar 2025 23:47:26 +0200 X-Gm-Features: AQ5f1JqC7Ge-mROXAo6NEE88N5QPfD5ZBen2DL3n_eMxfRnyV62pH9P7IFSMM_I Message-ID: <CAA8c5q9Fv25U13s4LKnHm6hk21jdEJK8pr-zn-H2XVHSgXSnkw@HIDDEN> Subject: 29.4; Emacsclient doesn't display warnings emitted during daemon startup To: bug-gnu-emacs@HIDDEN Content-Type: multipart/alternative; boundary="0000000000007ffd65062f9f5643" Received-SPF: pass client-ip=2a00:1450:4864:20::32d; envelope-from=artiombalan331@HIDDEN; helo=mail-wm1-x32d.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 1.2 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Steps to reproduce: 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" 2. Notice the warning is displayed 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \ [...] Content analysis details: (1.2 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (artiombalan331[at]gmail.com) 1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (artiombalan331[at]gmail.com) -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2001:470:142:0:0:0:0:17 listed in] [list.dnswl.org] X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Wed, 05 Mar 2025 23:47:00 -0500 X-BeenThere: debbugs-submit <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> X-Spam-Score: 0.2 (/) --0000000000007ffd65062f9f5643 Content-Type: text/plain; charset="UTF-8" Steps to reproduce: 1. Run emacs: emacs -Q --eval "(display-warning 'type \"message\"))" 2. Notice the warning is displayed 3. Start emacs server: emacs -Q --fg-daemon --eval "(display-warning 'type \"message\"))" 4. Open a client: emacsclient -c 5. Notice the warning is not displayed I expected that the warnings buffer would be displayed in the exact same way in the emacsclient as in the first scenario. In GNU Emacs 29.4 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.48, cairo version 1.18.2) --0000000000007ffd65062f9f5643 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Steps to reproduce:<br>1. Run emacs: emacs -Q --eval "= ;(display-warning 'type \"message\"))"<br>2. Notice the = warning is displayed<br>3. Start emacs server: emacs -Q --fg-daemon --eval = "(display-warning 'type \"message\"))"<br>4. Open a= client: emacsclient -c<br>5. Notice the warning is not displayed<br><br>I = expected that the warnings buffer would be displayed in the exact<br>same w= ay in the emacsclient as in the first scenario.<br><br><br>In GNU Emacs 29.= 4 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.48,<br>cairo version 1.1= 8.2)</div> --0000000000007ffd65062f9f5643--
Artiom Balan <artiombalan331@HIDDEN>:bug-gnu-emacs@HIDDEN.
Full text available.bug-gnu-emacs@HIDDEN:bug#76772; Package emacs.
Full text available.
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd,
1994-97 Ian Jackson.