Mail Archives: cygwin/2004/03/29/20:10:28
--=-GhvhI3HRWjlAuyX1Xl6e
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2004-03-30 at 10:56, Edward S. Peschko wrote:
> On Fri, Mar 26, 2004 at 10:12:05AM +0100, Corinna Vinschen wrote:
> yes, I realize that it is a problem with my environment - what I'm sugges=
ting
> is that no popups be created in response to the problem. That a text erro=
r is=20
> generated. This would vastly increase the robustness of the cygwin envir=
onment=20
> - I simply cannot afford to have an interactive error come up during a ba=
tch=20
> process, and hang there. It is not a question of specifics, its a question
> of how to deal with a generic problem.
Fix windows then. I'm sure MS will take a bug report happily.
Rob
P.S. I'm only being slightly facetious. This really is outside of
cygwin's purview. The only thing I can think of that might help is to
write a replace handler for these style of errors. And I don't know if
theres even a hook to do that.
--=20
GPG key available at: <http://www.robertcollins.net/keys.txt>.
--=-GhvhI3HRWjlAuyX1Xl6e
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBAaMjgI5+kQ8LJcoIRAmhoAKCNB7uZEG83F7R8zsSPKT0/UvAkpACcC5gi
F+VuC0DzCU3p3oaYIHsbR38=
=t0gT
-----END PGP SIGNATURE-----
--=-GhvhI3HRWjlAuyX1Xl6e--
- Raw text -