Open FichteFoll opened 1 year ago
Yeah, we could consider printing it outside of debug. The idea was that people could enable debug when they were adding and debugging custom commands and then disable debug to turn off noise once they've confirmed their custom rules were working.
The idea is that when you notice a problem, you can enable debug to see what is going on, but I guess we could consider always displaying. I'll evaluate potential annoyances that could occur if we do this. I wonder if default rules, which may not apply to everyone's system, would cause a lot of noise. If so, I may pass on this.
Just fyi, for my AutoSetSyntax
plugin,
While trying to figure out why my rule didn't work and eventually setting
"debug": true
, I noticed the following on the console:In my opinion, this is not the kind of message that should require to enable debug mode to be visible. Note that I'm only using custom rules and none of the defaults, but even then I still believe such a message could be useful to see every once in a while for people who do not have the third-party syntax installed that the default configuration wants to set.
For multiple syntaxes ina rule, this should only report whether each syntax can be found either in debug mode or when none of them could be found.
My rule, for comparison:
(must be
ShellScript
)