Dear Jim,
Thanks for your note. I touched a new file with the name you suggested,
but all it did was make XWin hang and never start. I tried to copy the two
files 'system.XWinrc' and '.xinitrc' to the same name. That started the
server, but other problems cropped up. Much of the gui
,
but all it did was make XWin hang and never start. I tried to copy the
two files 'system.XWinrc' and '.xinitrc' to the same name. That started
the server, but other problems cropped up. Much of the gui in the program
'xmgrace' was unusable and missing, and the server would in a few minutes
loads. There must be calls coming from somewhere else...
Please help, right now I blocked xterm with my firewall, but that is just
silly.
Thanks!,
-bjfcom
--
View this message in context:
http://old.nabble.com/xinitrc-ignored-tp28144050p28144050.html
Sent from the cygwin-xfree mailing list
You need to create an empty ~/.startxwinrc (I think that's the name)
file. This is new with the latest Cygwin-X server.
- Jim
On Mon, Apr 5, 2010 at 1:49 PM, bjfcom bjf...@yahoo.com wrote:
Thanks for reading.
I am going crazy. When I run my xserver, xterm loads.
So, commented out
open display: :0
After inserting 'sleep 1' into the .xinitrc before each xterm
seems to start
up without trouble, so I guess there's some sort of timing condition
somewhere, although I've no idea where...
I have had `sleep 1` statements after each xterm launch in my .xinitrc
out all the xterm's
it works fine.
What an interesting .xinitrc :-)
I can reproduce the problem using it. I seem to end up with a few of the
xterms spinning somewhere and trying to use 100% CPU, and outputting the
following:
No protocol specified
xterm Xt error: Can't open display: :0
After
the
following:
No protocol specified
xterm Xt error: Can't open display: :0
After inserting 'sleep 1' into the .xinitrc before each xterm
seems to start
up without trouble, so I guess there's some sort of timing condition
somewhere, although I've no idea where...
I have had `sleep 1
Phil Betts wrote:
There's a registry setting to force programs to quit on shutdown/logoff:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/rege
ntry/34615.mspx?mfr=true
True to form, MS only tell half the story in their documentation. They
don't say whether the timeouts
. Anyone know what I'll miss out on by skipping xinit? (Other than the
problem I have with needing to force the xinit process to stick around?) I
will seem to lose the ability to run custom stuff in my .xinitrc file, but I
think I'd be customizing startxwin.bat/.sh anyway so that wouldn't
to function by running the X server directly rather than
running xinit. Anyone know what I'll miss out on by skipping xinit?
(Other than the problem I have with needing to force the xinit
process to stick around?) I will seem to lose the ability to run
custom stuff in my .xinitrc file, but I
http://cygwin.com/acronyms/#PCYMTWLL. Thanks.
On Wed, 21 Mar 2007, J. David Blackstone wrote:
Since X exits when the xinitrc process terminates, xinitrc needs to
finish by starting a program that will run for the duration of my X
session. Traditionally this is a window manager
Since X exits when the xinitrc process terminates, xinitrc needs to finish by
starting a program that will run for the duration of my X session.
Traditionally this is a window manager, but with -multiwindow a window manager
is already running. So with -multiwindow the usual course
J. David Blackstone wrote:
snip
Does anyone know what the standard suggestion for the last command of
xinitrc is when you cannot run a window run a window manager and you do not
want to run an xterm or anything else that clutters up the task bar? It'd be
nice if sleep just had an option
Eyal Rozenberg wrote:
Many of the variables used in /etc/X11/xinit/xinitrc must be placed
within double quotes, otherwise home directory names with spaces are not
handled properly, e.g. /home/Some One/ is treated as two separate tokens
on the command line. I suggest the following :
I'll add
Many of the variables used in /etc/X11/xinit/xinitrc must be placed
within double quotes, otherwise home directory names with spaces are not
handled properly, e.g. /home/Some One/ is treated as two separate tokens
on the command line. I suggest the following
Frédéric L. W. Meunier wrote:
twm: another window manager is already running on screen 0?
twm: unable to find any unmanaged screens
If I use .xinitrc with exec twm, startx reports the above.
If you use startx, by default, the multi-window mode is used (startx
passed -multiwindow to XWin.exe
On Fri, 9 Apr 2004, Danilo Turina wrote:
Frédéric L. W. Meunier wrote:
twm: another window manager is already running on screen 0?
twm: unable to find any unmanaged screens
If I use .xinitrc with exec twm, startx reports the above.
If you use startx, by default, the multi-window mode
twm: another window manager is already running on screen 0?
twm: unable to find any unmanaged screens
If I use .xinitrc with exec twm, startx reports the above.
The same using another window manager. It works fine if I add
it to startxwin.sh. It used to work with XFree86.
--
How to contact me
I have several things that I like to have run when I start an xsession
and normally I would put these into a ~/.xinitrc file to have them run
at X startup time.
However, when I run startxwin.bat it does not appear to execute the
.xinitrc file automatically. Therefore I have had to manually
Sounds like I've got my Cygwin/Xfree setup the way you'd like. You can do
it, too, in 3 easy steps...
1) Edit the file .bash_profile in your home directory and make sure the
X11R6/bin directory gets added to your path. e.g.:
export PATH=$PATH:/usr/X11R6/bin
2) Put your .xinitrc file
-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: exec wmaker in /etc/xinit/xinitrc doesn't work
Date: Thu, 4 Sep 2003 23:33:14 -0400
Hi-
I want to run WindowMaker rather than twm, so I edited /etc/xinit/xinitrc
and replaced
exec twm
with
exec wmaker
then when I ran 'startx
Hi-
I want to run WindowMaker rather than twm, so I edited /etc/xinit/xinitrc and replaced
exec twm
with
exec wmaker
then when I ran 'startx', WindowMaker started then immediately crashed.
What am I missing here?
Thanks for the help.
I prefer rxvt over xterm, and it's great that it works with or without
Cygwin/XFree86 running.
But I just discovered that if I start rxvt like I do xterm from inside
my .xinitrc, it starts up in non-X11 mode. It appears to depend on
DISPLAY - if it's just .0 it runs without X11, if it's :0.0
On 22 Oct, To: [EMAIL PROTECTED] wrote:
But what's the right way to get it to start up via .xinitrc? It seems
wrong that I should do:
DISPLAY=:0$DISPLAY rxvt -sr -sk -backspacekey ^?
Well, experiments show that
DISPLAY=$DISPLAY.0 rxvt -sr -sk -backspacekey
24 matches
Mail list logo
