Starting new site: Error getting hugo version, Make sure hugo is available in path.

[GAZ082]

Arch Linux
Linux 4.18.12-arch1-1-ARCH #1 SMP PREEMPT Thu Oct 4 01:01:27 UTC 2018 x86_64 GNU/Linux

I do have hugo in my path.

[wmturner]

FYI I get this as well. I can even perform get version correctly.

[ralph-mcardell]

I have encountered this error when attempting to create a new site with Hugofy after creating a VS Code Remote-Container container with my Hugo and related tools installed plus the Hugofy extension and placing the .devcontainer files under Git control.

Asking for the Hugo version with Hugofy: Version is fine.
Asking for a new site with Hugofy: New Site fails with a "Error getting hugo version, Make sure hugo is available in path." error.

After some investigation, toggling Developer Tools on (on Help menu) and reading a bit of the extension source here on GitHub, this seems to be because:

1/ the error message for some Hugofy commands appears to have been copy and pasted from the Version command handler, hence misleadingly mentions hugo version.

2/ The actual error logged on the browser debug console was:
"[Extension Host] stderr: Error: /workspaces/project_root_dir already exists and is not empty. See --force."
(project_root_dir not the real workspace directory name).

The workspace directory is not empty as it already contains VSCode .devcontainer and Git .git directories. I would think sort of situation might occur quite often - even if not using a container. A developer might modify some settings causing a .vscode directory and files to be created before attempting to create a new site, and of course they may also get their project under source control early as well.