<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">On Dec 3, 2023, at 18:28, Kevin Horton wrote:</div><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>I find in ~/.zprofile</div><div><br></div><div><div># MacPorts Installer addition on <span>2020-12-29</span>_at_06:<span>08:54</span>: adding an appropriate DISPLAY variable for use with MacPorts.</div><div>export DISPLAY=:0</div><div># Finished adapting your DISPLAY environment variable for use with MacPorts.</div></div><div><br></div><div>My other machine also has a <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">~/.zprofile, but it only sets the PATH. it does not set DISPLAY.</span></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br></span></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">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.</span></font></div></div></blockquote><br><div>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. </div><div><br></div><div><a href="https://trac.macports.org/ticket/61649">https://trac.macports.org/ticket/61649</a></div><div><br></div><div>Could you file a new ticket to do that cleanup? Bonus points if you want to submit a pull request to implement it. See:</div><div><br></div><div><a href="https://github.com/macports/macports-base/pull/218#issuecomment-739666236">https://github.com/macports/macports-base/pull/218#issuecomment-739666236</a></div><div><br></div><div><br></div></body></html>