SublimePTY [pre-alpha]

[atomi]

[quote=“wuub”]

Win 7 x64

You’ve tried to run two SublimePTY terminals at the same time or something else is using port 8828 or 8829.
Right now Win32Process’es are not collected when TERMINAL view is closed, so if you start one you have to quickly restart sublime to free the port.[/quote]

I went ahead and restarted Sublime.
Tried again and got this error (though I’m not sure if it’s related, i’ll remove tortoisegit and try it again and post back):

Traceback (most recent call last): File ".\sublime_plugin.py", line 356, in run_ return self.run(edit, **args) File ".\sublime_keypress.py", line 11, in run File ".\process.py", line 280, in send_keypress File ".\process.py", line 296, in read TypeError: 'NoneType' object is not iterable Traceback (most recent call last): File ".\sublime_plugin.py", line 356, in run_ return self.run(edit, **args) File ".\sublime_keypress.py", line 11, in run File ".\process.py", line 280, in send_keypress File ".\process.py", line 296, in read TypeError: 'NoneType' object is not iterable Traceback (most recent call last): File ".\sublime_plugin.py", line 356, in run_ return self.run(edit, **args) File ".\sublime_keypress.py", line 11, in run File ".\process.py", line 280, in send_keypress File ".\process.py", line 296, in read TypeError: 'NoneType' object is not iterable

[atomi]

I uninstalled tortoisegit. Though I never use it, it may have been running something on the aforementioned ports.

Restarted and tried again ran into the same issue @erinata had.

Okay. Restarted Sublime again, but before that I made sure console_server.py was running.
Success! Got it working here’s how it looks. Now, here’s what I’m seeing (red grid lines):

Edit: Noticing that it is very slow frame rate as well, but great start! Amazing work as always!
Edit2: I hope you figure out a way to run terminal without having to run cmd prior to starting Sublime. I’m not sure that’s possible, but awesome? HELL YES!

[C0D312]

[quote=“facelessuser”]
If you create two regions (one solid, one outline) you can probably get rid of the different color border. That won’t help the rounded issue at the corners, but it would help it look a bit better.[/quote]

+1.
I’m sure wuub is still working out so more important things but if he gets a chance, it would look that much better.

[wuub]

Success! Got it working here’s how it looks.

Sometimes you just have to leave people alone and they will figure stuff out

Now, here’s what I’m seeing (red grid lines):

SublimePTY.tmTheme uses white[fg].black[bg] as a default screen color. If console reports any character as white.black I don’t have to add any region and: a) everything works faster b) borders are not present.
You’ve changed console text color to green, because of that each character is reported as green.black (even if it’s a [space]) and there are a lot of regions to apply.

Edit: Noticing that it is very slow frame rate as well,

_apply_colors() is slow, I promise I’ll try to improve it asap.

I hope you figure out a way to run terminal without having to run cmd prior to starting Sublime.

I know exactly how to enable this, but I also know that once I make it too easy to run SublimePTY, people will start using it for real tasks (against my every advice) and I’ll be flooded with requests. As you’ve probably noticed, it’s still an alpha/prototype, lets say running console_server.py is a test

If you create two regions (one solid, one outline) you can probably get rid of the different color border. That won’t help the rounded issue at the corners, but it would help it look a bit better.

I had the same idea, but combining any DRAW_EMPTY/DRAW_EMPTY_AS_OVERWRITE with DRAW_OUTLINED (in any order) did not yield anything useful. It seems as if any additional regions are ignored when DRAW_EMPTY or DRAW_EMPTY_AS_OVERWRITE is used.

[atomi]

I know exactly how to enable this, but I also know that once I make it too easy to run SublimePTY, people will start using it for real tasks (against my every advice) and I’ll be flooded with requests. As you’ve probably noticed, it’s still an alpha/prototype, lets say running console_server.py is a test

I see. Well, great job - again!
It works for me, but I’ll wait until then to recommend it.

[wuub]

It works for me, but I’ll wait until then to recommend it.

I hope that I didn’t sound smug.

PTY will blow up! Frequently! I just don’t think it’s a good idea to run it right now w/o:

• at least a bit of knowledge about how st2 plugins work
• fully realizing that at the current stage of development it’s nothing more than a few prototypes and workarounds held together with duct tape

I will support any st2 developer or power-user willing to invest some time and evaluate PTY, but general user friendliness will not be my main priority for at least two more weeks.

[wuub]

_apply_colors() is slow, I promise I’ll try to improve it asap.

I hate this &^$# thing! I made it 5x faster, but some stupid bug sneaked in and I’m trying to find it for 1.5 hour already…

AGrgrhrhrhhrgrh