<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
div.plaintext .task-list-item { list-style-type: none; }
</style>
</head>
<body><div class="plaintext"><p dir="auto">On 2024-10-17 at 13:04:54 UTC-0400 (Thu, 17 Oct 2024 10:04:54 -0700)
<br />
Alan Bram <alan.bram@cornell.edu>
<br />
is rumored to have said:</p>
</div><blockquote class="embedded"><div id="9F407CB7-B7CF-4828-B155-4909531EF80F">
<div dir="ltr">
<div dir="ltr">I have installed the emacs-app port. I see that it puts all of its content under the /Applications/MacPorts/Emacs.app/Contents folder, including the "emacsclient" and other command-line utilities under /Applications/MacPorts/Emacs.app/Contents/MacOS/bin/.
<div><br></div>
<div>If I want to use emacsclient as my EDITOR environment variable, should I add that (long) bin directory to my $PATH setting? or maybe put the entire long path to the utility as the value of the EDITOR variable?</div>
<div><br></div>
<div>Should the installation of the emacs-app port automatically add that directory to my $PATH?</div>
<div><br></div>
<div>Naively, it seems a little strange to me that I should have to mess with such detail.</div>
<div><br></div>
</div>
</div></div></blockquote>
<div class="plaintext"><p dir="auto">
<br />
To launch any GUI app in macOS, you need to execute the binary at /path/to/app/AppName.app/Contents/MacOS/AppName OR use "open /path/to/app/AppName.app". Both mechanisms only work if the caller is part of the same LaunchD "domain" as the current console user.</p>
<p dir="auto">So yes, if you want to launch an app from the command line, the whole path to the binary inside the app bundle (AppName.app/Contents/MacOS/AppName) is required. If there are many useful binaries in that directory, you may find it convenient to add the directory to your PATH environment variable, OR you could add ~/bin/ to your $PATH and populate ~/bin/ with symlinks to the app binaries from wherever that you frequently want to use from the command line.</p>
<br /></div><div id="391C2EDB-51F2-44BE-8BBE-77E1377A3737"><pre>
bill@scconsult.com or billcole@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
</pre></div>
</body>
</html>