Corey Shupe

> Hmmmm i just checked the source code, and you're running a different version than the current version as the line numbers don't line up. > > I suspect it...

> Maybe a suggestion to incorporate this as another parameter to hide/showPlayer overload, so you can hide the player as an entity while retaining said player in the tab list......

Considering this PR exposes a few values which would break quite a lot of logic in the backend - we should write a better API for interacting with certain scenarios....

So if I'm understanding correctly the entire point of this would be to update the virtual host used to connect to the remote. Nothing else seems to necessarily matter here....

> From what I understand of what you're saying, that's precisely what this is but with a different name. The sole purpose is to modify the address and port fields...

I think it might be time to move the logic into the pre connect and change the behavior of pre-connect to be more of a full-fledged "we need to decide...

> I'll see what I can do with regards to moving the logic. > > > > For the appending example, who is the "user" in this case? Referring to...

It's possible and something we definitely want to do :+1: There's more thought which has to go into it before we want to push out a feature like this, so...

What about commands which take 2 slashes? Wouldn't it be a lot more confusing to have inconsistent behavior.

This issue should cover de-compressing these files. We don’t have a file blacklist or whitelist.