>> 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
>
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
> 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 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.
sta
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
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
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 t
On 29/12/2009 16:15, Jim Reisert AD1C wrote:
Should we use "run" to launch startxwin.exe, or is it OK to just
create a shortcut to startxwin.exe?
In general, you should be using run.exe in Windows shortcuts. The Start
Menu shortcut created during postinstall goes a step further, running:
\p
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 (releas
On Tue, Dec 29, 2009 at 1:57 PM, Yaakov (Cygwin/X) wrote:
> This release replaces those scripts with a startxwin executable.
Should we use "run" to launch startxwin.exe, or is it OK to just
create a shortcut to startxwin.exe?
- Jim
--
Jim Reisert AD1C, , http://www.ad1c.us
--
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 th
11 matches
Mail list logo
