I upgraded to
CYGWIN_NT-5.0 UTIP011 1.3.12(0.54/3/2) 2002-07-03 16:42 i686 unknown
and now the problem has gone away; so the problem is fixed in the latest
version of the cygwin1 dll! Thanks for the help from all you people! Really
much much appreciated.
Regards,
Jaap-Henk
On Fri, 5 Jul 2002 18:46:08 +0200 David Starks-Browning <starksb(a)ebi.ac.uk>
writes:
On Friday 5 Jul 02, Jaap-Henk Hoepman writes:
>
> I'm using
> CYGWIN_NT-5.0 UTIP011 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown
Yes, I should have spotted that in your original message.
> i think this is the latest; i installed it only several weeks ago.
No, it is not the latest. The latest is 1.3.12. You might give that
a try first.
Regards,
David
On Fri, 5 Jul 2002 19:09:43 +0200 Andy Piper <andy(a)xemacs.org> writes:
> You're correct in assuming that (current-time-string) gives
the
> correct result
> always. However, i've never seen this behaviour with the native
> windows port of
> XEmacs, only with the cygwin version.... so why does only the
> windows version
> do-the-right-thing?
This is a known problem with cygwin which Phil Aston has provided a fix
for
but which the cygwin maintainers refuse to apply (or at least that was
the
status quo a few months ago). The problem is due to some inappropriate
uses
of win32 function calls in the cygwin dll.
andy
--
Jaap-Henk Hoepman | Come sail your ships around me
Dept. of Computer Science | And burn your bridges down
University of Twente | Nick Cave - "Ship Song"
Email: hoepman(a)cs.utwente.nl === WWW:
www.cs.utwente.nl/~hoepman
Phone: +31 53 4893795 === Secr: +31 53 4893770 === Fax: +31 53 4894590
PGP ID: 0xF52E26DD Fingerprint: 1AED DDEB C7F1 DBB3 0556 4732 4217 ABEF