Todd Wolfson

Alright, going to leave this issue open as I don't have time to prioritize for this either =/

Do you have a custom configuration set up for Sublime Terminal?

Ah, good eye. It looks like Windows should support environment variables up to 2048 characters: https://blogs.msdn.microsoft.com/oldnewthing/20100203-00/?p=15083 @wbond Could you give us more context behind this code?

This should be possible via Sublime Text's `is_enabled` method. Would you be interested in opening a PR adding this feature? http://www.sublimetext.com/docs/3/api_reference.html#sublime_plugin.WindowCommand

Can someone open a PR to remove and/or relocate the key binding? @wbond What was your preference for key binding? Also, we should mark this with a "help wanted" label...

Our current Terminal script doesn't support tabs: https://github.com/wbond/sublime_terminal/blob/1.18.0/Terminal.sh To add support, you'd need to either: - Fork our repo and modify the script appropriately - Copy/paste/modify the script and point...

@wbond On #99, you mentioned that the main task remaining for this is moving users from an older config to the new one. Here are a few questions I have...

With respect to config, I think exposing the keys 1:1 via JSON which maps directly to `kwargs` will be the sanest for us to manage. That includes `use_tabs` so :+1:...

@wbond Thoughts on this one? There are a good amount of repos on both sides of the argument: - Package Control https://github.com/wbond/package_control/blob/3.0.1/Default.sublime-commands#L70-L83 - SublimeLinter https://github.com/SublimeLinter/SublimeLinter3/blob/3.5.0/Default.sublime-commands#L2-L15 - Hex Viewer https://github.com/facelessuser/HexViewer/blob/st3-2.1.1/Default.sublime-commands#L70-L78

We are discussing support in #39. Thanks for opening this issue =)