On Jan 28, 2022, at 15:34, Dave Horsfall wrote:
>
>mackie:~ dave$ echo $DISPLAY
>
>mackie:~ dave$
>
> Is this something I forgot to do during the upgrade? I set $DISPLAY to
> ":0" (an old Unix trick) to no effect,
Setting DISPLAY to :0 is correct on Mac OS X 10.4.x and earlier, but i
On 2022-01-28 at 16:34:29 UTC-0500 (Sat, 29 Jan 2022 08:34:29 +1100
(EST))
Dave Horsfall
is rumored to have said:
MacBook Pro (13-inch, Mid 2010), saddled with High Sierra 10.13.6 (as
far
as it will go).
Back when I was running Sierra these tools worked just fine; after
upgrading to HS (and
Maybe setting the DISPLAY is the issue. On my machine, DISPLAY in a new
terminal session is
/private/tmp/com.apple.launchd.vW9b4Z3lh5/org.macosforge.xquartz:0
and presumably this is the mechanism by which Xquartz is triggered to
launch when a process in Terminal accesses DISPLAY.
Uli
On 1/2
MacBook Pro (13-inch, Mid 2010), saddled with High Sierra 10.13.6 (as far
as it will go).
Back when I was running Sierra these tools worked just fine; after
upgrading to HS (and rebuilding MacPorts that took almost a day) things
went pear-shaped:
mackie:~ dave$ xv
xv: Can't open displa
