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

Output not showing up in buildview? #32

Open
thelastprime opened this issue Dec 6, 2017 · 8 comments
Open

Output not showing up in buildview? #32

thelastprime opened this issue Dec 6, 2017 · 8 comments

Comments

@thelastprime
Copy link

I just installed the plugin. When I run a Python program using Ctrl-b, I get a new blank output window. If I go back to the program and run again, another build results window shows up. I am running ST3 on Linux. Does anyone know what the problem is?

Thanks!

@chris-palmer
Copy link

Same problem, configuration seems correct, but empty tab. Makes it useless, unfortunelty.

@rctay
Copy link
Owner

rctay commented Oct 16, 2018

Could you copy/screenshot the output of the Console window/tab?

@chris-palmer
Copy link

chris-palmer commented Oct 16, 2018

Thanks for replying! Unfortunately there is no output/error at all to the Console window, just a blank 'Build output' tab-view appears:

screenshot from 2018-10-16 10 47 06

And if I disable 'buildview', then my build works as expected, and output is correct.

@andrecavalcante
Copy link

Removing any lines related to buildview from my user settings and restarting subilime worked for me.

@rctay
Copy link
Owner

rctay commented Oct 30, 2018

You might not have your build system set up properly, as I don't see a Running /path/to/go "/path/to/your/gofile" in the Console output window. Try setting it up by going to Tools -> Build System -> New Build System... or referring to this page https://www.sublimetext.com/docs/3/build_systems.html

Sorry, I missed out that you had to disable buildview. Can I check how you did so, through Package Control, or through your Preferences.sublime-settings file? If the latter, what are the contents of the file?

@rctay rctay closed this as completed Oct 30, 2018
@rctay rctay reopened this Oct 30, 2018
@RajdeepBorgohain
Copy link

Restarting the sublime worked for me as well.

@jjon
Copy link

jjon commented Aug 22, 2019

FYI: I was experiencing the same problem.

ubuntu PoP!_OS 19.04
>>> sublime.version()
'3207'

On the same system I had buildview working fine, but had to reinstall system and lost a lot of notes and configuration files (don't ask), and when I installed buildview this time I couldn't get it to work. It exhibited the same behaviour as described above. Running a simple script resulted in the following traceback:

Traceback (most recent call last):
  File "/~~ my home ~~/.config/sublime-text-3/Installed Packages/sublime-text-2-buildview.sublime-package/pipe_views.py", line 67, in fn
  File "~~ my home ~~/.config/sublime-text-3/Installed Packages/sublime-text-2-buildview.sublime-package/pipe_views.py", line 40, in create_destination
  File "/opt/sublime_text/sublime.py", line 793, in set_scratch
    return sublime_api.view_set_scratch(self.view_id, scratch)
TypeError: Bool required

Following the experiences of others above, I started by simply restarting sublime without altering any of my project or sublime settings and Lo, the problem disappeared: The build result appears as expected in a persistent Build output window. (Which is pretty nifty! Thanks for making this.)

Just in case that's of any help.

@W-L
Copy link

W-L commented Jan 21, 2020

Had the same problem, might help someone to leave my issue here. I was trying to use the packages buildview and InputArgs combined. InputArgs normally opens a small dialog box and asks for arguments to the script. When trying to build with buildview, this dialogbox would flash up for a split second, hardly noticeable at all, and then probably aborts the build leaving the buildview tab empty. buildview worked after removing the other package. Would be grateful for suggestions of alternatives to InputArgs ;)

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

7 participants