On 12/19/22 11:42, Corinna Vinschen via Cygwin wrote:
Actually, Google hasn't relaxed their filtering, rather the DNS record
of the cygwin.com domain was the culprit. It didn't have the required
(by Google) DKIM/SFP records. This has been rectified last week,
fortunately, so this shouldn't
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
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
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
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
On 12/19/22 2:42 PM, Corinna Vinschen via Cygwin wrote:
On Dec 19 12:50, David Standish via Cygwin wrote:
On 12/19/22, Kyle Marek via Cygwin wrote:
(CC'd the public mailing list for visibility of problems that may be
affecting others)
Hello,
Today I received an email from
On Dec 19 12:50, David Standish via Cygwin wrote:
> On 12/19/22, Kyle Marek via Cygwin wrote:
> > (CC'd the public mailing list for visibility of problems that may be
> > affecting others)
> >
> > Hello,
> >
> > Today I received an email from cygwin-boun...@cygwin.com with the
> > subject line of
ditto!
On Mon, Dec 19, 2022 at 9:51 AM David Standish via Cygwin
wrote:
> On 12/19/22, Kyle Marek via Cygwin wrote:
> > (CC'd the public mailing list for visibility of problems that may be
> > affecting others)
> >
> > Hello,
> >
> > Today I received an email from cygwin-boun...@cygwin.com
On 12/19/22, Kyle Marek via Cygwin wrote:
> (CC'd the public mailing list for visibility of problems that may be
> affecting others)
>
> Hello,
>
> Today I received an email from cygwin-boun...@cygwin.com with the
> subject line of "You have been unsubscribed from the Cygwin mailing
> list". I
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
(CC'd the public mailing list for visibility of problems that may be
affecting others)
Hello,
Today I received an email from cygwin-boun...@cygwin.com with the
subject line of "You have been unsubscribed from the Cygwin mailing
list". I also just noticed that my Cygwin directory doesn't have
>>> In a gcc build script terminating with the instruction
>>> gcc -w -static -o myexe -O3 ./myarchive.a -lreadline -lncurses -lm
>>> I have suddenly started getting very many instances of both of
>>> ld: /usr/src/debug/readline-8.2-2/terminal.c:nn various: undefined
>>> reference to
On Dec 18 10:18, Christoph Reiter via Cygwin wrote:
> After the upgrade to 3.4 (disclaimer: in MSYS2) I'm seeing, and getting
> reports
> of, various things failing in Docker only, for example:
>
> 1 [main] pacman 252 child_copy: dll data read copy failed,
> 0x7FF8C816C000..0x7FF8C8178EB0,
13 matches
Mail list logo
