Can't open vscode through terminal with hyper but regular can

[LoyalPotato]

• I am on the latest Hyper.app version
• I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Manjaro 21.2.2
• Hyper.app version: 3.2.0
• Link of a Gist with the contents of your .hyper.js: Default with just some font changes
• Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
• The issue is reproducible in vanilla Hyper.app:

Issue

Hello,
I installed visual studio code through snap, by following these instructions.
In my normal terminal, the code command works fine and I can do code . to open the current directory.
In my $PATH I have the snap bin (/var/lib/snapd/snap/bin) which is where code is located.
When I run the code command in the hyper terminal it behaves as if I was running the snap command and printing the following error when I try to use the command like so code .:

error: unknown command ".", see 'snap help'.

Am I missing something? Shouldn't they perform the same?

[LabhanshAgrawal]

How did you install Hyper? Through AppImage?
Can you try a build from https://nightly.link/vercel/hyper/actions/runs/1794351456 and check

[LoyalPotato]

@LabhanshAgrawal Yeah it was through an AppImage.
I downloaded the Hyper-3.3.0-canary.1.AppImage and this time it doesn't do anything when I run the command code .

I also have zsh installed, but in the regular terminal the command works like mentioned above.

[LabhanshAgrawal]

The build I'd linked doesn't have shell environment vars inherited from hyper
I'm guessing it didn't do anything as PATH would also be stub
try to run /var/lib/snapd/snap/bin/code . and check

[LabhanshAgrawal]

may also try https://nightly.link/vercel/hyper/actions/runs/1800193266

[LoyalPotato]

Ok, running the command through the full pass, on the previous run (1794351456) and it still didn't work.
But 👀 the run you posted after that (1800193266) worked :D
What made it so that one works?

[LabhanshAgrawal]

#6268

[LabhanshAgrawal]

Ok, running the command through the full pass, on the previous run (1794351456) and it still didn't work.
But 👀 the run you posted after that (1800193266) worked :D
What made it so that one works?

Just to confirm, you used appimage for all the tests, right?

[LoyalPotato]

Yep

…

On Sun, Feb 6, 2022, 3:08 PM Labhansh Agrawal ***@***.***> wrote: Ok, running the command through the full pass, on the previous run (1794351456) and it still didn't work. But 👀 the run you posted after that (1800193266) worked :D What made it so that one works? Just to confirm, you used appimage for all the tests, right? — Reply to this email directly, view it on GitHub <#6288 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSC5RDNTWKOZBNFAYKZVWLUZ2FFTANCNFSM5NUAFEOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>