From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Question about dubious code for terminal frames Date: Mon, 02 Sep 2024 16:17:40 +0300 Message-ID: <86ed628aa3.fsf@gnu.org> References: <86wmju8em4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24148"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, rudalics@gmx.at To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 02 15:18:19 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sl6wk-00069Y-PG for ged-emacs-devel@m.gmane-mx.org; Mon, 02 Sep 2024 15:18:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sl6wD-00006J-P9; Mon, 02 Sep 2024 09:17:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sl6wC-0008SE-9c for emacs-devel@gnu.org; Mon, 02 Sep 2024 09:17:44 -0400 Original-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 ) id 1sl6wB-0006Au-NI; Mon, 02 Sep 2024 09:17:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=CO9lDef1ZBsaAxN0e034jZRqpKDWXjue03CUvv18EnA=; b=Av0tvV2IMFMj3OpIWfuT Fbp0KWJBuwGdhYGIVq4fySc2fBHAmMJtuV++1QBr+f+Ud3h/P2XNlaGu/bNRv9n5fJCkT6Wkl0+nM TEAI9CdV29srOE9f2ZxvdgdEt61xJsG8xzFFXAGfzlZZsYcraOMAJtT9DXvOE7BW7EyQMrYgG4Icg RLi+yqSbEOHfRRqKYfMNwoXN7SMJB9L6Z9ob1OoQHhVV42Yr0anIa05McJUDLZdertJF6iyUCQJfD A6ma951uEfcFn88YYJUP83rlMX6vbiGVHO38V8iti8suWlbhvcSTVtOfosRjDJFdc9/JvNVjRPnCi FOfBrkiAbBVcgw==; In-Reply-To: (message from Gerd =?utf-8?Q?M=C3=B6llmann?= on Mon, 02 Sep 2024 14:59:54 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:323289 Archived-At: > From: Gerd Möllmann > Cc: emacs-devel@gnu.org, rudalics@gmx.at > Date: Mon, 02 Sep 2024 14:59:54 +0200 > > Eli Zaretskii writes: > > > Did you consider SIGWINCH? Its handler also calls adjust_frame_size. > > Thanks, that would be this one, right? Right. > It also could know and set the terminal size, if get_tty_size can. > > How complicated. I guess I rather work around this for now :-). What exactly is the problem? Doesn't change_frame_size support child frames? > And I wonder if one could brew a make-frame with some suitable frame > parameters that lead to setting the terminal size to something that > leads to a later emacs_abort in cmcheckmagic during redisplay of another > frame on the same terminal :-). Someone already did, see bug#71289.