When the log level is error, normal messages cannot be output

[xiyaowong]

1. Set output channel level to error
2. Run lua print('a\nb')

This is not a log, so log levels should not affect it.

Messages should use an independent output channel

vscode-neovim/src/messages_manager.ts

Line 9 in b9ad120

public constructor(readonly channel: LogOutputChannel) {

And it should be OutputChannel, not LogOutputChannel

[justinmk]

I think we can handle this without an extra channel.

And it should be OutputChannel, not LogOutputChannel

Why? The timestamps and highlighting can be useful.

[xiyaowong]

The output is closer to neovim and is not a log in nature. In addition, there are problems with the current message output. Particularly long content is sometimes missing.

[ollien]

For normal msg_show events (e.g. pressing "u" and getting "Already at oldest change"), we already have those in the status bar, so it not being in the log makes sense to me. The only one that's different is show_msg_history, which needs somewhere to go. IMO, that is justification to have a separate output channel for logs (the alternative of creating a new temporary buffer seems worse)

My proposal is we create two output channels, one titled "vscode-neovim logs" and another titled "vscode-neovim", the latter of which is a plain output channel (that we could perhaps adorn with a timestamp). (not sold on these names specifically)

P.S, heh, so this is amusing. You can actually create two output channels with the same name, and they'll both display in the list.