all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21777@debbugs.gnu.org, schwab@linux-m68k.org, dima@secretsauce.net
Subject: bug#21777: 25.0.50; gud-gdb uses a pager, which is harmful inside emacs
Date: Wed, 23 Sep 2020 17:41:06 +0300	[thread overview]
Message-ID: <83mu1gv9ml.fsf@gnu.org> (raw)
In-Reply-To: <87y2l0d57i.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  23 Sep 2020 14:53:53 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: dima@secretsauce.net,  21777@debbugs.gnu.org,  schwab@linux-m68k.org
> Date: Wed, 23 Sep 2020 14:53:53 +0200
> 
> But I'm still not sure this is actually what is going on, because I'm
> just not finding exactly where this happens.  For instance,
> `window--adjust-process-windows' is never called in buffers started with
> `M-x gud-gdb'...  and adjusting the frame size in a buffer started with
> `M-x gdb' does not make gdb switch the pager on.  

The value of window-adjust-process-window-size-function in the GUD
buffer is window-adjust-process-window-size-smallest.  Did you try to
trace that function?

> Grepping for SIGWINCH doesn't immediately give me any clues, either.

We don't send SIGWINCH, we use IOCTL, AFAIR.





  reply	other threads:[~2020-09-23 14:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 19:20 bug#21777: 25.0.50; gud-gdb uses a pager, which is harmful inside emacs Dima Kogan
2015-10-28 22:27 ` Andreas Schwab
2015-10-28 22:57   ` Dima Kogan
2015-10-29 16:16     ` Eli Zaretskii
2015-10-29 22:58       ` Dima Kogan
2015-10-30  3:43         ` Dima Kogan
2015-10-30  8:17           ` Eli Zaretskii
2015-10-30  9:13             ` Dima Kogan
2015-10-30  9:32               ` Eli Zaretskii
2015-10-30 14:01                 ` Eli Zaretskii
2015-10-30 19:05                   ` Dima Kogan
2015-10-30 20:34                     ` Eli Zaretskii
2020-09-20 21:18                 ` Lars Ingebrigtsen
2020-09-21 14:03                   ` Eli Zaretskii
2020-09-21 14:07                     ` Lars Ingebrigtsen
2020-09-22 15:46                       ` Eli Zaretskii
2020-09-22 15:51                         ` Lars Ingebrigtsen
2020-09-22 15:57                           ` Andreas Schwab
2020-09-22 16:09                           ` Eli Zaretskii
2020-09-22 16:19                             ` Andreas Schwab
2020-09-22 16:51                               ` Eli Zaretskii
2020-09-22 17:18                                 ` Andreas Schwab
2020-09-22 17:39                                   ` Eli Zaretskii
2020-09-22 17:46                                     ` Andreas Schwab
2020-09-23 12:53                             ` Lars Ingebrigtsen
2020-09-23 14:41                               ` Eli Zaretskii [this message]
2020-09-24 14:15                                 ` Lars Ingebrigtsen
2020-09-24 15:06                                   ` Eli Zaretskii
2020-09-25  9:55                                     ` Lars Ingebrigtsen
2020-09-24 14:16                               ` Eli Zaretskii
2020-09-24 14:29                                 ` Lars Ingebrigtsen
2020-09-24 15:08                                   ` Eli Zaretskii
2015-10-30  7:54         ` Eli Zaretskii
2019-09-29 21:49 ` Stefan Kangas

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=83mu1gv9ml.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21777@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    --cc=larsi@gnus.org \
    --cc=schwab@linux-m68k.org \
    /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.