clayborg wrote:
Another idea would be to add a command that allows users to specify the console
to log LLDB commands from `*Commands` settings by allowing them to specify a
console. From the DAP spec we have:
```
/**
* The output category. If not specified or if the category is not
* understood by the client, `console` is assumed.
* Values:
* 'console': Show the output in the client's default message UI, e.g. a
* 'debug console'. This category should only be used for informational
* output from the debugger (as opposed to the debuggee).
* 'important': A hint for the client to show the output in the client's UI
* for important and highly visible information, e.g. as a popup
* notification. This category should only be used for important messages
* from the debugger (as opposed to the debuggee). Since this category value
* is a hint, clients might ignore the hint and assume the `console`
* category.
* 'stdout': Show the output as normal program output from the debuggee.
* 'stderr': Show the output as error program output from the debuggee.
* 'telemetry': Send the output to telemetry instead of showing it to the
* user.
* etc.
*/
category?: 'console' | 'important' | 'stdout' | 'stderr' | 'telemetry' |
string;
```
I was thinking:
```
"lldbCommandsOutputDestination" = ['console' | 'important' | 'stdout' |
'stderr' | 'telemetry' | 'none']
```
Note that I added one exrtra 'none' which would also be 'off' or 'quiet'
https://github.com/llvm/llvm-project/pull/74748
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
