Re: Following update to XWin or xorg-server: changed syntax to get a xterm terminal window

[Paul <Paul.Domaskis@gmail.com>]

Michael DePaulo <mikedep333 <at> gmail.com> writes:
|On Wed, Jun 10, 2015 at 7:28 AM, Fergus Daly
|<fergusd <at> frontier-science.co.uk> wrote:
|> For ages I used
|>     XWin -nolock -nolisten local -multiwindow &
|>     xterm -display localhost:0.0
|> to get a xterm terminal.
|> Following recent updates I get a fatal error: "Cannot establish any
|> listening sockets." In the past, updates to XWin have sometimes led
|> to similar difficulties, but I have always managed to iterate to a
|> new successful joint syntax
|>     XWin <arguments>
|>     xterm <arguments>
| By default, XWin 1.17 no longer listens on TCP sockets, only on unix
| domain sockets.
| https://www.cygwin.com/ml/cygwin-announce/2015-06/msg00003.html
| However, "-nolisten local" disables unix domain sockets.,
| So to use unix domain sockets:
|     XWin -nolock -multiwindow &
|     xterm -display :0.0
| Or to keep using TCP sockets:
|     XWin -nolock -nolisten local -listen tcp -multiwindow &
|     xterm -display localhost:0.0

I found that I also had to rejig my ~/.startxwinrc.

   ~/.startxwinrc:
   ---------------
   xrdb -load $HOME/.Xresources
   xterm -display :0.0 # xterm &
   exec sleep infinity


--
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/