On 09/06/2017 11:14, Ugly Leper wrote:
/usr/bin/xterm: Xt error: Can't open display: :0.0
/usr/bin/xterm: DISPLAY is not set
Thanks for all suggestions. Both the following fragments seem to work
flawlessly. Both incorporate a waiting time for XWin to gain traction
before xterm is called:
1. St
>> /usr/bin/xterm: Xt error: Can't open display: :0.0
>> /usr/bin/xterm: DISPLAY is not set
Thanks for all suggestions. Both the following fragments seem to work
flawlessly. Both incorporate a waiting time for XWin to gain traction
before xterm is called:
1. Starting a xterm console from a .cmd f
On 6/7/2017 12:29 PM, Hans-Bernhard Bröker wrote:
> Am 07.06.2017 um 17:18 schrieb Ugly Leper:
>> If I want to enter xterm straight from a Windows command prompt I try
>>
>> G:\> bin\run bin\XWin -clipboard -nolock -multiwindow 2>nul &
>> G:\> bin\xterm -display :0.0
>
> I'm less than convinced th
Am 07.06.2017 um 17:18 schrieb Ugly Leper:
> If I want to enter xterm straight from a Windows command prompt I try
>
> G:\> bin\run bin\XWin -clipboard -nolock -multiwindow 2>nul &
> G:\> bin\xterm -display :0.0
I'm less than convinced that the '&' at the end of the first command is
a valid idea
Just getting a problem: this used to work but has stopped!
>From within bash I can type
$ run XWin -clipboard -nolock -multiwindow 2>/dev/null &
$ /bin/xterm -display :0.0
and I am in a xterm window. Good; as intended.
If I want to enter xterm straight from a Windows command prompt I try
G:\> b
5 matches
Mail list logo