On Thu, Sep 10, 2026 at 07:38:08AM -0400, Greg Wooledge wrote: [...]
> > Worth a try [...]
> If Thomas is using "setenv", he might be in csh/tcsh, in which case
> he'd need to use
>
> env DISPLAY=:0 <your-application>
absolutely right (as you are most of the times in things shell),
thanks.
> to get the desired effect. However, I'm deeply curious about the
> results he's reporting. Are "Konsole" and "Mate" both terminals
> that are running in the same session? How do we explain the
> different values of $DISPLAY if they are?
This is curious, isn't it? My hunches go
(a) different sessions (I see "different computers as a special
case of this :)
(b) mate terminal is invoking a different shell than the others
(why?), and this has a faulty init file overriding the
inherited DISPLAY
(c) mate terminal prods some daemon (via DBUS or some similar
Rube-Goldbergian construct) and there is another "server"
process tasked with spawning the terminal. This one somehow
gets the DISPLAY right (otherwise the term wouldn't show)
but for some reason misses passing it on.
(c) is meant a bit tongue-in-cheek, but hey, I've seen my share
of constructions like that.
Cheers
--
t
signature.asc
Description: PGP signature
