confusion of "shell" configuration option about vscode-runonsave

[MartinMajewski]

Yeah, this confused me, too.

There should also be an placeholder to get the relative path to file from the current working directory after a cd command. Even better would be to specify a cwd.
I want to use run on save to avoid stupid gulp tasks for copying html files to by build directory, but it is a pain to preserve the current sub-path structure when the only path I can retrieve is the absolute path.

currently my config looks this way:

"emeraldwalk.runonsave": {
        "autoClearConsole": true,
        "commands": [
            {
                "match": "\\.html$",
                "cmd": "cd ${workspaceRoot} && copyfiles -u 1 './src/**/*.html' './build/'"
            }
        ]
    }

copyfiles is a globally installed npm module

Problem is, that it copies ALL files every time. But this is this the only way to get the subfolder structure preserved, as it uses glob pattern matching. I have no placeholder available to get the current file relative to the current working directory (as ${cwd} is always pointing to /}.

[bmingles]

@MartinMajewski Latest RunOnSave release added ${relativeFile} placeholder