Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error on syntax check #77

Open
jmls opened this issue Jan 13, 2022 · 3 comments
Open

error on syntax check #77

jmls opened this issue Jan 13, 2022 · 3 comments

Comments

@jmls
Copy link

jmls commented Jan 13, 2022

If I fix an error on syntax check, I get a notification error

image

and the error in the editor is not cleared. The extension seems stuck on "checking syntax"

image

@jmls
Copy link
Author

jmls commented Jan 13, 2022

How do I add the TERM environment to the extension ? It is set in the default shell (echo $TERM === xterm)

@jmls
Copy link
Author

jmls commented Jan 13, 2022

fwiw, a hack is to rename _progres to _progres_bin and create a new fiile _progres with

#!/bin/bash -e
  
export TERM=xterm
exec /usr/dlc/bin/_progres_bin "$@"

@tnguyen-brs
Copy link

I'm getting the same error. Any ideas @chriscamicas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants