Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Close on success #40

Open
markbirbeck opened this issue Feb 12, 2015 · 3 comments
Open

Close on success #40

markbirbeck opened this issue Feb 12, 2015 · 3 comments

Comments

@markbirbeck
Copy link
Owner

From @PeterPablo:

When considering this wish [#39], please also consider to add an option to automatically close the output (buffer or panel) on success.

@markbirbeck
Copy link
Owner Author

Is the use for this that you simply don't want to see any output at all?

I'm wondering whether instead of having a title attribute to name output buffer, I should instead have a buffer attribute, which can either be a string that names the buffer, or null to indicate that we don't want a buffer.

Without a buffer we would effectively just discard all output. Would that achieve what you want?

(Of course, if the command fails we need to know...but we can work that out once I have better understood what you're trying to achieve.)

@PeterPablo
Copy link

My use case is the compilation of LaTex. I don't want to be bothered if compilation is successful, but am interested in the output if there is an error present.

@markbirbeck
Copy link
Owner Author

Seems straightforward.

My previous comment was along the lines of 'suppress all output unless there is an error', but I think I overcomplicated it since then we would then need to specify where we want the error to be written to (panel or buffer).

All that we really need is a flag that says 'if the task ran successfully suppress the output'.

A bit of thought might be needed as to how this relates to long-running jobs, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants