In my Rust program I have a folder structure roughly thus:

project
    |
    |---- launch.json
    |---- tasks.json
    |---- src
    |      |
    |      |---- main.rs
    |
    |---- target
    |        |
    |        |---- debug
    |        |       |
    |        |       |---- project (executable)

If I open the main.rs file in Neovim, it doesn't seem to (automatically) find the workspace setup. I cannot execute the default task. I will add a lot more folders, so I want this to always go up until it can find the workspace (or add the files to the workspace somehow). How do I do this?

This will be even more of a problem for C++ I guess, where I typically have something like this:

project
    |
    |---- build
    |       |
    |       |---- launch.json
    |       |---- tasks.json
    |       |---- Debug
    |       |       |
    |       |       |---executable
    |
    |---- CMakeLists.txt
    |
    |---- src
    |      |
    |      |---- main.cpp

The documentation is a bit lacking, it's hard to use the plugin.

E.g. what is the difference between Automaton Create and Automaton Init? Why does create -> enter name "xyz" give a prompt of "xyz/home/user"?

I tried to initialize a workspace in one of my rust projects and it didn't give an error, but I don't see the .json files. Do I have to manually create them? What did init do then?

I had hoped fixing the globals issue would solve this, but sadly it doesn't.

On Windows, commands are not executed. They are printed into a terminal, but they don't do anything.

Also, when trying to execute, it will do so just once. I can close the terminal afterwards and call up the same task again, but now not even the terminal gets opened anymore until I restart nvim.

There is no output that I can see at all (apart from terminal the first time)

I tested this in Windows Terminal on both Powershell and Git-Bash. In WSL, it works, but also only once. On my Arch Linux system, I didn't notice any such problems.

Hope to support vim also. Thx a million!!!

Sorry about opening 99% of your issues :)

I am just getting into the quickfix list. It's super useful to jump around it when having compile errors, so I'd like to start using it. From what I can see, there is a pattern in the gcc template, but when programming in Rust I do not really need that; neovim knows cargo as a compiler type. So is there a way to set ":compiler cargo" and pipe the build output to the quickfix list?

I am trying to get a C++ qt cmake project to work with automaton, but I keep getting C:\globals is not accessible by the current user!

This happens already when executing one of the tasks, without using any variables at all. Current tasks.json:

// tasks
{
    version: "1.0.0",

    tasks: [
        {
            name: "Configure",
            cwd: "C:/Users/lobner/Dev/proof-of-concept/qt_glfw_interop",
            type: "shell",
            command: "cmake -G Ninja -S . -B ./build",
        },
        {
            name: "Build Debug",
            cwd: "C:/Users/lobner/Dev/proof-of-concept/qt_glfw_interop",
            type: "shell",
            command: "cmake --build ./build",
            depends: ["Configure"],
            default: true,
        },
    ]
}

I have rename launch.json and variables.json to make sure the error does not come from some read there, so I assume automaton just looks into my tasks.json right now.

OS: Windows 11
Neovim v0.10.0
LuaJIT 2.1.1713484068
Automaton v1.4.1

I tried to set a path which may have spaces in it. Due to that, I wanted to put it in double quotes for a cmake call.

This is the tasks code:

// tasks
{
    version: "1.0.0",

    tasks: [
        {
            name: "Configure MSVC",
            cwd: "${workspace_folder}",
            type: "shell",
            command: "cmake -S \"${workspace_folder}\" -B ${workspace_folder}/build/msvc -DCMAKE_PREFIX_PATH=${ws.qt_msvc_path}"
        },
        {
            name: "Build Debug MSVC",
            cwd: "${workspace_folder}",
            type: "shell",
            command: "cmake --build ${workspace_folder}\\build\\msvc",
            depends: ["Configure MSVC"],
            default: true,
            quickfix: true,
        },
    ]
}

For some reason, this does not really get executed. The command gets printed for a short time before opening what looks like a terminal (see video).
But apart from that, it does not correctly escape the double quotes. Instead, the printed command also contains the backslashes. Since this does not execute anyway, I'm not 100% sure this is an actual bug, but it certainly looks wrong to me.