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

Prefer the clang-format in PATH over the one bundled with the extension #3569

Closed
sean-mcmanus opened this issue Apr 30, 2019 · 1 comment
Closed
Assignees
Labels
Feature: Code Formatting Feature Request fixed Check the Milestone for the release in which the fix is or will be available. Language Service
Milestone

Comments

@sean-mcmanus
Copy link
Contributor

The right thing to do is to pick the clang-format in PATH over the VSCode one.

Originally posted by @ncihnegn in #2887 (comment)

@bobbrow bobbrow added this to the 1.0.0 milestone Jan 8, 2020
@bobbrow bobbrow changed the title Pick the clang-format in PATH over the VSCode one. Prefer the clang-format in PATH over the one bundled with the extension Jan 8, 2020
@bobbrow bobbrow added the fixed Check the Milestone for the release in which the fix is or will be available. label Jan 17, 2020
@sean-mcmanus sean-mcmanus modified the milestones: 1.0.0, 0.26.3 Jan 22, 2020
@sean-mcmanus
Copy link
Contributor Author

@github-actions github-actions bot locked and limited conversation to collaborators Oct 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature: Code Formatting Feature Request fixed Check the Milestone for the release in which the fix is or will be available. Language Service
Projects
None yet
Development

No branches or pull requests

3 participants