"Go is not installed" pop-up alert when opening Go files

ZasEditor / Zas-Editor-Issues

Public repository to track Zas Editor's bugs.

5 stars 0 forks source link

"Go is not installed" pop-up alert when opening Go files #6

Open LittleChimera opened 2 years ago

LittleChimera commented 2 years ago

I do have Go installed since I'm using VSCode for Go development. I also have plenty of Go dev tools installed (such as gopls) since they're automatically installed with VSCode, and they are in PATH.

Screenshot 2022-04-08 at 07 58 24

Go version:

go version go1.18 darwin/arm64

diocletiann commented 2 years ago

Getting the same, also Cargo (rust) is not installed

theodore-s-beers commented 2 years ago

Same, with Rust…

kexoth commented 2 years ago

Getting the same as @LittleChimera , also the code analysis/formatting tools don't work, so AFAIK go/gopls/gofmt don't get resolved/found.

FYI I use Golang via asdf:

 % go version  
go version go1.18 darwin/amd64
 % which go    
/Users/aleksandar.trpeski/.asdf/shims/go
 % which gopls
/Users/aleksandar.trpeski/.asdf/shims/gopls
% which gofmt
/Users/aleksandar.trpeski/.asdf/shims/gofmt

Formatter Error

Example Peek Definition Tooltip Error

Correct me if I'm wrong but there's no way to edit/modify the paths needed? 👀

ZasEditor commented 2 years ago

Thank you for the reports. There is definitely something wrong with the way we find the user's PATH. We will have to investigate this more. Hopefully it will be fixed in the next update we'll be releasing next week.

Since this bug make the editor practically useless, if you purchased a license, send us an email at support@zeditor.app and we'll refund you.

theodore-s-beers commented 2 years ago

Speaking only for myself: don't worry about a refund at this point. I'm sure you'll figure it out quickly.

diocletiann commented 2 years ago

I think you should consider making the demo time only expire if the app is open (or in the foreground) to give people more time to evaluate the fixes and key features (vim) as they come in. I don't see myself paying to re-test if this fix lands after my eval period expires.

jcrqr commented 2 years ago

I was able to get it working by starting the editor from the terminal:

$ open /Applications/Zas\ Editor.app/

atbentley commented 2 years ago

crqra's workaround also solves the rust issue for me: https://github.com/ZasEditor/Zas-Editor-Issues/issues/55

theodore-s-beers commented 2 years ago

@crqra that works for me too. Thanks!