Todd Wolfson

Cool, thanks for the info. I will try to reproduce by using a fresh machine on Sauce Labs by the end of next weekend.

@katmoon I believe that was the original edge case the error was for. Where would expect the terminal to open in that scenario? Maybe we could simply invoke the terminal...

@wbond Thoughts on opening in the default `cwd` (probably Sublime's directory) or home directory?

@hickford That would be an enhancement and is unrelated to this issue. Please open a separate issue or a PR.

What's the shortcut you're using and is the file in a project folder?

So the code that generates the message is: https://github.com/wbond/sublime_terminal/blob/1.18.0/Terminal.py#L123-L134 If you're invoking via a shortcut, then there should be no `paths` parameter. This means something is going wrong with `active_view().file_name()`...

Sorry for the slow response. I've been moving this weekend. I'll read this more in depth and think of options by the end of Wednesday

Alright, so due to your pre-emptive debugging, it seems like an issue in the `bash` script itself. Can you tell me what happens when you run these lines in `/bin/bash`...

I'm not seeing that. On a freshly cloned repo: ``` ls -la # -rwxr-xr-x 1 todd todd 1425 Oct 4 21:54 iTerm2-v3.sh ``` Can someone please tell me what happens...

@slifty Ah, interesting. Can you submit a PR for that? I'm not sure why it isn't showing up in my `git clone` =(