From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Gary Fredericks Newsgroups: gmane.emacs.bugs Subject: bug#32720: term-mode ignores certain window size changes Date: Sun, 23 Dec 2018 07:47:23 -0600 Message-ID: References: <5BDEC23D.4080707@gmx.at> <5BEEBECF.5060601@gmx.at> <835zwxulm5.fsf@gnu.org> <5BEFDD77.5080505@gmx.at> <83r2fkt4ye.fsf@gnu.org> <5BF06081.9060505@gmx.at> <83ftvzt63h.fsf@gnu.org> <5BF12F60.8020004@gmx.at> <83d0r2tnra.fsf@gnu.org> <5BF1BF63.6000307@gmx.at> <835zwutad4.fsf@gnu.org> <5BF28538.1080008@gmx.at> <5BF2D369.20806@gmx.at> <5C1F57A5.4040704@gmx.at> <5C1F9038.30604@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000000acba9057db0b95a" X-Trace: blaine.gmane.org 1545572767 10829 195.159.176.226 (23 Dec 2018 13:46:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Dec 2018 13:46:07 +0000 (UTC) Cc: 32720@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Dec 23 14:46:03 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gb44x-0002iR-4z for geb-bug-gnu-emacs@m.gmane.org; Sun, 23 Dec 2018 14:46:03 +0100 Original-Received: from localhost ([::1]:56280 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gb473-0005BE-JF for geb-bug-gnu-emacs@m.gmane.org; Sun, 23 Dec 2018 08:48:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gb46w-0005Aw-9h for bug-gnu-emacs@gnu.org; Sun, 23 Dec 2018 08:48:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gb46r-0008Ed-Vw for bug-gnu-emacs@gnu.org; Sun, 23 Dec 2018 08:48:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:56349) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gb46r-0008ER-RX for bug-gnu-emacs@gnu.org; Sun, 23 Dec 2018 08:48:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gb46r-0000dN-Le for bug-gnu-emacs@gnu.org; Sun, 23 Dec 2018 08:48:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gary Fredericks Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 23 Dec 2018 13:48:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32720 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32720-submit@debbugs.gnu.org id=B32720.15455728632411 (code B ref 32720); Sun, 23 Dec 2018 13:48:01 +0000 Original-Received: (at 32720) by debbugs.gnu.org; 23 Dec 2018 13:47:43 +0000 Original-Received: from localhost ([127.0.0.1]:60607 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gb46Y-0000cp-LD for submit@debbugs.gnu.org; Sun, 23 Dec 2018 08:47:42 -0500 Original-Received: from mail-wm1-f54.google.com ([209.85.128.54]:34330) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gb46X-0000cZ-Le for 32720@debbugs.gnu.org; Sun, 23 Dec 2018 08:47:42 -0500 Original-Received: by mail-wm1-f54.google.com with SMTP id y185so17584133wmd.1 for <32720@debbugs.gnu.org>; Sun, 23 Dec 2018 05:47:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OakCp8nQK+jlu9GpI6mYwQClnrPLFZf65/ES98Wb/u8=; b=HerCJd2ZiyBQyStRyxi6JkfrC51/ki6wlbofQuiuZ5cjmFGUD0AtF01LhYcVyWoiBY YXxrrK0O1pIbSrgXUIogY7FWIOks5XU9O20vKFFfpELW9si4pw8rBgr3n1ki2W6o65oz sXJ8SLbZUaKlcvXtksOLaSZsdCX0rYv+mutwvmnNufx/X2hnI5SOdNsmlEK1dc6Xe1wN t0l3W33YgakE3/ACQQ9p0v1xIh4FHpKVALMoIJd8sACZwkVDGV4LJOPUtne7t9ER/DkQ nm95ZcPPBY+XNmGrgs5PMoxsXQfYh6ZdFAc2piBf+PYfW54q9kOIkeWhwA6zikjppsUX OvrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OakCp8nQK+jlu9GpI6mYwQClnrPLFZf65/ES98Wb/u8=; b=b9YtgbDPChkRwU3kEqRS4FnWQDCtClbxB6SsDt7zgL58YXmjKrWLOv6Oj2AAo5o1GO 6bUCr6fj4pM+jU6O+go7CKYPu9gxuyg05paiWXPqWyvOjz2hd+RLh31SteJ7WZnUyDRn bsYXog7E8YQ38iq2IY8BLJY2A7rwS9gyf4CQPtxY/xN1dpE4prUH4oL9CW5gdyGFmZl4 +x/UJJxSUItzkdz4GpRshOz37tKw5PqqoEYDyxHXWKXxohM1iMxM0liFB1WCgTqgxeRh YC2ZqSrqvOsr7jzRTc0rzFK6Fuj2RGd74fnfRBxxxoDPraADVHyEMIE24tUO8GRRVaoG HPgw== X-Gm-Message-State: AA+aEWY/7JrU8Xg1iGoOe4RIx/ObbzKEAqs4TWx89+u4WiCdM3Puo6W5 Jds2Lpi4jSpT1dXMEYjb7SqMmiCDGG5hqvfU/Q4= X-Google-Smtp-Source: AFSGD/XY52ugcMT7oqUMpcc0aNe4Olk5OL/cOHQnCawxUGKNX7Yh7PxkHQKX44C9tSxMAKC+Ymp/gFm4bSt1Wdub1Dw= X-Received: by 2002:a1c:410b:: with SMTP id o11mr9446100wma.109.1545572855760; Sun, 23 Dec 2018 05:47:35 -0800 (PST) In-Reply-To: <5C1F9038.30604@gmx.at> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:153784 Archived-At: --0000000000000acba9057db0b95a Content-Type: text/plain; charset="UTF-8" Yes, that does seem to fail. You're anticipating this will be fixed by the broader changes you alluded to earlier? Gary Fredericks (803)-295-0195 fredericksgary@gmail.com gfredericks.com On Sun, Dec 23, 2018 at 7:40 AM martin rudalics wrote: > > I don't quite understand "It might have problems when you show a process > > buffer in an existing window whose size you never change thereafter." > > I've been only guessing. 'window-size-change-functions' triggers only > after a window is created or changed size. It doesn't trigger when a > window gets another buffer. So for example the following scenario > should fail: > > (1) Show process output in a window. > > (2) Display another buffer in that window. > > (3) Change the width of the window. > > (4) Show the process output again in that window. > > I suppose (4) fails to communicate the new window width to the > process. If you now do > > (5) Change the window width again. > > everything should be OK. > > martin > --0000000000000acba9057db0b95a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, that does seem to fail.

You're anticipating this will be fixed by the broader changes you allu= ded to earlier?

Gary = Fredericks
(803)-295-0195
fredericksgary@gmail.com
gfredericks.com


On Sun, Dec 23, 2018= at 7:40 AM martin rudalics <rudalics= @gmx.at> wrote:
=C2=A0> I= don't quite understand "It might have problems when you show a pr= ocess
=C2=A0> buffer in an existing window whose size you never change thereaf= ter."

I've been only guessing.=C2=A0 'window-size-change-functions' t= riggers only
after a window is created or changed size.=C2=A0 It doesn't trigger whe= n a
window gets another buffer.=C2=A0 So for example the following scenario
should fail:

(1) Show process output in a window.

(2) Display another buffer in that window.

(3) Change the width of the window.

(4) Show the process output again in that window.

I suppose (4) fails to communicate the new window width to the
process.=C2=A0 If you now do

(5) Change the window width again.

everything should be OK.

martin
--0000000000000acba9057db0b95a--