From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org, rudalics@gmx.at
Subject: Re: Question about dubious code for terminal frames
Date: Mon, 02 Sep 2024 20:39:38 +0300 [thread overview]
Message-ID: <86zfoq6jl1.fsf@gnu.org> (raw)
In-Reply-To: <m2le0a6me5.fsf@pro2.fritz.box> (message from Gerd Möllmann on Mon, 02 Sep 2024 18:38:58 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: emacs-devel@gnu.org, rudalics@gmx.at
> Date: Mon, 02 Sep 2024 18:38:58 +0200
>
> >> We're taking past each other.
> >
> > Maybe. You were criticizing the existing code, which wasn't supposed
> > to handle child frames on TTYs, so I interpreted that as unrelated to
> > child frames, like a kind-of general critique of the design and
> > implementation of frame resizing on TTYs. And that was the context in
> > which I replied.
>
> And I said I wonder if one couldn't brew a make-frame, a normal frame,
> that also leads to the same problem. And you said here's a bug for that.
That bug was fixed. And it was triggered by SIGWINCH, not by other
calls that resize the frame.
next prev parent reply other threads:[~2024-09-02 17:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 9:04 Question about dubious code for terminal frames Gerd Möllmann
2024-09-02 9:10 ` Andreas Schwab
2024-09-02 9:48 ` Gerd Möllmann
2024-09-02 10:23 ` Andreas Schwab
2024-09-02 10:46 ` Gerd Möllmann
2024-09-02 11:44 ` Eli Zaretskii
2024-09-02 12:59 ` Gerd Möllmann
2024-09-02 13:17 ` Eli Zaretskii
2024-09-02 14:11 ` Gerd Möllmann
2024-09-02 14:35 ` Eli Zaretskii
2024-09-02 14:54 ` Gerd Möllmann
2024-09-02 15:31 ` Eli Zaretskii
2024-09-02 15:46 ` Gerd Möllmann
2024-09-02 15:55 ` Eli Zaretskii
2024-09-02 16:24 ` Gerd Möllmann
2024-09-02 16:35 ` Eli Zaretskii
2024-09-02 16:38 ` Gerd Möllmann
2024-09-02 17:39 ` Eli Zaretskii [this message]
2024-09-02 16:20 ` martin rudalics
2024-09-02 16:31 ` Gerd Möllmann
2024-09-02 17:32 ` martin rudalics
2024-09-02 18:02 ` Gerd Möllmann
2024-09-02 18:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zfoq6jl1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.