It seems that useTrailingLinebreak can not work anymore in useOutputdebug

[PythonYunfei]

It seems that useTrailingLinebreak can not work anymore in useOutputdebug. I set the launch like this;

But it seems that it does not make any difference. Is there something wrong in my settings, or in the plugin either?

[zero-plusplus]

Specify as follows.

"useOutputDebug": {
  "useTrailingLinebreak ": true
}

The useOutputdebug.useTrailingLinebreak just represents the hierarchical structure.

This notation is used because it is not possible to express hierarchical structures well using tables.

These attributes can be conveniently completed by pressing Ctrl + Space.
Also, these errors should normally generate warnings or errors, but have you had any of these messages?

[PythonYunfei]

Thank you very much. I feel so sorry for bothering you with this question.🤣

These attributes can be conveniently completed by pressing Ctrl + Space.

Ctrl + Space does not work but it will show suggestions if I type letters within the quote. Does the same thing happen to your
own editor?

Also, these errors should normally generate warnings or errors, but have you had any of these messages?

No, it doesn't. But “type” will:

[PythonYunfei]

These attributes can be conveniently completed by pressing Ctrl + Space.

I have known the reason. Because it will change the language of the input method when pressing Ctrl+Space in Win10. A change of keybinding to Ctrl+Space will solve it.

[zero-plusplus]

It may depend on the Windows configuration language. My completion feature was Ctrl + Space by default.

No, it doesn't. But will:“type”

I have also checked and it appears that child attributes do not display any warnings or other messages.

I will check if this is a specification or my mistake.

[PythonYunfei]

Thanks for hard and sometimes trivial work.

[zero-plusplus]

No, it doesn't. But will:“type”

I have also checked and it appears that child attributes do not display any warnings or other messages.

I will check if this is a specification or my mistake.

This issue was still a bug. You can track it here.

[PythonYunfei]

Ok. Thanks.