aboutsummaryrefslogtreecommitdiffstats
path: root/sources/pyside6/doc/tutorials/debugging/vscode
diff options
context:
space:
mode:
authorFriedemann Kleint <Friedemann.Kleint@qt.io>2022-01-06 11:40:56 +0100
committerFriedemann Kleint <Friedemann.Kleint@qt.io>2022-01-06 12:21:20 +0100
commit4a8b8e3dc45f1067a7f75e5f7ce95d8e639d530a (patch)
treeac599bae94663f4d91f7c0b5497e64a8e9db2ce7 /sources/pyside6/doc/tutorials/debugging/vscode
parent5925ccb54b818e9dfc0766480683d232f95e6965 (diff)
Fix some doc warnings in the debugging tutorial
Fix: - sources/pyside6/doc/tutorials/debugging/qtcreator/qtcreator.rst:2: WARNING: Title underline too short. - sources/pyside6/doc/tutorials/debugging/qtcreator/qtcreator.rst:21: WARNING: Inline interpreted text or phrase reference start-string without end-string. Change the syntax highlighting to javascript, since json does not like the embedded comments of the MS-extended jsonc, fixing: sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst:21: WARNING: Could not lex literal_block as "json". Highlighting skipped. sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst:47: WARNING: Could not lex literal_block as "json". Highlighting skipped. Amends d727a69e2f58be167845b8179edf1735df6ccf1e. Pick-to: 6.2 Task-number: PYSIDE-841 Change-Id: I171c57e4a7f787559022fbbb14a7eb7bb9f1a91c Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Diffstat (limited to 'sources/pyside6/doc/tutorials/debugging/vscode')
-rw-r--r--sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst b/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
index 59579e7cf..2563b4377 100644
--- a/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
+++ b/sources/pyside6/doc/tutorials/debugging/vscode/vscode.rst
@@ -18,7 +18,7 @@ Run -> Add Configuration -> Python -> Python File
This should create a launch.json file which looks like this:
-.. code-block:: json
+.. code-block:: javascript
{
// Use IntelliSense to learn about possible attributes.
@@ -44,7 +44,7 @@ interpreter inside the virtual environment.
Now, we need to add a configuration to attach the GDB debugger to the Python
process that is already running in debug mode. Let's call it "(gdb) Attach"
-.. code-block:: json
+.. code-block:: javascript
{
// Use IntelliSense to learn about possible attributes.