On Tue, 27 Aug 2002, Nicholas Wourms wrote:
Well tell your emacs people that they'll just have to download the
same way we all do. If they want a pretty package, they can use
Xemacs. Is the install really that big for emacs people? After all,
if you want simplicity, use vi. It only
On Tue, 27 Aug 2002, Harold L Hunt II wrote:
Joe,
I agree, it would be nice if Cygwin/XFree86 packages were able to allow
the user to pick-and-choose elements at a more fine-grained level.
The current scheme is good, but has one bug.
The shared libraries are not in lib, but in bin. I'll
I have been trying to use Cygwin/XFree86 to run HP Openview. I start XWin
with the -query to log into the Solaris system that OV runs on and
everything seems to run fine, better than with the release of Hummingbird's
Exceed that I have. However, the right mouse button doesn't work in any
On Wed, 28 Aug 2002, Traxler, Gene W wrote:
I have been trying to use Cygwin/XFree86 to run HP Openview. I start XWin
with the -query to log into the Solaris system that OV runs on and
everything seems to run fine, better than with the release of Hummingbird's
Exceed that I have. However,
Here are the two events from pressing the right mouse button. I assumed
that you didn't want all of the motion and other events.
ButtonPress event, serial 17, synthetic NO, window 0x41,
root 0x36, subw 0x0, time 10973308, (27,95), root:(581,377),
state 0x0, button 3, same_screen YES
xterm displays a VT Fonts menu when I hold down CTRL and right click. So
far, the only program that I am having trouble with is HP OpenView. The
rest of the CDE 1.3 environment appears to work normally although I haven't
tested a lot of other programs (Netscape, various CDE desktop functions,
Hi All,
I posted last week that I had a possible solution to the xwinclip selection
behaviour. I didn't get any feedback so I endeavoured to do it anyway. So
this ones a bit long but it's an explanation of how I've got it working ..
Basic premise :
Use a seperate dll that runs a system
I think the goal in the not-too-far-away-future is to have xwinclip
integrated directly inside the XWin app. This would save you the trouble
to use SetWindowsHookEx, which IIRC is a big piece of crap. Also, this
would save you the trouble of killing xwinclip while XWin is still running.
