Howdy Harold...
..
You may still be correct with your worries, I'm sure there's a file
descriptor
that the OS is dup2()'ing there you don't want. FWIW I'm execl()'ing
/bin/sh -c command string
Hmm... that is a good point. We have the Win32 message queue file
handle open, a feature
Howdy Harold...
At 10:40 PM 8/6/2003 -0400, you wrote:
c) Replaces %display% with 127.0.0.1:display.0 in commands
Huh, I was going to say that %display% should be replaced with
127.0.0.1:0.0, but then I remembered that we know the 0.0, but we
don't know that the user connected via 127.0.0.1.
Igor,
Igor Pechtchanski wrote:
Two small notes here:
1) You can actually call setenv(DISPLAY, value) inside the XWin process,
Umm, make that {char buf[80]=DISPLAY=;putenv(strcat(buf,value));}
Sorry. The point remains, however.
which will be
On Wed, Aug 06, 2003 at 01:06:55PM -0400, Harold L Hunt II wrote:
The for loop that you have is the way I have seen it done before.
Me too. However, if you can find an API specification for something
which does something similar in the Single Unix Specification, I'd be
happy to implement it in
Earle F. Philhower III wrote:
The most recent patch looks pretty good from your description.
c) Replaces %display% with 127.0.0.1:display.0 in commands
Huh, I was going to say that %display% should be replaced with
127.0.0.1:0.0, but then I remembered that we know the 0.0, but we
don't know
Howdy Harold,
At 06:13 PM 8/10/2003 -0400, you wrote:
Should we change the file prefixes to something along the lines of
winprefs then?
Done in the attached patch, you'll want to
rm winmultiwindowprefs.[cho] winmultiwindowyacc.[ycho]
winmultiwindowlex.[lco]
to get rid of the old files. The
On Wed, 6 Aug 2003, Earle F. Philhower III wrote:
The started
app sees all ENV variables that XWin.exe saw at startup, so if you set
your DISPLAY before starting XWin you don't need the -display x.x.x.x:y.y
options.
Don't rely on that. At our company many people are using just XWin and no
Howdy Harold,
At 12:58 PM 8/10/2003 -0400, you wrote:
I have committed your patch to my local tree. However, I wonder why all
of the files are prefixed with winmultiwindow. Is the code purely
intended only for multiwindow modes? If so, that is fine. It not,
perhaps we should rebrand this
Earle F. Philhower III wrote:
Howdy Harold...
At 09:30 AM 8/6/2003 -0400, you wrote:
That is really the problem: the machines don't die; they just freeze.
So I have a computer sitting here that I can't keep my hands off but
it randomly freezes between a couple of times an hour and once every
On Wed, Aug 06, 2003 at 07:24:32PM -0700, Earle F. Philhower III wrote:
Howdy Christopher...
At 09:57 PM 8/6/2003 -0400, you wrote:
a) Closes all fds on the fork()'d process
It *may* be helpful to call setsid() at this point, after you've closed
the file descriptors.
I'm not really up on
Hi Harold,
If my IP is w.x.y.z vs. my loopback of 127.0.0.1, how is one of these
using unix domain sockets and the other using tcp/ip?
you're right, the answer is off-topic for this issue. I had read a note about
using DISPLAY=:0, which means using unix domain socket and for that my answer
was
Howdy Christopher, Igor, and Harold...
...
Two small notes here:
1) You can actually call setenv(DISPLAY, value) inside the XWin process,
which will be inherited by XWin's children.
...
On Wed, Aug 06, 2003 at 01:06:55PM -0400, Harold L Hunt II wrote:
The for loop that you have is the way I have
Earle,
Earle F. Philhower III wrote:
Howdy Harold,
At 07:31 PM 8/5/2003 -0400, you wrote:
Can't remember if I replied to this yet. I am in the process of
getting my Inspiron 8500 returned after having it replaced (bought it
3 weeks ago). Both the original and the replacement randomly freeze.
Howdy David
At 07:09 AM 8/6/2003 +0200, you wrote:
Wow! This is great! Just what we were discussing earlier...
Just one comment: Is it not possible to automatically set the DISPLAY
variable from X so that it automatically starts the xterms etc in the
right X display, rather than having to
Earle F. Philhower III wrote:
Howdy Harold,
At 07:31 PM 8/5/2003 -0400, you wrote:
In other words, I might look at your patch tomorrow, or I might look
at it next week. Can't say for sure.
In any case, thanks for the patch, I like the idea and am looking
forward to seeing what it does.
No
Howdy Harold,
At 07:31 PM 8/5/2003 -0400, you wrote:
Can't remember if I replied to this yet. I am in the process of getting
my Inspiron 8500 returned after having it replaced (bought it 3 weeks
ago). Both the original and the replacement randomly freeze. Google for
[Inspiron 8500 freeze]
On Wed, 6 Aug 2003, Alexander Gottwald wrote:
On Wed, 6 Aug 2003, Earle F. Philhower III wrote:
The started
app sees all ENV variables that XWin.exe saw at startup, so if you set
your DISPLAY before starting XWin you don't need the -display x.x.x.x:y.y
options.
Don't rely on that. At
Earle,
Earle F. Philhower III wrote:
Howdy Harold,
At 12:58 PM 8/10/2003 -0400, you wrote:
I have committed your patch to my local tree. However, I wonder why
all of the files are prefixed with winmultiwindow. Is the code
purely intended only for multiwindow modes? If so, that is fine.
Howdy again Christopher...
At 11:00 PM 8/6/2003 -0400, you wrote:
I'm not really up on cygwin's process model, what would the setsid() call
do? I have read the man page and I'm still not sure what's a session ID or
why I'd want a new one...
It would disassociate a tty from any child process.
Howdy Christopher...
At 09:57 PM 8/6/2003 -0400, you wrote:
a) Closes all fds on the fork()'d process
It *may* be helpful to call setsid() at this point, after you've closed
the file descriptors.
I'm not really up on cygwin's process model, what would the setsid() call
do? I have read the man
The for loop that you have is the way I have seen it done before.
Harold
Earle F. Philhower, III wrote:
Howdy Harold...
..
You may still be correct with your worries, I'm sure there's a file
descriptor
that the OS is dup2()'ing there you don't want. FWIW I'm execl()'ing
/bin/sh -c command
On Wed, 6 Aug 2003, Igor Pechtchanski wrote:
On Wed, 6 Aug 2003, Alexander Gottwald wrote:
On Wed, 6 Aug 2003, Earle F. Philhower III wrote:
The started
app sees all ENV variables that XWin.exe saw at startup, so if you set
your DISPLAY before starting XWin you don't need the
Ralf,
If my IP is w.x.y.z vs. my loopback of 127.0.0.1, how is one of these
using unix domain sockets and the other using tcp/ip?
Harold
Ralf Habacker wrote:
Hi all,
The most recent patch looks pretty good from your description.
c) Replaces %display% with 127.0.0.1:display.0 in commands
Hi all,
The most recent patch looks pretty good from your description.
c) Replaces %display% with 127.0.0.1:display.0 in commands
Huh, I was going to say that %display% should be replaced with
127.0.0.1:0.0, but then I remembered that we know the 0.0, but we
don't know that the user
On Thu, Aug 07, 2003 at 05:36:10PM -0700, Earle F. Philhower III wrote:
Howdy again Christopher...
At 11:00 PM 8/6/2003 -0400, you wrote:
I'm not really up on cygwin's process model, what would the setsid() call
do? I have read the man page and I'm still not sure what's a session ID
or
why I'd
On Wed, Aug 06, 2003 at 06:45:22PM -0700, Earle F. Philhower III wrote:
Howdy Christopher, Igor, and Harold...
...
Two small notes here:
1) You can actually call setenv(DISPLAY, value) inside the XWin process,
which will be inherited by XWin's children.
...
On Wed, Aug 06, 2003 at 01:06:55PM
26 matches
Mail list logo
