Shell pipe not executed in workspace

[pjungkamp]

kakoune lets me insert the local directory/file names/contents using ls or cat.

I'd expect !# ls to insert a list of all file in the working directory. Instead it inserts my home directories contents.
Checking with !# env shows that the command runs in an empty environment (not even PATH is present!). See

PWD=/home/redacted
SHLVL=0
_=/usr/bin/env

This is the same with terminal.integrated.automationProfile.linux unconfigured and with a basic configuration

"terminal.integrated.automationProfile.linux": {
    "path": "/bin/sh",
    "args": ["-c"]
}

I'm unable to inject the `${workspaceFolder}" into the environment of the shell pipes.

[71]

Thanks for the report! b144b02 should fix it, but I only tried it on Windows so I would welcome a confirmation!

[pjungkamp]

I'd like to try it!

Are there build instructions?
I'm inexperienced with npm.

I installed vsce, yarn and ts-node and tried to build using:

npm install
npm run package

Which complains about a missing process dependency.

[71]

Uuuh I'm not quite sure this works. In my case I run yarn at the root of the repository (which installs dependencies), then I open the repo in VS Code, and in the "Run" view of VS Codes I pick "Launch extension" (or something like that). With this approach you can set breakpoints and debug Dance while using it, which is nice.

[pjungkamp]

My bad. With yarn it's working. Seems like npm was the problem. I had seen the package.json and just assumed npm.

The shell commands work great! E.g. generating a filesystem link using ls/fzf/realpath.

[71]

Ah, glad to know it works! Yeah package.json is used by both npm and yarn, but the file that gives yarn away is yarn.lock :)