martin rudalics <rudalics@gmx.at> writes:

>> It was when byte comping emacs/lisp/leim/leim-list.el, so I just removed the
>> whole thing along with the quail library.  Then after than it was
>> another thing where it would just spam me with 'temacs' warnings, and
>> then segmentation fault.
>
> Does it happen while building Emacs?  Then I would do a bootstrap.  If
> the error persists, stash your changes, update from the repository and
> do git clean -xf.  If the error still happens with the next bootstrap,
> file a bug report.  Otherwise unstash your changes and build once more.

Ok, I tried building again, but this time with a new shallow clone, and
it worked fine.  But I got confused with which split-window.diff to
apply, and just ended up applying the same one.  This bug only happens
when building a second time, so I'll let it sleep for now.

>> Ok, I did that, and it now works fine.
>
> It's got one tiny bug: With 'window-resize-pixelwise' non-nil, you must
> not pass a float as SIZE to 'split-window'.  So please use
>
> (round split-size)
>
> in both calls.  Also, compiling currently gives
>
> In cycle-windows:
> window-transpose.el:203:29: Warning: ‘deepmap’ called with 1 argument, but
>     requires 2
> window-transpose.el:210:22: Warning: reference to free variable ‘atom-windows’

Fixed.  These errors were to do with cycle-windows.  Now I also updated
it so it gives message when it has atom or fixed size windows.

>> Also what do you want to happen with dedicated-windows in cycle-windows
>> command?  Technically it'll work fine, but it's unitutve as the user
>> gets the expression buffers have changed but window remains the same,
>> evo tho only windows have changed.
>
> You would have to tell me more about it.  Can you give me an example?
>

Ok, so cycle-windows is like other-window, expect you stay where you
are, and the windows move for you.