On 27 Aug 2010 19:33:36 +0100, Andy Koppe wrote:
It will be synced with the POSIX working directory again, except when
the path is too long or it's a virtual directory such as /proc.
Thank you for summarizing the thread. I tried
using the snapshot cygwin1-20100829.dll.bz2 and confirmed
2010/8/27 Charles Wilson:
On 8/27/2010 2:33 PM, Andy Koppe wrote:
On 27 August 2010 19:22, neomjp wrote:
2. I understand that the reason to have tcltk-20080420-1 as a win32 app is
to have a graphical insight that does not depend on X Window.
Cygwin programs can have Win32 interfaces
On 8/28/2010 10:31 AM, Reini Urban wrote:
2010/8/27 Charles Wilson:
Obviously git and
python-idle both work with X (on linux) so it's doable to convert --
just a nuisance.
A big nuisance in my eyes.
Why do I have to start a xserver, when I can use native fast small GDI?
Why do you have to
Charles Wilson schrieb:
On 8/28/2010 10:31 AM, Reini Urban wrote:
2010/8/27 Charles Wilson:
Obviously git and
python-idle both work with X (on linux) so it's doable to convert --
just a nuisance.
A big nuisance in my eyes.
Why do I have to start a xserver, when I can use native fast small
When I invoke gitk like this:
#
$ cygcheck -c cygwin git gitk tcltk
Cygwin Package Information
Package VersionStatus
cygwin 1.7.6-1OK
git 1.7.1-1OK
gitk 1.7.1-1
On 27 August 2010 19:22, neomjp wrote:
1. I see a long discussion about cygwin vs. win32 CWD is taking place in
cygwin-developer. What is win32 CWD going to be in cygwin in the future?
It will be synced with the POSIX working directory again, except when
the path is too long or it's a virtual
On 8/27/2010 2:33 PM, Andy Koppe wrote:
On 27 August 2010 19:22, neomjp wrote:
2. I understand that the reason to have tcltk-20080420-1 as a win32 app is
to have a graphical insight that does not depend on X Window.
Cygwin programs can have Win32 interfaces actually, as proven by the
likes
7 matches
Mail list logo
