bug#32720: term-mode ignores certain window size changes

[Gary Fredericks <fredericksgary@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]

That sounds plausible, I'll try that out.

Thanks!

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


On Wed, Jan 16, 2019 at 11:30 AM martin rudalics <rudalics@gmx.at> wrote:

>  > I tracked down my issue to this line in my configuration:
>  >
>  >
> https://github.com/gfredericks/dotfiles/blob/48c503319046517fc1767735d09fbb232ace12ba/base/.emacs.d/user/gfredericks-longrunning.el.symlink#L34
>  >
>  > I can see how it's related, since it's adding a
>  > window-configuration-change-hook, but I can't tell at a glance what's
> wrong
>  > with it. It's a function that tries to save the current window
>  > configuration to a variable each time it changes.
>
> ...
>
>  >>   > it complains about the minibuffer being active).
>
> The error seems to come from this wg function:
>
> (defun wg-error-on-active-minibuffer ()
>    "Throw an error when the minibuffer is active."
>    (when (active-minibuffer-window)
>      (error "Workgroup operations aren't permitted while the \
> minibuffer is active.")))
>
> 'window-configuration-change-hook' now conceptually runs after any
> resize operation which includes states where the minibuffer window is
> active.  FWIW the call sequence you encounter is
>
> stash-my-working-config -> wg-make-wconfig -> wg-ewtree->wtree ->
> wg-error-on-active-minibuffer
>
> so maybe you should not stash your working configuration when the
> minibuffer is active.
>
> martin
>

[-- Attachment #2: Type: text/html, Size: 2407 bytes --]