aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorWalter Erquinigo <a20012251@gmail.com>2023-10-25 00:05:54 -0400
committerGitHub <noreply@github.com>2023-10-25 00:05:54 -0400
commit10664813fca8d5ccbfd90bae9e791b7062dabd7c (patch)
treeb16222307bff41fba748ff041f6f01794b29c072 /lldb/packages/Python/lldbsuite/test/configuration.py
parentd72aa10a9a08e8213c84060de5a78bfb2fc1a6e5 (diff)
downloadllvm-10664813fca8d5ccbfd90bae9e791b7062dabd7c.zip
llvm-10664813fca8d5ccbfd90bae9e791b7062dabd7c.tar.gz
llvm-10664813fca8d5ccbfd90bae9e791b7062dabd7c.tar.bz2
[lldb-vscode] Allow specifying a custom escape prefix for LLDB commands (#69238)
We've been using the backtick as our escape character, however that leads to a weird experience on VS Code, because on most hosts, as soon as you type the backtick on VS Code, the IDE will introduce another backtick. As changing the default escape character might be out of question because other plugins might rely on it, we can instead introduce an option to change this variable upon lldb-vscode initialization. FWIW, my users will be using : instead ot the backtick.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions