Hello,
On Sat 12 Nov 2022 at 02:55AM +01, Vincent Lefevre wrote:
> Hi,
>
> On 2022-11-11 11:32:33 -0700, Sean Whitton wrote:
>> On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:
>> > On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
>> >> Are you able to test the patch? Let me know if
Hi,
On 2022-11-11 11:32:33 -0700, Sean Whitton wrote:
> On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:
> > On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
> >> Are you able to test the patch? Let me know if you need help getting an
> >> installable .deb. Thanks.
> >
> > Sorry, I
Hello,
On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:
> On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
>> Are you able to test the patch? Let me know if you need help getting an
>> installable .deb. Thanks.
>
> Sorry, I couldn't test it yet, first because of an uninstallable
>
On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
> Are you able to test the patch? Let me know if you need help getting an
> installable .deb. Thanks.
Sorry, I couldn't test it yet, first because of an uninstallable
package needed for the build because I couldn't upgrade libc6 yet
and I
> Date: Sat, 5 Nov 2022 13:54:54 -0700
> Cc: vinc...@vinc17.net, spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
> 1017...@bugs.debian.org
> From: Paul Eggert
>
> On 2022-11-04 00:00, Eli Zaretskii wrote:
> > We need to establish what is the
> > source of SIGHUP in these cases. "These cases"
Hello Vincent,
Are you able to test the patch? Let me know if you need help getting an
installable .deb. Thanks.
--
Sean Whitton
signature.asc
Description: PGP signature
> Date: Sun, 6 Nov 2022 11:44:43 -0800
> Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name,
> 58...@debbugs.gnu.org, 1017...@bugs.debian.org
> From: Paul Eggert
>
> On 2022-11-06 11:32, Eli Zaretskii wrote:
> > My question was whether in this scenario, since the parent Emacs
> >
On 2022-11-06 11:32, Eli Zaretskii wrote:
My question was whether in this scenario, since the parent Emacs
exits, the child Emacs can get SIGHUP, simply because its parent
exited and the read end of the PTY no longer exists.
Yes, my sense from the few experiments I tried, is that it's a
> Date: Sun, 6 Nov 2022 11:18:03 -0800
> Cc: a...@sdf.org, vinc...@vinc17.net, spwhit...@spwhitton.name,
> 58...@debbugs.gnu.org, 1017...@bugs.debian.org
> From: Paul Eggert
>
> On 2022-11-05 22:51, Eli Zaretskii wrote:
>
> > But is it possible for a program like Emacs to get SIGHUP in such a
On 2022-11-05 22:51, Eli Zaretskii wrote:
But is it possible for a program like Emacs to get SIGHUP in such a
situation, or is that highly improbable? We have standard streams of
the inferior Emacs process connected via PTYs to the parent process, I
believe -- does that deliver SIGHUP or
> Date: Sat, 5 Nov 2022 13:54:54 -0700
> Cc: vinc...@vinc17.net, spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
> 1017...@bugs.debian.org
> From: Paul Eggert
>
> On 2022-11-04 00:00, Eli Zaretskii wrote:
> > We need to establish what is the
> > source of SIGHUP in these cases. "These cases"
On 2022-11-04 00:00, Eli Zaretskii wrote:
We need to establish what is the
source of SIGHUP in these cases. "These cases" mean, AFAIU, the
situations where Emacs launched an async subprocess to do native
compilation (which is another Emacs process in a --batch session), and
the parent Emacs
Eli Zaretskii writes:
>> From: Andrea Corallo
>> Cc: Vincent Lefevre , spwhit...@spwhitton.name,
>> 58...@debbugs.gnu.org, 1017...@bugs.debian.org
>> Date: Thu, 03 Nov 2022 21:25:08 +
>>
>> AFAIU the Emacs subprocess we use to compile should behave like a
>> regular Emacs.
>
>
> From: Andrea Corallo
> Cc: Vincent Lefevre , spwhit...@spwhitton.name,
> 58...@debbugs.gnu.org, 1017...@bugs.debian.org
> Date: Thu, 03 Nov 2022 21:25:08 +
>
> AFAIU the Emacs subprocess we use to compile should behave like a
> regular Emacs.
Basically, you are saying that if the
Eli Zaretskii writes:
>> Date: Thu, 3 Nov 2022 11:13:08 +0100
>> From: Vincent Lefevre
>> Cc: spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
>> 1017...@bugs.debian.org
>>
>> On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote:
>> > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
>> >
> Date: Thu, 3 Nov 2022 11:13:08 +0100
> From: Vincent Lefevre
> Cc: spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
> 1017...@bugs.debian.org
>
> On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote:
> > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> > > > Signal 1 is SIGHUP, AFAIU.
On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote:
> > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> > > Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the
> > > middle of GC, I have no idea. Maybe ask the user what was he doing at
> > > that time. E.g., could that be a
> Cc: 58...@debbugs.gnu.org, 1017...@bugs.debian.org
> Date: Thu, 3 Nov 2022 04:00:46 +0100
> From: Vincent Lefevre
>
> On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> > Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the
> > middle of GC, I have no idea. Maybe ask the user
On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
> Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the
> middle of GC, I have no idea. Maybe ask the user what was he doing at
> that time. E.g., could that be a remote Emacs session?
No, it is on my local machine.
On 2022-11-02
19 matches
Mail list logo
