From: Gary Fredericks <fredericksgary@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 32720@debbugs.gnu.org
Subject: bug#32720: term-mode ignores certain window size changes
Date: Sun, 23 Dec 2018 07:47:23 -0600 [thread overview]
Message-ID: <CAMMdeLj_cU3Mho-oLqfpO8+UP4_HRisMnSo9yvVtfHeKGjJDRQ@mail.gmail.com> (raw)
In-Reply-To: <5C1F9038.30604@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
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 <rudalics@gmx.at> 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
>
[-- Attachment #2: Type: text/html, Size: 1667 bytes --]
next prev parent reply other threads:[~2018-12-23 13:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 12:09 bug#32720: term-mode ignores certain window size changes Gary Fredericks
2018-09-13 8:07 ` martin rudalics
2018-09-13 14:06 ` Eli Zaretskii
2018-09-14 8:32 ` martin rudalics
2018-11-04 9:56 ` martin rudalics
2018-11-16 12:15 ` Gary Fredericks
2018-11-16 12:57 ` martin rudalics
2018-11-16 13:15 ` Gary Fredericks
2018-11-18 9:22 ` martin rudalics
2018-11-16 14:45 ` Eli Zaretskii
2018-11-17 9:20 ` martin rudalics
2018-11-17 9:43 ` Eli Zaretskii
2018-11-17 18:40 ` martin rudalics
2018-11-18 3:30 ` Eli Zaretskii
2018-11-18 9:22 ` martin rudalics
2018-11-18 15:21 ` Eli Zaretskii
2018-11-18 19:37 ` martin rudalics
2018-11-18 20:10 ` Eli Zaretskii
2018-11-19 9:41 ` martin rudalics
2018-11-19 15:04 ` Gary Fredericks
2018-11-19 15:14 ` martin rudalics
2018-12-22 22:53 ` Gary Fredericks
2018-12-23 9:38 ` martin rudalics
2018-12-23 13:16 ` Gary Fredericks
2018-12-23 13:40 ` martin rudalics
2018-12-23 13:47 ` Gary Fredericks [this message]
2018-12-23 18:02 ` martin rudalics
2018-12-23 18:54 ` Gary Fredericks
2018-12-25 9:51 ` martin rudalics
2018-12-29 23:23 ` Gary Fredericks
2018-12-30 9:53 ` martin rudalics
2018-12-31 12:45 ` Gary Fredericks
2018-12-31 14:16 ` martin rudalics
2019-01-01 15:37 ` Gary Fredericks
2019-01-01 17:25 ` martin rudalics
2019-01-01 17:31 ` Gary Fredericks
2019-01-01 17:55 ` martin rudalics
2019-01-06 22:51 ` Gary Fredericks
2019-01-07 12:29 ` Gary Fredericks
2019-01-07 16:11 ` martin rudalics
2019-01-11 9:24 ` martin rudalics
2019-01-16 14:07 ` Gary Fredericks
2019-01-16 17:30 ` martin rudalics
2019-01-16 17:44 ` Gary Fredericks
2020-08-22 14:59 ` Lars Ingebrigtsen
2020-08-22 16:57 ` Gary Fredericks
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=CAMMdeLj_cU3Mho-oLqfpO8+UP4_HRisMnSo9yvVtfHeKGjJDRQ@mail.gmail.com \
--to=fredericksgary@gmail.com \
--cc=32720@debbugs.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.