On Sat, 2 Feb 2002, Harold L Hunt wrote:
The problem is that XNextEvent () is a blocking function, just like Win32's
GetMessage () function. The problem here is when the X Server exits or
resets while XNextEvent () is blocking... in that case our X Client
(xwinclip) gets no notification
man XSetIOErrorHandler:
The XSetIOErrorHandler sets the fatal I/O error handler.
Xlib calls the program's supplied error handler if any
sort of system call error occurs (for example, the connec
tion to the server was lost). This is assumed to be a
On Sun, 3 Feb 2002, Brian Genisio wrote:
I am not sure that would be the best programming practice... (I could be wrong)
Wont that leave the IOErrorHandler function call still on the stack, causing
problems on multiple restarts of the server?
Or does that setjmp/longjmp change the
Please send your questions to [EMAIL PROTECTED]
Error can mean many things. Were your server up and running? Send further
replies to list.
Suhaib
-Original Message-
From: Eurico Covas [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 03, 2002 6:46 PM
To: [EMAIL PROTECTED];
Hi,
1.Our application has a problem writing to the serial port connected to the
modem.
The same application works fine on Linux.
2.The following is the open call for the serial port connected to the modem:
fd = open( device_name, O_RDWR | O_NONBLOCK );
3.The serial port has the following
Using setup-2002-01-27-1.exe I have noticed that the text in the
selection dialog is clipped. i.e. there appear to be ~3 pixels missing
from the top of the displayed text on my 1280x1024 display.
Haven't seen it reported so I thought I'd mention it.
Cheers
Don Sharp
--
Unsubscribe info:
How about adding a /dev/registry fhandler to Cygwin? Registry keys would be
directories and values in the registry files. I'm willing to try coding this
if people think it's a good idea. It allows shell scripts to easily access
registry keys as well as programs.
Regards
Chris
--
Unsubscribe
How about adding a /dev/registry fhandler to Cygwin? Registry keys would be
directories and values in the registry files. I'm willing to try coding this
if people think it's a good idea. It allows shell scripts to easily access
registry keys as well as programs.
Seems good to me, but it
This sounds like a GREAT idea to me.
How about adding a /dev/registry fhandler to Cygwin? Registry keys would
be
directories and values in the registry files. I'm willing to try coding
this
if people think it's a good idea. It allows shell scripts to easily access
registry keys as well as
Hi,
Chris January [EMAIL PROTECTED] wrtote:
How about adding a /dev/registry fhandler to Cygwin?
Registry keys would be directories and values in the
registry files.
UWIN (a commercial alternative to cygwin) has
something similar. See
http://www.research.att.com/sw/tools/uwin/
They use
On Sun, Feb 03, 2002 at 02:31:40PM -, Chris January wrote:
I doubt that either Corinna or I want to transcribe the book for this
mailing list. And, I'm pretty sure that neither of us has that much
experience with the routines in the book. I did play with the
implementation and realized that
/proc/registry/*
is a GREAT idea!
Sincerely,
Daniel Adams - [EMAIL PROTECTED]
http://dana.ucc.nau.edu/~dpa3
1 Peter 4:10 (NIV)- Each one should use whatever gift he has received to
serve others, faithfully administering God's grace in its various forms.
--
Unsubscribe info:
Daniel Adams wrote:
/proc/registry/*
is a GREAT idea!
Okay folks, enough with the me toos. Suffice it to say that everybody
thinks this is a wonderful idea. Not surprisingly, the suggestion of a
/dev/registry or /proc/registry HAS been made before. And everybody
thought it was a
On Sun, Feb 03, 2002 at 02:15:50PM -0500, Charles Wilson wrote:
Daniel Adams wrote:
/proc/registry/*
is a GREAT idea!
Okay folks, enough with the me toos. Suffice it to say that
everybody thinks this is a wonderful idea. Not surprisingly, the
suggestion of a /dev/registry or /proc/registry
(*) P.S. back then somebody mentioned a few problems with
file-system
access to registry entries: how do you deal with the various types --
DWORD, BINARY, STRING, (and the other types that AREN'T accessible via
regedit...) Just something to keep in mind, if somebody actually tries
to write
I have found a workaround. Just change your rxvt line to read:
rxvt -geometry 80x60 -e cmd /c c:\cygwin\bin\bash --login -i
This is assuming you're running 2000, ME, or XP. I don't know about 9x.
You can look for a command.com option that does the same thing as /c for
cmd.exe. (Runs a command
Am 2 Feb 2002 um 17:58 hat Rhet Turnbull geschrieben:
Gerrit P. Haase wrote:
Why? Where is docu about this?
The perl documentation for $^S in the perlvar manpage states:
$^S Current state of the interpreter. Undefined if
parsing of the current module/eval is not finished
On Sun, Feb 03, 2002 at 10:03:36PM +0100, Gerrit P. Haase wrote:
Am 2 Feb 2002 um 17:58 hat Rhet Turnbull geschrieben:
Gerrit P. Haase wrote:
Why? Where is docu about this?
The perl documentation for $^S in the perlvar manpage states:
$^S Current state of the interpreter. Undefined if
Since upgrading from cygwin-1.3.2, I've noticed that sh always causes
Invalid Page Fault when executing .com files.
The crash is 100% reproduceable on difference machines running Win98 and
cygwin 1.3.3 or higher:
C:\windowssh
$more.com /?
At this point, a IPF will be generated, with
I can't recreate the problem under WinXP. Try putting your VIM and Cygwin
directories at the front of the path instead of the back to see if that
makes a difference.
It might be interesting to see if the problem occurs under bash or tcsh as
well.
--
Mac :})
** I normally forward private
On Saturday 02 February 2002 13:02, Arek wrote:
Okay, On a whim, I decided to upgrade to GCC 3.0.3 on my box. Following
David Billinghurst's instructions, everything went fine until 'make
install', where it failed with the following error:
make[1]: Entering directory
I've tried your suggestion of changing the path order, but IPF still occurs.
On the other hand, bash and tcsh cause no problems.
Timothy
I can't recreate the problem under WinXP. Try putting your VIM and Cygwin
directories at the front of the path instead of the back to see if that
makes
/proc/registry/*
is a GREAT idea!
(*) P.S. back then somebody mentioned a few problems with file-system
access to registry entries: how do you deal with the various types --
DWORD, BINARY, STRING, (and the other types that AREN'T accessible
via regedit...)
Why not use a file name
23 matches
Mail list logo
