Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Feedback Survey #119

Closed
vector-of-bool opened this issue Feb 21, 2017 · 10 comments
Closed

User Feedback Survey #119

vector-of-bool opened this issue Feb 21, 2017 · 10 comments

Comments

@vector-of-bool
Copy link
Contributor

Click here to take the survey.

Rather than figuring out how to insert telemetry or set up any fancy dashboards required for such things, I've created an informal, anonymous Google Forms survey.

The feedback collected therein will be used to steer future project changes.

@mkatliar
Copy link

I am happy so far, will let you know when I have something particular to say.
Keep doing the great job!

@mkatliar
Copy link

mkatliar commented Feb 23, 2017

Yes, I do have a suggestion. It would be nice to have colorful output from cmake in the OUTPUT window. With colors it is easier to perceive and analyze.

@vector-of-bool
Copy link
Contributor Author

@mkotlyar, I've always wanted to be able to provide richer output than what is available in VSCode's current OutputChannel API. There are a few open feature requests on VSCode relating to this (#564, #571, and #11005). We'll have to see where they go.

@bkeys
Copy link

bkeys commented Mar 28, 2017

This is an awesome plugin! It works really well with vscode and makes the IDE so much more usable. Thanks you for this contribution!

@papahabla
Copy link

papahabla commented May 4, 2017

When executing the command "CMake: Build a target", it would be nice to have a list of available targets displayed, such as when executing "CMake: Select a target to debug". Currently, "all" is default which may not exist (e.g. when using XCode generator), and the target must be manually entered.

@andyreimann
Copy link

Like the plugin.

You think it's possible to extract all include paths from a cmake project and use them for locating files in include statements?

@vector-of-bool
Copy link
Contributor Author

@andyreimann, that's been brought up frequently. Even my own coworkers are hounding me about it. @maddouri has made an extension to do just that, and it may be merged into this codebase in the future.

@dhicksNTIA
Copy link

I love the plugin. Great time saver. The only complaint is that I would like the debugger to allow for LLDB in Linux. When I tried to switch the 'MIMode' to 'lldb' it did not work stating '/usr/bin/lldb: unrecognized option '--interpreter=mi''.

@debojyoti-majumder
Copy link

I like it very much. Keep up the good work. Thanks for building such a good tool

@no-realm
Copy link
Contributor

no-realm commented Mar 1, 2018

@vector-of-bool If you still have a need for the survey, I would suggest placing the link in your README.md instead, since here it is pretty much invisible to most users.
I will close this one for now.

@no-realm no-realm closed this as completed Mar 1, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants