all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org,  rudalics@gmx.at
Subject: Re: Question about dubious code for terminal frames
Date: Mon, 02 Sep 2024 14:59:54 +0200	[thread overview]
Message-ID: <m2frqi8b3p.fsf@pro2.fritz.box> (raw)
In-Reply-To: <86wmju8em4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Sep 2024 14:44:03 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: martin rudalics <rudalics@gmx.at>
>> Date: Mon, 02 Sep 2024 11:04:02 +0200
>> 
>> In 3 places, among them adjust_frame_size, which is why I CC'd
>> Martin, Emacs sets the values of FrameRows/FrameCols.
>> 
>> AFAIU, these two values give the physical size of a terminal (screen,
>> window), as returned from the co and li escape sequences on termcap
>> frames. And I can't find code that tries to change the physical size of
>> the terminal, if that would even make sense in the first place :-). So
>> this doesn't make any sense to me.
>
> Did you consider SIGWINCH?  Its handler also calls adjust_frame_size.

Thanks, that would be this one, right?

static void
handle_window_change_signal (int sig)
{
  int width, height;
  struct tty_display_info *tty;

  /* The frame size change obviously applies to a single
     termcap-controlled terminal, but we can't decide which.
     Therefore, we resize the frames corresponding to each tty.
  */
  for (tty = tty_list; tty; tty = tty->next)
    {
      if (! tty->term_initted)
	continue;

      /* Suspended tty frames have tty->input == NULL avoid trying to
	 use it.  */
      if (!tty->input)
	continue;

      get_tty_size (fileno (tty->input), &width, &height);

      if (width > 5 && height > 2)
	{
	  Lisp_Object tail, frame;

	  FOR_EACH_FRAME (tail, frame)
	    {
	      struct frame *f = XFRAME (frame);

	      if (FRAME_TERMCAP_P (f) && FRAME_TTY (f) == tty)
		/* Record the new sizes, but don't reallocate the data
		   structures now.  Let that be done later outside of the
		   signal handler.  */
		change_frame_size (f, width, height, false, true, false);
	    }
	}
    }
}

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 :-).

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 :-).




  reply	other threads:[~2024-09-02 12:59 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 [this message]
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
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=m2frqi8b3p.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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.