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

The Build output tab is not reused after project change or Sublime Text Restart #23

Open
evandrocoan opened this issue Sep 5, 2016 · 9 comments

Comments

@evandrocoan
Copy link
Contributor

evandrocoan commented Sep 5, 2016

The Build output tab is not reused after project change or Sublime Text Restart

It just create a new one, accumulating several ones. This is annoying because happens after the project change or sublime restart.

@evandrocoan
Copy link
Contributor Author

This looks like the know issue:

  • build view is "forgotten" after restarting Sublime

@evandrocoan
Copy link
Contributor Author

What about close it on sublime plugin load?
Much better than those ghosts hunting the house.

@rctay
Copy link
Owner

rctay commented Mar 27, 2017

Hmm. I could probably set a flag via view.settings() (so I can distinguish it from actual users' files of the name "Build Output"), any views with the flag set would be closed/cleared. But I don't know if view.settings()q are preserved across editor restarts.

@evandrocoan
Copy link
Contributor Author

But I don't know if view.settings()q are preserved across editor restarts.

I doubt Sublime preservers the state. Anyways, just closing any tab named Build Output seems fine. Add a option to it on the first moment. Therefore if happens to Sublime Text preserve the state good, otherwise, good also. At least for me.

evandrocoan added a commit to evandrocoan/BuildView that referenced this issue Oct 12, 2018
Sublime Text Restart. Fixes rctay#23 - The
`Build output` tab is not reused after project change or Sublime
Text Restart
@evandrocoan
Copy link
Contributor Author

I fixed it on my fork. I am waiting other pull request being merged before because their code is dependent: evandrocoan@e777e8c

@Hansimov
Copy link

I fixed it on my fork. I am waiting other pull request being merged before because their code is dependent: evandrocoan@e777e8c

What you have done is what I have expected for a long time. I have tested your commit and it works perfectly!
Just a little note: In the latest version of your commit, one needs to change "buildview.enabled" from false to true or the plugin will not be enabled.
Thanks a lot for your contribution!

@evandrocoan
Copy link
Contributor Author

evandrocoan commented Oct 25, 2018

I disabled it because I only enable it per project. But when creating a pull request I can check pick all other commits except that one. It was very annoying having the Build output view opening everywhere. I can also enable it per view basis with https://github.com/evandrocoan/QuickSettings

@Hansimov
Copy link

@evandrocoan Another useful package found! Hope that the QuickSettings could be on the Package Control.

@evandrocoan
Copy link
Contributor Author

I just requested for it to be added: wbond/package_control_channel#7337 - Added QuickSettings Package

But I am not sure it will be accepted because I use .no-sublime-package and I not much fan of changing it.

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

No branches or pull requests

3 participants