Harold,
I tested your fix and it works fine with twm. Doing a 'startkde' on a
remote box does not fail like twm does... it still works and has weird
behavior. I wonder if there is something else that we need to do to
work with modern window managers? In any case, your fix is better
Hello everybody,
it's some time I'm using Cygwin and XFree and I feel very satisfied
with both them.
Until today, I always have used the rootless mode + wmaker (which I like
very much). Anyway this morning I tried to switch to the multiwindow mode.
Having customized the contextual menu of
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect this modification solves the problem for rlogins launched
manually by an xterm, but I does not affect at all commands inserted
into .XWinrc (they look like xterm -e rlogin machine -l user).
I tried several ways to put the speed to 38400 for
Alexander Gottwald wrote:
0 is ERROR_SUCCESS which means The operation completed successfully
I guess the clipboard was opened successfully but returned a wrong
error condition. After bailing out we leave the clipboard in an open
state and other programs can not access it anymore.
I guess
Thomas Dickey wrote:
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect this modification solves the problem for rlogins launched
manually by an xterm, but I does not affect at all commands inserted
into .XWinrc (they look like xterm -e rlogin machine -l user).
I tried several ways to put the
On Wed, 25 Feb 2004, Danilo Turina wrote:
Thomas Dickey wrote:
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect this modification solves the problem for rlogins launched
manually by an xterm, but I does not affect at all commands inserted
into .XWinrc (they look like xterm -e rlogin
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect opening an xterm within rootless mode I can see from stty that
the terminal speed is 38400, while opening the same terminal from
multiwindow mode I see that the speed is 0 (the same does not happens
for rxvt for which stty always reports
Alexander Gottwald wrote:
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect opening an xterm within rootless mode I can see from stty that
the terminal speed is 38400, while opening the same terminal from
multiwindow mode I see that the speed is 0 (the same does not happens
for rxvt for
On Wed, 25 Feb 2004, Alexander Gottwald wrote:
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect opening an xterm within rootless mode I can see from stty that
the terminal speed is 38400, while opening the same terminal from
multiwindow mode I see that the speed is 0 (the same does not
Alexander Gottwald wrote:
Alexander Gottwald wrote:
On Mon, 23 Feb 2004, Takuma Murakami wrote:
Looks 'sinclude ...' is missing.
Hm, I thought I had checked that in. I'll check tonight.
I forgot th check it in. I've done it now. make Makefile should create
a Makefile which honours the
This issue has to have something to do with the way that commands are
launched from the .XWinrc menu, since launching an xterm from another
xterm works just fine. Here is the code that launches commands
specified in the .XWinrc menus:
case CMD_EXEC:
if (fork()==0)
{
struct rlimit rl;
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
Alexander,
I didn't see a commit message for this, nor is there a log of it in CVS:
It is in the config/cf directory. The Makefile template uses the macro
IncludeMakefile(DependFileName) to include the dependencies but this
macros was defined as
Alexander Gottwald wrote:
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
Alexander,
I didn't see a commit message for this, nor is there a log of it in CVS:
It is in the config/cf directory. The Makefile template uses the macro
IncludeMakefile(DependFileName) to include the dependencies but
Alexander,
I have messages from before and after your commit, and the mailing list
archive seems to have caught your commit too:
http://pdx.freedesktop.org/pipermail/xorg-commit/2004-February/000376.html
http://pdx.freedesktop.org/pipermail/xorg-commit/2004-February/000377.html
Did you happen
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
This issue has to have something to do with the way that commands are
launched from the .XWinrc menu, since launching an xterm from another
xterm works just fine. Here is the code that launches commands
specified in the .XWinrc menus:
case
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
I changed the condition when IncludeMakefile is defined as sinclude (the
former condition seemed broken) and define HasMakefileSafeInclude in cygwin.cf
The second was already in CVS. So I only changed the condiation.
Interesting. Do you have
Thomas Dickey wrote:
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
This issue has to have something to do with the way that commands are
launched from the .XWinrc menu, since launching an xterm from another
xterm works just fine. Here is the code that launches commands
specified in the .XWinrc
--- Ehud Karni wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2004 08:41:23, Elvin Peterson
elvin_peterson(at)yahoo.com wrote:
Does the clipboard paste from Windows to Emacs
under X
work? I am able to paste from Emacs to Windows
programs, but nothing happends
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
If the stdin for the menu process isn't a tty, the inherited stdin for
xterm still won't be a tty. Some stty settings can be set for non-tty's,
and some cannot. Usually the differences between xterm and rxvt in this
area are related to
Hi -
I have cygwin on W2K Pro from which I launch xwin.exe
I use xwin to monitor 3 Linux servers. I use the ALT-Fn
feature of xwin to open a separate virtual xwin session
(what is that called ... a panel? a window? an instance?)
for each server. I then open multiple telnet sessions
form each
Thanks, Takuma, the Z-order bug seems to be fixed now. Unfortunately, I am
now suddenly having problems with the clipboard integration which I have not
had problems with in ages. The bottom of my XWin.log contains the
following:
winInitClipboard ()
winProcEstablishConnection - winInitClipboard
Hi -
I have cygwin on W2K Pro from which I launch xwin.exe
I use xwin to monitor 3 Linux servers. I use the ALT-Fn
feature of xwin to open a separate virtual xwin session
(what is that called ... a panel? a window? an instance?)
for each server. I then open multiple telnet sessions
form each
Does anyone have an environment to test the reproducibility of this bug
report? I would appreciate any help in debugging it.
Harold
Original Message
Subject: [Bug 217] New: Menu bar in window is not clickable - Cygwin - XWin
Date: Wed, 25 Feb 2004 08:11:27 -0800
From:
Don,
Don V Black wrote:
Hi -
I have cygwin on W2K Pro from which I launch xwin.exe
I use xwin to monitor 3 Linux servers.
Fair enough.
I use the ALT-Fn
feature of xwin to open a separate virtual xwin session
(what is that called ... a panel? a window? an instance?)
for each server.
I am not
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
Does anyone have an environment to test the reproducibility of this bug
report? I would appreciate any help in debugging it.
Is NumLock activated?
Original Message
Subject: [Bug 217] New: Menu bar in window is not clickable -
When I enter the command startx in the bash window,
I get this response
X connection to :0.0 broken explicit kill or server
shutdown
Please help. What is going on?
__
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
On Wed, 25 Feb 2004, Eric Axelson wrote:
Here is the file.
Thanks,
Somethings wrong with the fonts. Reinstall the XFree86-fnts package.
bye
ago
--
[EMAIL PROTECTED]
http://www.gotti.org ICQ: 126018723
Chemnitzer Linux-Tag 2004 - 6. und 7. März 2004
On Wed, 25 Feb 2004, Harold L Hunt II wrote:
Does anyone have an environment to test the reproducibility of this bug
report? I would appreciate any help in debugging it.
WFM with current packages. Differing details follow.
Version: unspecified
That was helpful!
When I use
When I type in xfig in the bash window I get this
response Error: Can't open display LOCALHOST:0.0.
When I type in startx I get this response X
connection to :0.0 broken (explicit kill or server
shutdown. I reinstalled cygwin and that didn't solve
the problem. Please help.
--- Alexander Gottwald
Virgilio, Vincent Vincent dot Virgilio at itt dot com writes:
I just updated to XFree86-xserv-4.3.0-47 from -46, and now have two
problems:
1. Clipboard integration is weakened in both 'twm' and multiwindow. I
can copy/paste between X indows, but not between X and Windows (!).
2. Tk/tcl
Feeling ? :
Fat, stopped up, depressed, aching, knees hurt, back hurt, tired, sick ?
Then come let our online doctors prescribe a wonder drug for you .
Discreet, free shipping, free doctor's consult, no prior prescription required !
100's of medicines to choose from, lowest prices, highest
Constantine,
I have the latest stable versions of cygwin and cygwin/X. I usually
update them every month or so. After I automatically updated it last
time to the latest cygwin release, I started to have problems with my
X-configuration. I have the following in my ~/.xinitrc file:
xhost
In my previous message, I missed a major piece of the puzzle.
The xterm windows that are dying mysteriously are running on a Solaris
system, not on my laptop under Cygwin.
Here's the scenario. My laptop is baldur (IBM Thinkpad T40, Windows
XP, Cygwin); my Sun workstation is elmak (Sun Blade
Another couple of data points:
I don't need so many xterms to reproduce the problem. I can just ssh
from baldur (in a non-xterm window) to elmak, then run a single xterm
from there, and I see the same symptom.
If I run rxvt rather than xterm, I get:
rxvt: XError: Request: 18 . 0, Error: 5
Igor,
Yes, it's a neat trick *if* the only thing people changed was the install
drive. If they change the path, all bets are off. I'm surprised you
don't actually customize startxwin.bat (and similar files, like
startxdmcp.bat) in a postinstall script (which can run under a Cygwin
shell,
35 matches
Mail list logo
