Marcelo Serpa @fullofcaffeine 15:54
@Gama11 I'm trying the eval debugger, but vshaxe shows a dialog saying I don't have haxe rc2 installed. I do have through lix in my project directory and it works fine for completion. Do I have to do something else in order to point the eval plugin subsystem to my lix-installed RC2?
Marcelo Serpa @fullofcaffeine 16:03
OK, nevermind, it was a lix issue as well. I have lix installed globally, it seems that when a scope is not specified, when you set the haxe version using lix, it sets the global scope. I had Haxe 3.7 setup via lix/haxeshim outside of my project directory and vscode was using that instead. I just ran "lix use 4.0.0-rc2" and now the global binary is set to RC2.
Not very intuitive, wish there was a lix system use <version> instead.
Marcelo Serpa @fullofcaffeine 16:09
Still...
It's using the global Haxe installation instead of the Haxe from the project scope :( So if I try to debug it says it's missing all the haxelibs that are actually already installed.
Am I missing something? cc @Gama11
Jens Fischer @Gama11 16:10
not sure, I don't use lix
eval-debugger uses haxe haxe from the haxe.executable setting
Marcelo Serpa @fullofcaffeine 16:12
ok, I'll try pointing to the absolute path. It seems to work fine for completion but fails for the eval-debugger.
Does it run Haxe from the context of the project directory?
Jens Fischer @Gama11 16:15
it uses Haxe's --cwd argument, just like the language server does for completion
Marcelo Serpa @fullofcaffeine 16:15
How can I set the value for this argument?
To make sure it runs from within the project dir?
Jens Fischer @Gama11 16:16
I mean, it already sets that to the project dir
Marcelo Serpa @fullofcaffeine 16:17
Strange, it seems to work fine for completion and picks up the right Haxe Lix scope for the project, but fails with the eval-debugger
:(
Jens Fischer @Gama11 16:18
seems to work fine with a local .haxelib repo
so my money is on it being another lix issue :P
Marcelo Serpa @fullofcaffeine 16:19
@Gama11 Posted on the #lix channel
How can use a local haxelib repo?
Is this documented somewhere?
Jens Fischer @Gama11 16:19
haxelib newrepo, or just create a .haxelib folder in the project
https://lib.haxe.org/documentation/using-haxelib/#newrepo
Marcelo Serpa @fullofcaffeine 16:20
Maybe this could be a workaround for now
@Gama11 So I installed all the necessary haxelibs on the global haxe and now the debug output says this:
classpath src is not a directory or cannot be read from
Any hints?
Jens Fischer @Gama11 16:25
doesn't seem familiar, not even sure what program would print that error?
Marcelo Serpa @fullofcaffeine 16:28
It's the output for the Haxe Interpreter launch config I have
Which is the verbatim one from the vshaxe help wiki
 {
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Haxe Interpreter",
            "type": "haxe-eval",
            "request": "launch",
        }
    ]
}
Jens Fischer @Gama11 16:28
in the debug console?
Marcelo Serpa @fullofcaffeine 16:28
Yes
Jens Fischer @Gama11 16:28
huh
Marcelo Serpa @fullofcaffeine 16:29
https://clb.sh/1ba52b
Jens Fischer @Gama11 16:29
src is directly in your project root?
Marcelo Serpa @fullofcaffeine 16:30
.
├── app.js
├── build-backend.hxml
├── build-frontend.hxml
├── build.hxml.~1~
├── haxelib.json
├── haxe_libraries
├── hx-web-on-rails-neko.hxproj
├── hx-web-on-rails-nodejs.hxproj
├── makefile
├── node_modules
├── package.json
├── README.md
├── release_haxelib.sh
├── src
├── webpack.config.js
├── webpack.config.js.~1~
└── yarn.lock
Jens Fischer @Gama11 16:30
urm
Marcelo Serpa @fullofcaffeine 16:30
yes
Jens Fischer @Gama11 16:30
I think that is a lix error message :P https://github.com/lix-pm/haxeshim/blob/f762683f14591731ada2a756084e3a235792e11a/src/haxeshim/HaxeCli.hx#L57
no wonder I haven't seen it before
(was searching for it in the compiler first and no hits)
well, haxeshim to be exact I guess..
Marcelo Serpa @fullofcaffeine 16:33
So there's defintetly an issue with haxeshim<>eval-debugger extension
Marcelo Serpa @fullofcaffeine 16:55
@Gama11 Is there verbose knob that allows me to see what is being sent to haxe from vshaxe in the console?
in vshaxe
Jens Fischer @Gama11 16:58
not for eval-debugger
it's really just this https://github.com/vshaxe/eval-debugger/blob/master/src/Main.hx#L141
Marcelo Serpa @fullofcaffeine 16:58
Considering vshaxe works well with lix and eval-debugger doesn't, maybe the issue could also be the (perhaps slightly different) implementation for eval-debugger?
Mybe there's some difference there?
Can I force-set cwd in the settings.json?
Jens Fischer @Gama11 17:53
it's just the workspace directory