On 3/24/2016 3:49 PM, Mark Hansen wrote:
Here is an FAQ on this topic:
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xserver-nolisten-tcp-default
Here are the last two announcements in which there were major changes to
the xinit package; both of them spelled out the changes very clearly:
Here is an FAQ on this topic:
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xserver-nolisten-tcp-default
Here are the last two announcements in which there were major changes to
the xinit package; both of them spelled out the changes very clearly:
https://sourceware.org/ml/cygwin-announce
> On 2/23/2016 3:42 PM, Jaakov wrote:
>Ken, I'll try your file, thanks a lot!
>But let us recapitulate that such files get outdated very quickly.
> Your best defense against this is to read the xinit release
> announcements. You can always ask for help if you want to change the
> new behav
On 2/23/2016 3:42 PM, Jaakov wrote:
Ken, I'll try your file, thanks a lot!
But let us recapitulate that such files get outdated very quickly.
Your best defense against this is to read the xinit release
announcements. You can always ask for help if you want to change the
new behavior and are
Ken, I'll try your file, thanks a lot!
But let us recapitulate that such files get outdated very quickly.
Frankly speaking, I would be most probably lost when in need to adapt
some part of your file.
(E.g., the documentation
http://x.cygwin.com/docs/man1/startxwin.1.html
from January 28, 2016
On 2/22/2016 4:51 PM, Ken Brown wrote:
There's no need for this complexity. If you don't like what the system
startxwinrc does, just copy it to ~/.startxwinrc and modify it to suit
your purposes.
For example, something like the attached .startxwinrc might do what you
want.
Ken
#!/bin/sh
#
On 2/22/2016 3:55 PM, Jaakov wrote:
...
And yet a third alternative would be to automatically install a default
$HOME/.startxwinrc during updates.
That would completely defeat the purpose of ~/.startxwinrc, which is to
allow the user to override the system startxwinrc.
Ken
--
Problem repor
On 2/22/2016 3:46 PM, Jaakov wrote:
Ah, perhaps. There may be ways to catch that, but it may be easier
for the
OP to copy the startxwinrc file's contents. Not the best for
responding to
future changes ...
One way to prevent recursion is
if [[ "$FILEINCLUDED" != "1" ]];
then
export FILEINC
...
And yet a third alternative would be to automatically install a default
$HOME/.startxwinrc during updates.
...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: ht
Ah, perhaps. There may be ways to catch that, but it may be easier for the
OP to copy the startxwinrc file's contents. Not the best for responding to
future changes ...
One way to prevent recursion is
if [[ "$FILEINCLUDED" != "1" ]];
then
export FILEINCLUDED=1
... # do real job here
fi
On 2/21/2016 8:59 PM, Ken Brown wrote:
On 2/21/2016 6:21 PM, Eliot Moss wrote:
On 2/21/2016 4:28 PM, Jaakov Jaakov wrote:
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
Do this in your personal .startxwinrc file ...
Won't this lead to an infinite recursion? (See
https://www.cy
On 2/21/2016 6:21 PM, Eliot Moss wrote:
On 2/21/2016 4:28 PM, Jaakov Jaakov wrote:
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
Do this in your personal .startxwinrc file ...
Won't this lead to an infinite recursion? (See
https://www.cygwin.com/ml/cygwin/2016-02/msg00325.html
On 2/21/2016 4:28 PM, Jaakov Jaakov wrote:
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
Do this in your personal .startxwinrc file ...
EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
?
Where do you suggest to do it?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#u
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
?
Regards -- Eliot Moss
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Dear Marco:
>
> So, are you saying that not starting xterm is by design?
yes
Well, then, apparently, the design changed several months ago.
>> http://x.cygwin.com/docs/man1/startxwin.1.html
>
> The manpage above is a bit outdated; creating a .startxwinrc with
>
> xrdb -load $HOME/.Xresou
On 21/02/2016 19:24, Jaakov Jaakov wrote:
Dear Marco:
So, are you saying that not starting xterm is by design?
yes
http://x.cygwin.com/docs/man1/startxwin.1.html
The manpage above is a bit outdated; creating a .startxwinrc with
xrdb -load $HOME/.Xresources
xbiff -geometry -430+5 &
oclock
Dear Marco:
So, are you saying that not starting xterm is by design?
http://x.cygwin.com/docs/man1/startxwin.1.html
The manpage above is a bit outdated; creating a .startxwinrc with
xrdb -load $HOME/.Xresources
xbiff -geometry -430+5 &
oclock -geometry 75x75-0-0 &
xload -geometry -80-0 &
xt
On 21/02/2016 15:38, Jaakov Jaakov wrote:
Dear all:
How to make xterm start automatically on XWin start? When I run XWin
from a Windows shortcut, the X Server starts, but not an xterm. The same
happens when I run startxwin from a cygwin terminal.
(After the X server starts, choosing xterm from t
Dear all:
How to make xterm start automatically on XWin start? When I run XWin from a Windows shortcut, the X Server starts, but not an xterm. The same happens when I run startxwin from a cygwin terminal.
(After the X server starts, choosing xterm from the graphical menu does bring
up an xt
20 matches
Mail list logo
