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.
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:
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
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
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:
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
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.
facepalm!
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
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
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
