Yaakov S (Cygwin Ports) wrote: >> IMHO, that was not desirable. Eventually I could imagine X11 and >> Cygwin native versions of the same package. I liked this method of >> making the distinction. > > What does "Cygwin native" mean? If Cygwin is meant to be a POSIX > environment, then X11 should be the standard for GUI apps.
I won't argue the point (since I'd like to see better X11 support), but POSIX doesn't necessarily imply X11 support. However... What about console apps? When I was still using the X11 version, my /usr/X11R6/bin/vim linked in X11 libs, although /usr/bin/vim didn't. That way, vim -g did the right thing. And from a practical standpoint, notice my wording there. It's true that various inconveniences and performance issues eventually caused me to move away from using X for daily Cygwin work, though I used to use it almost exclusively. Perhaps X11 improvements could draw me back, but until they do I'd actually prefer a few more Cygwin-aware GUI apps that don't use X. I wouldn't mind grabbing these apps from /usr/win32native or whatever, but that doesn't change the fact that (at least at this point) X11 isn't for everybody. gsw
