Re: Quartz no longer launching when an X application is invoked
> On Dec 4, 2023, at 10:08, Ryan Schmidt wrote: > > Could you file a new ticket to do that cleanup? Bonus points if you want to > submit a pull request to implement it. See: > Thanks for providing the history here. Ticket 68836 created. https://trac.macports.org/ticket/68836#ticket
Re: Quartz no longer launching when an X application is invoked
On Dec 3, 2023, at 18:28, Kevin Horton wrote: > > I find in ~/.zprofile > > # MacPorts Installer addition on 2020-12-29_at_06:08:54: adding an > appropriate DISPLAY variable for use with MacPorts. > export DISPLAY=:0 > # Finished adapting your DISPLAY environment variable for use with MacPorts. > > My other machine also has a ~/.zprofile, but it only sets the PATH. it does > not set DISPLAY. > > I surmise that MacPorts stopped fiddling with DISPLAY sometime between late > 2020 and late 2021. Maybe there should be some automatic check of DISPLAY in > .zprofile, and a it could offer to clean it up if needed. The MacPorts 2.6.4 installer for macOS 11 inadvertently added the DISPLAY=:0 setting to shell startup files. The bug was corrected in MacPorts 2.7.0 but no code was ever added to clean up the mess for users who had already used the 2.6.4 installer. https://trac.macports.org/ticket/61649 Could you file a new ticket to do that cleanup? Bonus points if you want to submit a pull request to implement it. See: https://github.com/macports/macports-base/pull/218#issuecomment-739666236
Re: Quartz no longer launching when an X application is invoked
Chris Jones writes: > Users should not need to do *anything* to get DISPLAY correctly set. > Anything you have in your personal environment configuration should be > removed. If you aren't getting DISPLAY set with the correct launchd > socket by default then you must have something that is interfering with > this. I removed that line and rebooted, and lo and behold, DISPLAY got properly set and the X server started up automatically when I launced an X11 program. Thanks for reminding us, Chris. > > On 04/12/2023 2:15 pm, Pieter van Oostrum wrote: >> On my machine I have: >> export DISPLAY=$(launchctl getenv DISPLAY) >> I don't know if that is the canonical way to do it but for me it works. > -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Quartz no longer launching when an X application is invoked
Users should not need to do *anything* to get DISPLAY correctly set. Anything you have in your personal environment configuration should be removed. If you aren't getting DISPLAY set with the correct launchd socket by default then you must have something that is interfering with this. On 04/12/2023 2:15 pm, Pieter van Oostrum wrote: On my machine I have: export DISPLAY=$(launchctl getenv DISPLAY) I don't know if that is the canonical way to do it but for me it works.
Re: Quartz no longer launching when an X application is invoked
On my machine I have: export DISPLAY=$(launchctl getenv DISPLAY) I don't know if that is the canonical way to do it but for me it works. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
