Possible to not have the Output panel open every time I save?

[gavin310]

In the old Live SASS Compiler extension, when I would save my SASS file it would render to CSS and the only visual indication was the green "Success" message would show briefly. After installing this version, every time I save my SASS file the Output panel pops up and I have to close it. Is there a way to prevent the Output panel from opening every time I save my file?

[enoversum]

@gavin310 Know exactly what you mean. Best would be an option to only show it on error detection. You could disable it completely by setting liveSassCompile.settings.showOutputWindow to false, see https://github.com/glenn2223/vscode-live-sass-compiler/blob/master/docs/settings.md - but that would probably disable messages on detected errors as well, right, @glenn2223 ?

[gavin310]

Thanks for the tip @enoversum ! You're right that when this setting is false, when there's an error the output window won't show. I tried clicking on the red "Error" text, but that doesn't show the output window either. Unfortunately I'm not talented enough that I don't need error messages, so it would be great if the output window could only show when it needs to (on errors). Or, just having the output window show when you click on the red "Error" text could work too.

[glenn2223]

Hey @gavin310, thanks for contributing to making this extension even better!!

You could disable it completely by setting liveSassCompile.settings.showOutputWindow to false

@enoversum is right, setting this to false will hide the output all the time (including on error), but the info is still logged and can be accessed

You can open the output:

1. With the liveSassCompile.command.openOutputWindow command (F1 then type some of the above or Live Sass: Open Live Sass Output Window)
2. Clicking the error warning icons at the bottom far left, then choose the Output tab and change the drop down to Live Sass

---

I tried clicking on the red "Error" text, but that doesn't show the output window either.

This should definitely be a feature. Clicking on the Success or Error should open the output window. Will add this plus fix another for v4.4.0 which I'll try to get on tonight

Note

vscode-live-sass-compiler/src/StatusbarUi.ts

Lines 70 to 74 in 2a6a0ff

	static compilationError(isWatching: boolean): void {
	StatusBarUi.statusBarItem.text = `$(x) Error`;
	StatusBarUi.statusBarItem.color = "#ff0033";
	StatusBarUi.statusBarItem.command = null;

---

I think I need to readdress the outputting in the extension.

I will open a new issue with my initial thoughts and assign it the v5 milestone

[enoversum]

@glenn2223 Make sure you still get some free time, with all the effort you put into this beautiful extension :) . As for the feature, yeah, that would be perfect.

@gavin310 If you are looking for a quick solution for panel hiding, possibly for other panel message as well, you could try this extension: https://marketplace.visualstudio.com/items?itemName=sirmspencer.vscode-autohide

[gavin310]

That's awesome @glenn2223 , that's for working on it so quickly! Just being able to click on the Success/Error caption to bring up the output would be pretty cool.

@enoversum Thanks for that tip!

[glenn2223]

v4.4.0 will be up shortly

Closing

[glenn2223]

Any input on #26 would be appreciated 😄

[gavin310]

Any input on #26 would be appreciated 😄

It's working great! I had a small issue at the beginning where the red "Error" text was going away after only about a second, but after completely closing and reopening VSCode it's working better and gives me enough time to click the message.

The whole process and experience with the extension is so much more seamless and unobtrusive, I love it :)

[enoversum]

Any input on #26 would be appreciated 😄

I can only second @gavin310 here - it's now very fluid, and lovely to have that input window out of the way. No problems whatsoever. Even with the extension I mentioned above, the output window would still pop up and then disappear after typing (that's how the extension works). But this is now a lot better for the compiler.

[glenn2223]

Thanks for the input on this new feature. Glad you like it 😄

#26 is actually a different issue talking about an overhaul to the output window

[gavin310]

Thanks for the input on this new feature. Glad you like it 😄

#26 is actually a different issue talking about an overhaul to the output window

Oh, I didn't realize the output window was overhauled. I hadn't been paying attention to it. I'll check it out today

[glenn2223]

Oh, I didn't realize the output window was overhauled. I hadn't been paying attention to it. I'll check it out today

No, sorry if I wasn't clear. It's just an issue raised to discuss the possibility of overhauling the log. Making sure it's considered a useful/viable change before I commit to it for v5.