walter-erquinigo wrote: @clayborg , the main issue is to allow users to use the regular initCommands and at the same time have another way for the vscode extension to issue their own initCommands and control the output of these specific commands without interfering with the initCommands provided by the user. Any sort of global setting that controls the output is not going to work because it would affect both the extension's initCommands as well as the user's. Like, we don't want to hide users' initCommands just because the extension wants to hide a few. This makes me think that the cleanest approach is to have another set of initCommands for the extension, that runs totally independently from the ones provided by the user. What do you think?
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
