Semantic History (cmd + click on text to trigger action) not working in v3 Beta

debuglog.txtiTerm2 supports cmd+click on text within the terminal to open files (or trigger other actions). This feature seems to be partially broken for certain file types in the v3 Beta release.

The feature IS working fine on my machine when I use iTerm Build 2.1.4.

Some observations:

• .sql files seem to open okay
• .coffee files will NOT open
• behavior of how urls are handled seems to differ between 2.1.4 and the Beta, e.g.www.google.com will not open a browser in Beta, but it will in 2.1.4.

My environment: OSX 10.11.3 iTerm 2 Build 2.9.20160206

Would you mind providing a debug log that includes you clicking on a .coffee file? Semantic history is very complex and I can't really do much without one. Instructions are at https://iterm2.com/debuglog

As for www.google.com not being clickable, commit 9f484c51 expands what is considered a URL to 2+ part hostnames and IP addresses.

@gnachman I added the debug file, thanks! Looks like a string parsing issue.

Milestone changed to Ship 3.0

Looks like we asked the OS to open /Users/scottantipa/dev/web/app/client/main/stores/NotificationStore.coffee using whatever app is registered as the default editor for .coffee files.

I bet nothing is registered. In 2.1.4 we'd use a text editor in this case, but that was kind of a gross hack because we tried to guess what the right text editor was. Still, it's less than awesome to just do nothing. We should prompt you and create a file association.

Commit 76ced69f fixes this as described in the preceding comment.

Status changed to closed

I definitely have Sublime as registered for opening .coffee files. As I said in the summary, click to open even works on my machine in previous versions of iTerm that I have installed. Or just by calling open in the terminal on a coffee file.

That's really surprising. Curiously, Apple's open command uses a deprecated API. Would you mind running the following command and attaching it here? It produces a lot of output so redirect it to a file.

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister  -dump