rp2: Fix syntax break in CMakeLists.txt.#19417
Open
Gadgetoid wants to merge 1 commit into
Open
Conversation
rp2/CMakeLists.txt: Remove backslash escape from the BTStack config file setting. This broke syntax highlighting in VSCode and GitHub's web UI, even though it still worked. Signed-off-by: Phil Howard <github@gadgetoid.com>
|
Code size report: |
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
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.
Remove backslash escape from the BTStack config file setting. This broke syntax highlighting in VSCode and GitHub's web UI, even though it still worked.
Stumbled upon this while monkeying with PSRAM. It's not essential (doesn't seem to break anything) but reading CMakeLists.txt without syntax highlighting hurts.
See the break in GitHub's web UI half way through:
micropython/ports/rp2/CMakeLists.txt
Lines 349 to 365 in 964803a
Generative AI
I did not use generative AI tools when creating this PR.