Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2010-01-01 Thread Frédéric Bron
>> I used to add the following option to XWin command because my screen
>> resolution is now always recognized automatically: -screen 0 1920x1200
>>
>> How can I do the same using .startxwinrc?
>
> From the announcment:
>
> "startxwin also accepts command line arguments to use a different DISPLAY
> number and add additional options to pass to the server.  Please read the
> startxwin(1) manpage, which describes both the command-line arguments
> accepted by startxwin and the format of the $HOME/.startxwinrc file."

I have read that but it was not clear to me. I suspect that I should
write "--" before the "-screen" option? Is that true?

Frédéric

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2010-01-01 Thread Yaakov (Cygwin/X)

On 01/01/2010 04:30, Frédéric Bron wrote:

I used to add the following option to XWin command because my screen
resolution is now always recognized automatically: -screen 0 1920x1200

How can I do the same using .startxwinrc?


From the announcment:

"startxwin also accepts command line arguments to use a different 
DISPLAY number and add additional options to pass to the server.  Please 
read the startxwin(1) manpage, which describes both the command-line 
arguments accepted by startxwin and the format of the $HOME/.startxwinrc 
file."



Yaakov
Cygwin/X

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2010-01-01 Thread Frédéric Bron
> IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER
> SUPPORTED.

I used to add the following option to XWin command because my screen
resolution is now always recognized automatically: -screen 0 1920x1200

How can I do the same using .startxwinrc?

Frédéric

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2010-01-01 Thread Yaakov (Cygwin/X)

On 01/01/2010 01:55, Duane Krings wrote:

For of those of us who prefer the X window managers, I would like to
request an option to this new command that starts the server _not_ in
multiwindow mode as there is no -singlewindow or -nomultiwindow options
we can send to the server as overrides.


startx


Yaakov
Cygwin/X

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2009-12-31 Thread Duane Krings
For of those of us who prefer the X window managers, I would like to request an option to this new command that starts 
the server _not_ in multiwindow mode as there is no -singlewindow or -nomultiwindow options we can send to the server as 
overrides.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2009-12-29 Thread Charles Wilson
Yaakov (Cygwin/X) wrote:
> On 29/12/2009 16:27, Charles Wilson wrote:
>> Sounds like a good idea, but I wish I'd known this was coming before
>> wasting time on:
>>
>>  * Improve checkX behavior when used as 'barrier' in startxwin.
> 
> Sorry about that, Chuck, but this was just the latest of a long string
> of issues involving these scripts.  We've been talking about replacing
> them for a while, and the recent traffic on the list was enough of an
> impetus to make me finally stop bandaging the scripts and find a better
> solution.  Plus, we gain argument handling and .startxwinrc, something
> the scripts would likely never do.

Like I said, it sounds to me like a good idea; there's just so many
issues that can go (and have gone) wrong in these scripts -- PLUS, whose
idea was it to have TWO, one .sh and one .bat?!!?  Yeeesh.  We're well
rid of them.

> Honestly, this wasn't even checkX's fault, so we weren't expecting you
> to "fix" it.  The real problem here is a corner-case bug in the server;
> the race condition that checkX was causing was just the trigger.  We
> still need to get to the bottom of that, but in the meantime we have a
> solution that completely avoids the problem and gives us new features to
> boot.

Yes, it definitely seemed like some sort of race going on -- I even
noticed sometimes that checkX would return success (e.g. was able to
call XOpenDisplay()), but that the very next command in my startxwin.sh
script would fail with a "can't open display" error.  Err...what?

So, yeah, I think startxwin.exe/.startxwinrc is a really excellent step
forward.

--
Chuck

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2009-12-29 Thread Yaakov (Cygwin/X)

On 29/12/2009 16:27, Charles Wilson wrote:

Sounds like a good idea, but I wish I'd known this was coming before
wasting time on:

 * Improve checkX behavior when used as 'barrier' in startxwin.


Sorry about that, Chuck, but this was just the latest of a long string 
of issues involving these scripts.  We've been talking about replacing 
them for a while, and the recent traffic on the list was enough of an 
impetus to make me finally stop bandaging the scripts and find a better 
solution.  Plus, we gain argument handling and .startxwinrc, something 
the scripts would likely never do.


Honestly, this wasn't even checkX's fault, so we weren't expecting you 
to "fix" it.  The real problem here is a corner-case bug in the server; 
the race condition that checkX was causing was just the trigger.  We 
still need to get to the bottom of that, but in the meantime we have a 
solution that completely avoids the problem and gives us new features to 
boot.



Yaakov
Cygwin/X

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

2009-12-29 Thread Charles Wilson
Yaakov (Cygwin/X) wrote:
> IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER
> SUPPORTED.
> 
> This release replaces those scripts with a startxwin executable.

!

Sounds like a good idea, but I wish I'd known this was coming before
wasting time on:

2009-12-29  run2-0.4.0 (release)
...
* Improve checkX behavior when used as 'barrier' in startxwin.
...

Oh, well.

--
Chuck


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



[ANNOUNCEMENT] Updated: xinit-1.2.0-2

2009-12-29 Thread Yaakov (Cygwin/X)

The following package has been updated in the Cygwin distribution:

* xinit-1.2.0-2

This package includes the startx, startxdmcp.bat, and startxwin commands 
for launching the XWin server.


IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER 
SUPPORTED.


This release replaces those scripts with a startxwin executable.

By default, startxwin will launch an XWin server in multiwindow mode 
together with an xterm.  A $HOME/.startxwinrc file can be created with a 
list of commands for startxwin to launch instead of an xterm.


startxwin also accepts command line arguments to use a different DISPLAY 
number and add additional options to pass to the server.  Please read 
the startxwin(1) manpage, which describes both the command-line 
arguments accepted by startxwin and the format of the $HOME/.startxwinrc 
file.



Yaakov
Cygwin/X


CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO
==

If you want to unsubscribe from the cygwin-xfree-announce mailing list, 
please use the automated form at:


http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then look at the "List-Unsubscribe: " tag in the
email header of this message.  Send email to the address specified
there.  It will be in the format:

cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/