Jean, That would be nice. How does one do this to get this information?
GR On Thursday, March 5, 2026 at 12:22:45 AM UTC-8 jj wrote: > Hi Greg, > > Did you compare the output of `env` in your Terminal and in the Worksheet? > This could give you some clues of what is missing or different. > > HTH > > Jean Jourdain > > On Wednesday, March 4, 2026 at 10:27:08 PM UTC+1 Greg Raven wrote: > >> I copied the paths from .zshrc to .zprofile, but that changed nothing. I >> could always execute the Servbay commands in Terminal app ... still hoping >> to be able to reach them through a BBEdit shell worksheet, though. >> >> For now, I have moved the commands from Unix Worksheet to Scratchpad, >> where I can copy and paste them into Terminal app. >> >> Thanks for your help. >> >> --- GR >> >> On Tuesday, March 3, 2026 at 1:31:39 PM UTC-8 GP wrote: >> >>> Hmm ... "paths to my .zshrc file" ... >>> >>> Did you read BBEdit's Regarding environment variables when using “zsh” >>> <https://www.barebones.com/support/bbedit/zshenv.html>? >>> >>> According to that, "BBEdit runs zsh as a non-interactive shell, zsh does >>> not load ~/.zshrc" so you need to "move $PATH (and other environment >>> settings) into ~/.zprofile" which will get loaded by zsh in a >>> non-interactive invocation. >>> >>> Also, did you install the ServBay CLI per the ServBay CLI: >>> Installation, Configuration & Usage Guide >>> <https://support.servbay.com/basic-usage/command-line-support%20directions> >>> ? >>> >>> Although the directions are slightly outdated (by referencing bash as >>> the default MacOS shell), the context of applying "Install CLI Tool to zsh" >>> seems to imply modifying .zshrc, which per the above BBEdit support >>> document won't work to add Servbay's installed tools path to the invoked >>> non-interactive shell's $PATH. >>> >>> Without physically installing ServBay and checking what "Install CLI >>> Tool to zsh" does, I assume that command modifies an existing ~/.zshrc file >>> (or creates one if needed) by adding: >>> >>> export PATH="/Applications/ServBay/script:$PATH" >>> >>> to it, as the Servbay support Command-Line Tool: servbayctl >>> <https://support.servbay.com/basic-usage/command-line-tool-servbayctl> >>> article's >>> Prerequisites section recommends. >>> >>> With all that covered: >>> >>> 1. Check your ~/.zshrc file. Does it have the above export PATH command >>> in it? >>> >>> a. If so, move it to ~/.zprofile (creating the ~/.zprofile file if >>> needed). >>> >>> b. If not, check the ~/.zprofile file (if one exists) to see if the >>> above export PATH command is in it. If the file or command doesn't exist, >>> create the file (if necessary) and add the command to it. >>> >>> 2. Open the MacOS Terminal app and check the ServBay installed tools can >>> be found using the now-configured ~/.zshrc and ~/.zprofile export PATH >>> arrangement. (Tool version commands are one way to check.) >>> >>> 3. If 2. works, repeat with a BBEdit Shell Worksheet to check the >>> ServBay installed tools can be found. >>> On Monday, March 2, 2026 at 7:03:29 AM UTC-8 Greg Raven wrote: >>> >>>> I used MAMP Pro for years in my local dev environment, and project >>>> worksheet commands (such as, to invoke js-beautify, netlify, and wrangler) >>>> worked fine. MAMP Pro's rough edges finally got to me, though, and I >>>> switched to Servbay, which in many cases seems to be a superior local >>>> environment. >>>> >>>> However, even though I have PHP, Python, Node, Rust, and Go installed, >>>> worksheet commands that used to allow me to upload files to Netlify or >>>> Cloudflare, as well as format JavaScript and JSON files, no longer work. >>>> When I try to invoke them, I get either a "js-beautify not found" or "node >>>> not found" console error. >>>> >>>> I don't mind (too much) having to copy-paste the upload commands, but I >>>> miss the JavaScript formatting. >>>> >>>> I read the BBEdit documents, tried adding aliases and paths to my >>>> .zshrc file, putting the commands in worksheets, trying different >>>> command-line syntaxes, etc., but either I'm missing something or this is >>>> simply not possible to do, even though the commands do work just fine from >>>> the command line. >>>> >>>> Anyone else run into this and come up with a solution? >>>> >>> -- This is the BBEdit Talk public discussion group. If you have a feature request or believe that the application isn't working correctly, please email "[email protected]" rather than posting here. Follow @bbedit on Mastodon: <https://mastodon.social/@bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bbedit/3ad02986-405c-4a29-9cc9-3d07051a5888n%40googlegroups.com.
