Re: problem opening xterm

2016-08-06 Thread JF Mezei
On 2016-08-06 14:21, Brandon Allbery wrote: > Sigh. So something else is clearing it. The terminal is started with > $DISPLAY set correctly (if it weren't, the terminal window wouldn't even > show up) so something in your shell session is clearing $DISPLAY. More complete test: after having

Re: problem opening xterm

2016-08-06 Thread JF Mezei
On 2016-08-06 14:04, Brandon Allbery wrote: > This means your dotfiles (probably cribbed from Linux) are overriding > $DISPLAY. Don't do that; there is no guarantee that the display is actually > :0, and the persistent security access keys are indexed by the $DISPLAY set > by launchd not the

Re: problem opening xterm

2016-08-06 Thread Brandon Allbery
On Sat, Aug 6, 2016 at 2:01 PM, JF Mezei wrote: > So it appears that before XQuartz is started, DISPLAY is set to the > value seen by Mr Gurman, and once it is running, set to :0 as I am > seeing on my deskop now. > This means your dotfiles (probably cribbed from Linux)

Re: problem opening xterm

2016-08-06 Thread Joseph B. Gurman
For instance, I see: /private/tmp/com.apple.launchd.fMz15nlE00/org.macosforge.xquartz:0 when I echo $DISPLAY. Xquartz 2.7.9, OS X 10.11.6 > On Aug 6, 2016, at 1:39 PM, Brandon Allbery wrote: > > On Sat, Aug 6, 2016 at 1:35 PM, JF Mezei