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

Partial CMT activation configuration for non CMake workspace folder not persistent #1269

Closed
kurthardin opened this issue May 28, 2020 · 1 comment
Labels
bug a bug in the product Feature: configure
Milestone

Comments

@kurthardin
Copy link

Brief Issue Summary

When connecting to a remote multi-root workspace where one folder doesn't contain a CMakeLists.txt file, clicking the "Don't show again" button on the "CMakeLists.txt was not found in the root of the folder..." notification does not persist, i.e. the notification appears each time the workspace is opened.

Expected:

  1. Connect to remote development environment via remote-ssh extension.
  2. Open multi-root workspace with one root folder that doesn't contain a CMakeLists.txt file.
  3. Click "Don't show again" button on the "CMakeLists.txt was not found in the root of the folder..." notification.
  4. Close and re-open workspace.
  5. "CMakeLists.txt was not found..." notification is not shown again.

Apparent Behavior:

  1. Connect to remote development environment via remote-ssh extension.
  2. Open multi-root workspace with one root folder that doesn't contain a CMakeLists.txt file.
  3. Click "Don't show again" button on the "CMakeLists.txt was not found in the root of the folder..." notification.
  4. Close and re-open workspace.
  5. "CMakeLists.txt was not found..." notification is shown again.

Platform and Versions

  • Operating System: Windows 10 (local), Ubuntu 19.10 (remote)
  • CMake Version: cmake version 3.14.5
  • VSCode Version: 1.45.1
  • CMake Tools Extension Version: 1.4.0
  • Compiler/Toolchain: 8.0.0-3
@andreeis
Copy link
Contributor

This should be fixed in CMake Tools 1.4.1 which was published today.
Let us know if you encounter any issues with this release.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug a bug in the product Feature: configure
Projects
None yet
Development

No branches or pull requests

2 participants