On Mon, Dec 19, 2022 at 1:59 PM Jon Turney wrote:
> This seems to be an upstream problem with libX11 1.8.3
>
> I've withdrawn that version (so setup should automatically downgrade to
> the previous version, 1.8.1)
Thank you, Jon.
Yes Ken, the problems show up in Emacs 28.2
--
Jim Reisert AD1C
On 12/19/2022 4:05 PM, Ken Brown via Cygwin wrote:
On 12/19/2022 11:52 AM, Jim Reisert AD1C via Cygwin wrote:
I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
Cygwin" and in addition the X package refresh. I started emacs-X11 in
an xterm and am now seeing this in the console
On 12/19/2022 11:52 AM, Jim Reisert AD1C via Cygwin wrote:
I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
Cygwin" and in addition the X package refresh. I started emacs-X11 in
an xterm and am now seeing this in the console:
Xlib: sequence lost (0x1 > 0x16c) in reply ty
On 19/12/2022 16:52, Jim Reisert AD1C via Cygwin wrote:
I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
Cygwin" and in addition the X package refresh. I started emacs-X11 in
an xterm and am now seeing this in the console:
Xlib: sequence lost (0x1 > 0x16c) in reply type
I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
Cygwin" and in addition the X package refresh. I started emacs-X11 in
an xterm and am now seeing this in the console:
Xlib: sequence lost (0x1 > 0x16c) in reply type 0x13!
Xlib: sequence lost (0x1 > 0x172) in reply type
5 matches
Mail list logo