* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
[not found] ` <20241219091511.B84DEC022CC@vcs3.savannah.gnu.org>
@ 2024-12-19 11:00 ` Stefan Kangas
2024-12-19 11:25 ` Gerd Möllmann
2024-12-19 12:44 ` Gerd Möllmann
2024-12-19 11:37 ` Michael Albinus
1 sibling, 2 replies; 13+ messages in thread
From: Stefan Kangas @ 2024-12-19 11:00 UTC (permalink / raw)
To: Gerd Moellmann, emacs-devel
Gerd Moellmann <gerd@gnu.org> writes:
> branch: master
> commit 8aef5d224a6fccb675729748836d5ebfdcfa1101
> Merge: ea865c98cf3 6fa2050ee76
> Author: Gerd Möllmann <gerd@gnu.org>
> Commit: Gerd Möllmann <gerd@gnu.org>
>
> Merge branch 'scratch/tty-child-frames'
>
> Add support for child frames on tty
>
> The redisplay part is complete. The frame-handling part supports
> use-cases like Posframe, Corfu, and child frames acting like tooltips.
> Other use-cases of child frames are not currently supported. In
> particular, trying to create minibuffer-only child frames on ttys will
> signal an error.
Very nice, thank you! And congratulations.
I can't find anything about this in NEWS, though.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 11:00 ` master 8aef5d224a6: Merge branch 'scratch/tty-child-frames' Stefan Kangas
@ 2024-12-19 11:25 ` Gerd Möllmann
2024-12-19 12:44 ` Gerd Möllmann
1 sibling, 0 replies; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 11:25 UTC (permalink / raw)
To: Stefan Kangas; +Cc: Gerd Moellmann, emacs-devel
Stefan Kangas <stefankangas@gmail.com> writes:
> Gerd Moellmann <gerd@gnu.org> writes:
>
>> branch: master
>> commit 8aef5d224a6fccb675729748836d5ebfdcfa1101
>> Merge: ea865c98cf3 6fa2050ee76
>> Author: Gerd Möllmann <gerd@gnu.org>
>> Commit: Gerd Möllmann <gerd@gnu.org>
>>
>> Merge branch 'scratch/tty-child-frames'
>>
>> Add support for child frames on tty
>>
>> The redisplay part is complete. The frame-handling part supports
>> use-cases like Posframe, Corfu, and child frames acting like tooltips.
>> Other use-cases of child frames are not currently supported. In
>> particular, trying to create minibuffer-only child frames on ttys will
>> signal an error.
>
> Very nice, thank you! And congratulations.
Thanks, one thing less to try to not forget :-). Or two actually, with
the not pausing for input, even better.
> I can't find anything about this in NEWS, though.
I'll add one real soon now (tm). Need to synchronize with GNU first.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
[not found] ` <20241219091511.B84DEC022CC@vcs3.savannah.gnu.org>
2024-12-19 11:00 ` master 8aef5d224a6: Merge branch 'scratch/tty-child-frames' Stefan Kangas
@ 2024-12-19 11:37 ` Michael Albinus
2024-12-19 11:59 ` Gerd Möllmann
1 sibling, 1 reply; 13+ messages in thread
From: Michael Albinus @ 2024-12-19 11:37 UTC (permalink / raw)
To: emacs-devel; +Cc: Gerd Möllmann
Gerd Moellmann <gerd@gnu.org> writes:
Hi Gerd,
> Merge branch 'scratch/tty-child-frames'
>
> Add support for child frames on tty
This breaks xt-mouse-tests:
--8<---------------cut here---------------start------------->8---
# make -C test xt-mouse-tests
Test xt-mouse-tracking-basic condition:
(error "tty frame should be used")
FAILED 1/3 xt-mouse-tracking-basic (0.776520 sec) at lisp/xt-mouse-tests.el:61
Test xt-mouse-tracking-sgr condition:
(error "tty frame should be used")
FAILED 2/3 xt-mouse-tracking-sgr (0.000466 sec) at lisp/xt-mouse-tests.el:102
Test xt-mouse-tracking-utf-8 condition:
(error "tty frame should be used")
FAILED 3/3 xt-mouse-tracking-utf-8 (0.000746 sec) at lisp/xt-mouse-tests.el:80
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 11:37 ` Michael Albinus
@ 2024-12-19 11:59 ` Gerd Möllmann
2024-12-19 12:46 ` Eli Zaretskii
0 siblings, 1 reply; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 11:59 UTC (permalink / raw)
To: Michael Albinus; +Cc: emacs-devel
Michael Albinus <michael.albinus@gmx.de> writes:
> Gerd Moellmann <gerd@gnu.org> writes:
>
> Hi Gerd,
>
>> Merge branch 'scratch/tty-child-frames'
>>
>> Add support for child frames on tty
>
> This breaks xt-mouse-tests:
>
> --8<---------------cut here---------------start------------->8---
> # make -C test xt-mouse-tests
> Test xt-mouse-tracking-basic condition:
> (error "tty frame should be used")
> FAILED 1/3 xt-mouse-tracking-basic (0.776520 sec) at lisp/xt-mouse-tests.el:61
> Test xt-mouse-tracking-sgr condition:
> (error "tty frame should be used")
> FAILED 2/3 xt-mouse-tracking-sgr (0.000466 sec) at lisp/xt-mouse-tests.el:102
> Test xt-mouse-tracking-utf-8 condition:
> (error "tty frame should be used")
> FAILED 3/3 xt-mouse-tracking-utf-8 (0.000746 sec) at lisp/xt-mouse-tests.el:80
> --8<---------------cut here---------------end--------------->8---
>
> Best regards, Michael.
Hi Michael,
The new code now _requires_ a tty frame to be used (decode_tty_frame,
check_tty), which I think the tests can't provide, running in batch. And
I'd rather not be less picky for the sake of these tests.
Kind of a predicament. Any idea what could be done?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 11:00 ` master 8aef5d224a6: Merge branch 'scratch/tty-child-frames' Stefan Kangas
2024-12-19 11:25 ` Gerd Möllmann
@ 2024-12-19 12:44 ` Gerd Möllmann
2024-12-19 14:50 ` Robert Pluim
1 sibling, 1 reply; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 12:44 UTC (permalink / raw)
To: Stefan Kangas; +Cc: Gerd Moellmann, emacs-devel
Stefan Kangas <stefankangas@gmail.com> writes:
> Gerd Moellmann <gerd@gnu.org> writes:
>
>> branch: master
>> commit 8aef5d224a6fccb675729748836d5ebfdcfa1101
>> Merge: ea865c98cf3 6fa2050ee76
>> Author: Gerd Möllmann <gerd@gnu.org>
>> Commit: Gerd Möllmann <gerd@gnu.org>
>>
>> Merge branch 'scratch/tty-child-frames'
>>
>> Add support for child frames on tty
>>
>> The redisplay part is complete. The frame-handling part supports
>> use-cases like Posframe, Corfu, and child frames acting like tooltips.
>> Other use-cases of child frames are not currently supported. In
>> particular, trying to create minibuffer-only child frames on ttys will
>> signal an error.
>
> Very nice, thank you! And congratulations.
>
> I can't find anything about this in NEWS, though.
Now done, but it would be nice if someone could check if that's
sufficient and so on.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 11:59 ` Gerd Möllmann
@ 2024-12-19 12:46 ` Eli Zaretskii
2024-12-19 13:19 ` Gerd Möllmann
0 siblings, 1 reply; 13+ messages in thread
From: Eli Zaretskii @ 2024-12-19 12:46 UTC (permalink / raw)
To: Gerd Möllmann; +Cc: michael.albinus, emacs-devel
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 19 Dec 2024 12:59:44 +0100
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> > Gerd Moellmann <gerd@gnu.org> writes:
> >
> > Hi Gerd,
> >
> >> Merge branch 'scratch/tty-child-frames'
> >>
> >> Add support for child frames on tty
> >
> > This breaks xt-mouse-tests:
> >
> > --8<---------------cut here---------------start------------->8---
> > # make -C test xt-mouse-tests
> > Test xt-mouse-tracking-basic condition:
> > (error "tty frame should be used")
> > FAILED 1/3 xt-mouse-tracking-basic (0.776520 sec) at lisp/xt-mouse-tests.el:61
> > Test xt-mouse-tracking-sgr condition:
> > (error "tty frame should be used")
> > FAILED 2/3 xt-mouse-tracking-sgr (0.000466 sec) at lisp/xt-mouse-tests.el:102
> > Test xt-mouse-tracking-utf-8 condition:
> > (error "tty frame should be used")
> > FAILED 3/3 xt-mouse-tracking-utf-8 (0.000746 sec) at lisp/xt-mouse-tests.el:80
> > --8<---------------cut here---------------end--------------->8---
> >
> > Best regards, Michael.
>
> Hi Michael,
>
> The new code now _requires_ a tty frame to be used (decode_tty_frame,
> check_tty), which I think the tests can't provide, running in batch. And
> I'd rather not be less picky for the sake of these tests.
Why is that a problem? A batch session does have a frame, you just
need to account for that. I think the test that emits the error is
too strict, and should be relaxed when noninteractive is non-zero. Or
maybe invert the test and check for !FRAME_WINDOW_P (which would then
allow the frame that exists in the batch session).
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 12:46 ` Eli Zaretskii
@ 2024-12-19 13:19 ` Gerd Möllmann
2024-12-19 13:28 ` Eli Zaretskii
0 siblings, 1 reply; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 13:19 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: michael.albinus, emacs-devel
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 19 Dec 2024 12:59:44 +0100
>>
>> Michael Albinus <michael.albinus@gmx.de> writes:
>>
>> > Gerd Moellmann <gerd@gnu.org> writes:
>> >
>> > Hi Gerd,
>> >
>> >> Merge branch 'scratch/tty-child-frames'
>> >>
>> >> Add support for child frames on tty
>> >
>> > This breaks xt-mouse-tests:
>> >
>> > --8<---------------cut here---------------start------------->8---
>> > # make -C test xt-mouse-tests
>> > Test xt-mouse-tracking-basic condition:
>> > (error "tty frame should be used")
>> > FAILED 1/3 xt-mouse-tracking-basic (0.776520 sec) at lisp/xt-mouse-tests.el:61
>> > Test xt-mouse-tracking-sgr condition:
>> > (error "tty frame should be used")
>> > FAILED 2/3 xt-mouse-tracking-sgr (0.000466 sec) at lisp/xt-mouse-tests.el:102
>> > Test xt-mouse-tracking-utf-8 condition:
>> > (error "tty frame should be used")
>> > FAILED 3/3 xt-mouse-tracking-utf-8 (0.000746 sec) at lisp/xt-mouse-tests.el:80
>> > --8<---------------cut here---------------end--------------->8---
>> >
>> > Best regards, Michael.
>>
>> Hi Michael,
>>
>> The new code now _requires_ a tty frame to be used (decode_tty_frame,
>> check_tty), which I think the tests can't provide, running in batch. And
>> I'd rather not be less picky for the sake of these tests.
>
> Why is that a problem?
You mean why removing the checks (decode_tty_frame, check_tty) is a
problem?. My question is more what these tests bring tot he table that
outweighs removing checks.
> A batch session does have a frame, you just need to account for that.
I know it has an initial frame, which is neither a tty nor a window
system frame. The idea of testing xt-mouse with that is, let's say,
interesting. And then that comment
;; FIXME: this doesn't work when called inside a non-batch mode Emacs
;; session.
> I think the test that emits the error is too strict, and should be
> relaxed when noninteractive is non-zero. Or maybe invert the test and
> check for !FRAME_WINDOW_P (which would then allow the frame that
> exists in the batch session).
I could maybe make check_tty not signal if noninteractive == true. I
guess that could make things work, one has to try, but it surely doesn't
win a beauty price :-(.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 13:19 ` Gerd Möllmann
@ 2024-12-19 13:28 ` Eli Zaretskii
0 siblings, 0 replies; 13+ messages in thread
From: Eli Zaretskii @ 2024-12-19 13:28 UTC (permalink / raw)
To: Gerd Möllmann; +Cc: michael.albinus, emacs-devel
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
> Date: Thu, 19 Dec 2024 14:19:20 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> The new code now _requires_ a tty frame to be used (decode_tty_frame,
> >> check_tty), which I think the tests can't provide, running in batch. And
> >> I'd rather not be less picky for the sake of these tests.
> >
> > Why is that a problem?
>
> You mean why removing the checks (decode_tty_frame, check_tty) is a
> problem?. My question is more what these tests bring tot he table that
> outweighs removing checks.
>
> > A batch session does have a frame, you just need to account for that.
>
> I know it has an initial frame, which is neither a tty nor a window
> system frame. The idea of testing xt-mouse with that is, let's say,
> interesting. And then that comment
That frame is very much like a tty frame, AFAIR. I suggest to try
relaxing the test and seeing if the xt-mouse tests then pass.
> > I think the test that emits the error is too strict, and should be
> > relaxed when noninteractive is non-zero. Or maybe invert the test and
> > check for !FRAME_WINDOW_P (which would then allow the frame that
> > exists in the batch session).
>
> I could maybe make check_tty not signal if noninteractive == true. I
> guess that could make things work, one has to try, but it surely doesn't
> win a beauty price :-(.
If it makes a test work, why not? We can even document this in a
comment.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 12:44 ` Gerd Möllmann
@ 2024-12-19 14:50 ` Robert Pluim
2024-12-19 14:58 ` Gerd Möllmann
2024-12-19 15:09 ` Eli Zaretskii
0 siblings, 2 replies; 13+ messages in thread
From: Robert Pluim @ 2024-12-19 14:50 UTC (permalink / raw)
To: Gerd Möllmann; +Cc: Stefan Kangas, Gerd Moellmann, emacs-devel
>>>>> On Thu, 19 Dec 2024 13:44:54 +0100, Gerd Möllmann <gerd.moellmann@gmail.com> said:
Gerd> Stefan Kangas <stefankangas@gmail.com> writes:
>> Gerd Moellmann <gerd@gnu.org> writes:
>>
>>> branch: master
>>> commit 8aef5d224a6fccb675729748836d5ebfdcfa1101
>>> Merge: ea865c98cf3 6fa2050ee76
>>> Author: Gerd Möllmann <gerd@gnu.org>
>>> Commit: Gerd Möllmann <gerd@gnu.org>
>>>
>>> Merge branch 'scratch/tty-child-frames'
>>>
>>> Add support for child frames on tty
>>>
>>> The redisplay part is complete. The frame-handling part supports
>>> use-cases like Posframe, Corfu, and child frames acting like tooltips.
>>> Other use-cases of child frames are not currently supported. In
>>> particular, trying to create minibuffer-only child frames on ttys will
>>> signal an error.
>>
>> Very nice, thank you! And congratulations.
>>
>> I can't find anything about this in NEWS, though.
Gerd> Now done, but it would be nice if someone could check if that's
Gerd> sufficient and so on.
I was thinking of sticking something like this on top. Do we need to
document the limitations there, such as no suport for minibuffer-only?
diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index bf4d5c05f3a..cc7d3f79a7f 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -3393,8 +3393,8 @@ Child Frames
By design, operations to make or modify child frames are implemented
with the help of frame parameters (@pxref{Frame Parameters}) without any
-specialized functions or customizable variables. Note that child frames
-are meaningful on graphical terminals only.
+specialized functions or customizable variables. Child frames
+are meaningful on graphical and text terminals.
To create a new child frame or to convert a normal frame into a child
frame, set that frame's @code{parent-frame} parameter (@pxref{Frame
Robert
--
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 14:50 ` Robert Pluim
@ 2024-12-19 14:58 ` Gerd Möllmann
2024-12-19 15:30 ` Robert Pluim
2024-12-19 15:09 ` Eli Zaretskii
1 sibling, 1 reply; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 14:58 UTC (permalink / raw)
To: Robert Pluim; +Cc: Stefan Kangas, Gerd Moellmann, emacs-devel
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Thu, 19 Dec 2024 13:44:54 +0100, Gerd Möllmann <gerd.moellmann@gmail.com> said:
>
> Gerd> Stefan Kangas <stefankangas@gmail.com> writes:
> >> Gerd Moellmann <gerd@gnu.org> writes:
> >>
> >>> branch: master
> >>> commit 8aef5d224a6fccb675729748836d5ebfdcfa1101
> >>> Merge: ea865c98cf3 6fa2050ee76
> >>> Author: Gerd Möllmann <gerd@gnu.org>
> >>> Commit: Gerd Möllmann <gerd@gnu.org>
> >>>
> >>> Merge branch 'scratch/tty-child-frames'
> >>>
> >>> Add support for child frames on tty
> >>>
> >>> The redisplay part is complete. The frame-handling part supports
> >>> use-cases like Posframe, Corfu, and child frames acting like tooltips.
> >>> Other use-cases of child frames are not currently supported. In
> >>> particular, trying to create minibuffer-only child frames on ttys will
> >>> signal an error.
> >>
> >> Very nice, thank you! And congratulations.
> >>
> >> I can't find anything about this in NEWS, though.
>
> Gerd> Now done, but it would be nice if someone could check if that's
> Gerd> sufficient and so on.
>
> I was thinking of sticking something like this on top. Do we need to
> document the limitations there, such as no suport for minibuffer-only?
>
> diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
> index bf4d5c05f3a..cc7d3f79a7f 100644
> --- a/doc/lispref/frames.texi
> +++ b/doc/lispref/frames.texi
> @@ -3393,8 +3393,8 @@ Child Frames
>
> By design, operations to make or modify child frames are implemented
> with the help of frame parameters (@pxref{Frame Parameters}) without any
> -specialized functions or customizable variables. Note that child frames
> -are meaningful on graphical terminals only.
> +specialized functions or customizable variables. Child frames
> +are meaningful on graphical and text terminals.
>
> To create a new child frame or to convert a normal frame into a child
> frame, set that frame's @code{parent-frame} parameter (@pxref{Frame
>
> Robert
Thanks!
Can't answer your question, but I just stumbled over the last paragraph
above. Changing a root to a child frame or vice versa is also not
supported on ttys.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 14:50 ` Robert Pluim
2024-12-19 14:58 ` Gerd Möllmann
@ 2024-12-19 15:09 ` Eli Zaretskii
1 sibling, 0 replies; 13+ messages in thread
From: Eli Zaretskii @ 2024-12-19 15:09 UTC (permalink / raw)
To: Robert Pluim; +Cc: gerd.moellmann, stefankangas, gerd, emacs-devel
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>, Gerd Moellmann <gerd@gnu.org>,
> emacs-devel@gnu.org
> Date: Thu, 19 Dec 2024 15:50:07 +0100
>
> I was thinking of sticking something like this on top.
Please do, and thanks.
> Do we need to document the limitations there, such as no suport for
> minibuffer-only?
No. It's in NEWS, and that is enough for now.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 14:58 ` Gerd Möllmann
@ 2024-12-19 15:30 ` Robert Pluim
2024-12-19 15:31 ` Gerd Möllmann
0 siblings, 1 reply; 13+ messages in thread
From: Robert Pluim @ 2024-12-19 15:30 UTC (permalink / raw)
To: Gerd Möllmann
Cc: Eli Zaretskii, Stefan Kangas, Gerd Moellmann, emacs-devel
>>>>> On Thu, 19 Dec 2024 17:09:03 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> I was thinking of sticking something like this on top.
Eli> Please do, and thanks.
Done
>> Do we need to document the limitations there, such as no suport for
>> minibuffer-only?
Eli> No. It's in NEWS, and that is enough for now.
>>>>> On Thu, 19 Dec 2024 15:58:50 +0100, Gerd Möllmann <gerd.moellmann@gmail.com> said:
Gerd> Can't answer your question, but I just stumbled over the last paragraph
Gerd> above. Changing a root to a child frame or vice versa is also not
Gerd> supported on ttys.
Iʼve put that in NEWS too.
Robert
--
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: master 8aef5d224a6: Merge branch 'scratch/tty-child-frames'
2024-12-19 15:30 ` Robert Pluim
@ 2024-12-19 15:31 ` Gerd Möllmann
0 siblings, 0 replies; 13+ messages in thread
From: Gerd Möllmann @ 2024-12-19 15:31 UTC (permalink / raw)
To: Robert Pluim
Cc: Eli Zaretskii, Stefan Kangas, Gerd Möllmann, Emacs Devel
> On 19. Dec 2024, at 16:30, Robert Pluim <rpluim@gmail.com> wrote:
>
>>>>>> On Thu, 19 Dec 2024 17:09:03 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
>>> I was thinking of sticking something like this on top.
>
> Eli> Please do, and thanks.
>
> Done
>
>>> Do we need to document the limitations there, such as no suport for
>>> minibuffer-only?
>
> Eli> No. It's in NEWS, and that is enough for now.
>
>>>>>> On Thu, 19 Dec 2024 15:58:50 +0100, Gerd Möllmann <gerd.moellmann@gmail.com> said:
>
> Gerd> Can't answer your question, but I just stumbled over the last paragraph
> Gerd> above. Changing a root to a child frame or vice versa is also not
> Gerd> supported on ttys.
>
> Iʼve put that in NEWS too.
>
> Robert
> --
Thansk!
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2024-12-19 15:31 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <173459970775.288909.12887171645975658795@vcs3.savannah.gnu.org>
[not found] ` <20241219091511.B84DEC022CC@vcs3.savannah.gnu.org>
2024-12-19 11:00 ` master 8aef5d224a6: Merge branch 'scratch/tty-child-frames' Stefan Kangas
2024-12-19 11:25 ` Gerd Möllmann
2024-12-19 12:44 ` Gerd Möllmann
2024-12-19 14:50 ` Robert Pluim
2024-12-19 14:58 ` Gerd Möllmann
2024-12-19 15:30 ` Robert Pluim
2024-12-19 15:31 ` Gerd Möllmann
2024-12-19 15:09 ` Eli Zaretskii
2024-12-19 11:37 ` Michael Albinus
2024-12-19 11:59 ` Gerd Möllmann
2024-12-19 12:46 ` Eli Zaretskii
2024-12-19 13:19 ` Gerd Möllmann
2024-12-19 13:28 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).