I believe what is happening is that the various #command: messages in
OSProcess classes are executing without searching my PATH. Even if I add a
copy of the current running process environment and set that as the
environment of a new PipeableOSProcess, for example, I can't even get a
result for `which node`. I can see that /usr/bin and /usr/sbin are on the
path from within Squeak.

Another example is that `PipeableOSProcess class >> #unixCommandPipeLine`
responds with an empty string when I inspect it.

Might this all be related to newer macOS settings somehow?

On Fri, Aug 26, 2022 at 1:08 AM Tom Beckmann <tomjonabc at gmail.com> wrote:

> Also just guessing here :)
> A brief google search for the return code seemed to suggest that it's
> sometimes used for "file not found" -- not sure from which component that
> would come from though. If you are using nvm, maybe nodejs only gets added
> to your PATH if you're starting from your zsh?
>
> In addition, you could try adding these params to the language server
> invocation:
> {'--stdio'. '--log-level'. '4'. '--tsserver-log-file'. '/tmp/ts.log'.
> '--tsserver-log-verbosity'. 'verbose'}
> and see if the log file is created.
>
> Best,
> Tom
>
> On Fri, Aug 26, 2022 at 12:28 AM Eric Gade <eric.gade at gmail.com> wrote:
>
>> I am a little out of my depth here so please bear with me! Answers inline:
>>
>> On Thu, Aug 25, 2022 at 10:55 AM Tom Beckmann <tomjonabc at gmail.com>
>> wrote:
>>
>>> Some things you could try:
>>>
>>> * What's the return code in the inspector?
>>>
>>
>> The exitStatus is 32512
>>
>>
>>> * Does it work if you run the lsp from a terminal?
>>>
>>
>> It works in my terminal if I just execute `typescript-language-server` or
>> `/opt/homebrew/bin/typescript-language-server`. However, this is just a
>> javascript file that the shell executes in a node environment using
>> `#!/usr/bin/env node` at the top.
>>
>>
>>> * Does e.g. /bin/ls work?
>>>
>>
>> The exitStatus is 0, so I think so. However, when I try to inspect
>> initialStdOut, it doesn't appear to contain any data anywhere.
>>
>>
>>> * If you start squeak from a terminal, is something printed to its
>>> stdout/stderr?
>>>
>>
>> In the case of /bin/ls, yes, it outputs the result to the terminal if I
>> run Squeak from a terminal (on this Mac I don't usually do so).
>>
>> Thanks!
>>
>>
>> --
>> Eric
>>
>>
>

-- 
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220826/c956ba6d/attachment.html>