Hi Brian,
May I suggest that you use these new tooltips on each package to display
the long descriptions.
Being able to view these descriptions from setup would be very handy.
Cheers,
Sebastien
signature.asc
Description: Digital signature
Hi guys,
Sorry for busting in...
Wouldn't putenv(CYGWIN=nontsec) possibly override a user's own CYGWIN
environment variable (I always set mine under HKLM)
Wouldn't it be preferable to check the existence of the CYGWIN
environment variable and simply append nontsec in this case?
my 2 cents.
On Fri, Oct 15, 2004 at 05:02:32PM -0400, Charles Wilson wrote:
Jean-Sebastien Trottier wrote:
I would say that what we already have is:
Tcl/Tk: half-Windows/half-Cygwin, GDI
Err...ok. If by this you mean
tcl: cygwin (no GUI), but it doesn't do cygwin paths correctly in all
On Fri, Oct 15, 2004 at 10:09:28AM +0200, Dr. Volker Zell wrote:
Jean-Sebastien Trottier writes:
Hi All (and Chris in particular),
I've already been successful in getting the following to compile as
native Cygwin packages with minimal patches:
Tcl v8.4.7 (without
On Fri, Oct 15, 2004 at 01:35:16PM -0400, Charles Wilson wrote:
In the interests of clarity, let's agree on some terminology:
a cygwin version --
uses the cygwin1.dll for runtime services (like printf etc)
a native windows version
uses msvcrt.dll for runtime services
an X version
Hi All (and Chris in particular),
The current Tcl and Tk packages are not native Cygwin apps but a mix
of UNIX and Windows flavors... are there any good reasons to keep it
this way?
Apart from getting Tk to work without X, I don't see any... If you want
Tk for Windows, might as well get it from
