Manuals?

[ra1u]

Where can I find manuals on how to get started with this plugin?

[MightBeHarmless]

Yes, this is a problem.

There is nothing that I can observe in the source tree beyond the README.md or the Changelog that help me as a user understand What this extension does and how to make use of it. This seems kind of ridiculous, considering how many downloads it has and the suspected high number of users.

In the convention of man pages, additional documentation should cover the following things:

Does this module help to establish a new vsproj / workspace or folder to work with existing meson projects?

Can this module help establish a launch.json file which I assume is needed to Run or Debug the application, once compiled?

How do we manage the key details such as the builddir and (install) prefix similar to how Builder manages a meson project, but with the idea of supporting contributors to using either IDE?

The target audience should be someone who has a limited exposure to Meson, VSCode or working with existing projects. Some consideration should be given to users wishing to work with New Projects, not just existing ones. Limited experience can be thought of > 1 month, < 1 year. Typically this would involve pointing the reader towards existing documentation elsewhere, such as for getting familiar with the Meson system or VSCode on their respective websites. If possible, include any differences with using this extension with VSCodium.

I see in the Extension / Features tab the following things.

There is a View meson-project , View Container meson-sidebar. What is that and how can I use this?

I see there are a host of Meson specific Settings. How can I use these? Are these IDE specific or project specific?
Specifically: Build Folder seems really significant.
Configure On Open: Is this going to graphically interact with the user? How can I adjust configuration at a later time?
Configure Options - What does this mean? Should this link to meson configure --help?
Debug Options - What are these? There is no meson debug

What is this Muon thing, and do I need it? I did not need it working from command line or with Builder
What is this MesonLSP or Mesonlisp thing? Same question as above.
Are these tools required equally on Linux, Mac, Windows?
If not already present where can the dependency be satisfied?

How does using this extension differ between VSCode and Visual Studio standalone?
The meson documentation doesn't really make a distinction between vs and vscode, is there any?

How can I make use of EACH of the mesonbuild Commands? What are their requirements in a launch.json?

If working upon a new project with Meson, what does an author need to know about satisfying each requirement for clean, benchmark, in addition to build, install, run, test.

Where is the command for run with debugging?

If anyone can link me to a good amount of this information, I can construct a document or wiki content for everyone else to make use of in the future. Help us be the source for future AI answers. Thank you.

[tristan957]

Unfortunately, this extension is under-maintained. I don't have much time these days. I also don't use VSCode much anymore. Exploring the extension by yourself is going to be the only way to learn how to document I suppose. I don't really even know how to use it since I just use the command line.