On 7-1-2015 07:08, Yaakov Selkowitz wrote:
One of the recent improvements to startxwin was that it would now find
an available $DISPLAY itself, just like startx does. Using
-silent-dup-error doesn't do that; think of the case where another
user on the same system has started an X server
On 5-1-2015 19:17, Yaakov Selkowitz wrote:
On 2015-01-05 11:43, Yaakov Selkowitz wrote:
On 2015-01-05 05:46, Laurens Blankers wrote:
[..]
1. Handling of empty .startxwinrc
[..]
And what if it's not zero-length but still blank?
I could have startxwin check if ~/.startxwinrc is executable,
On 2015-01-06 03:38, Laurens Blankers wrote:
On 5-1-2015 19:17, Yaakov Selkowitz wrote:
On 2015-01-05 11:43, Yaakov Selkowitz wrote:
On 2015-01-05 05:46, Laurens Blankers wrote:
[..]
1. Handling of empty .startxwinrc
[..]
And what if it's not zero-length but still blank?
I could have
Hi,
As requested [1] a separate thread for suggesting improvements to xinit,
in order to solve some of the issues people have been having since the
release of 1.3.4-1 [2].
1. Handling of empty .startxwinrc
Given the new behaviour of startxwin having an empty is never a correct
configuration. It
On 2015-01-05 05:46, Laurens Blankers wrote:
As requested [1] a separate thread for suggesting improvements to xinit,
in order to solve some of the issues people have been having since the
release of 1.3.4-1 [2].
1. Handling of empty .startxwinrc
Given the new behaviour of startxwin having an
On 2015-01-05 11:43, Yaakov Selkowitz wrote:
On 2015-01-05 05:46, Laurens Blankers wrote:
As requested [1] a separate thread for suggesting improvements to xinit,
in order to solve some of the issues people have been having since the
release of 1.3.4-1 [2].
1. Handling of empty .startxwinrc
