Better support for empty/blank projects about cquery HOT 13 CLOSED

The end goal is to make cquery as easy as possible, ie, just install the extension and it mostly works. If an include is not found we give a diagnostic to add an -I directive (ideally almost automatically, ie, user just clicks "Yes"), etc. The best support is of course if you generate a compile_commands.json file, but most people will not want to spend the effort on that.

from cquery.

Haha I could've filed it here instead 😛

from cquery.

echo clang++ > .cquery ?

from cquery.

why not have it as default if no .cquery is found?

from cquery.

Do you mean assume there is a .cquery for a single-file project?

from cquery.

@MaskRay yes! The official plugin of c/c++ does the same and I really like that behavior 😄

from cquery.

There will have to be a global configuration file if non-project file is to be supported.

from cquery.

I think we can do a pretty good job with defaults outside of global config? I'm fine with adding a global config too

from cquery.

I think cquery --language-server can run in a graceful degradation mode: no -I, no cache, ... But how will language clients handle non-project files?

I don't like global config because it complicates code.

from cquery.

I think the only question w.r.t. non-project files is where to store them in the cache directory, and so long as we put them under the workspace directory the language server is initialized I think everything should mostly work fine.

I don't think global config will be too much complication but I don't see a reason to add it unless there is a specific need that cannot otherwise be solved.

from cquery.

Is there initializationOptions w.r.t non-project files?

from cquery.

Is there initializationOptions w.r.t non-project files?

What do you mean? It should use the same instance of cquery as is already running in the editor session.

from cquery.

I think it now works without .cquery or compile_commands.json

from cquery.