Update Linux IntelliSense behavior#1844
Merged
Merged
Conversation
Update Linux IntelliSense behavior with brief description and link to more detailed blog post. I did this in a note since the behavior only applies to 16.5+ - but please let me know if there is a better way to communicate this information.
Contributor
|
Hi @mikeblome - Could you review the proposed changes to the article? Thanks. |
Contributor
Author
|
CC @corob-msft |
Contributor
|
@ktoliver Hi, Kristine - Mike Blome has retired as of 12/31. For now, it's just me doing the cpp-docs repo administration. Is there a way to let the Aquent editors know? |
Contributor
Hi @corob-msft Oh, that's excellent for him. I will send email to the Aquent team to let them know. Thanks for sharing the info. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update Linux IntelliSense behavior with brief description and link to more detailed blog post.
I did this in a note since the behavior only applies to 16.5+ - but please let me know if there is a better way to communicate this information.