- There doesn't seem to be a way to create .inetloc files other than drag and drop. You can create a file that has the correct data fork and the Finder will handle it, but without the resource fork portion that the Finder itself creates upon drop, other programs (like Path Finder) won't open the file properly. I keep a list of hosts I regularly connect to in ~/.hosts, and I wanted to be able to use a script to create the .inetloc files based on .hosts, rather than have to drag and drop the location to the Finder for every single one. (That would be fine if it was one time only, but the list changes.)
- For whatever reason (I suspect a bug in Terminal.app), if you open a new Terminal window via one of these ssh://host shortcuts, .term files will not open until you relaunch the Terminal. They'll make Terminal the active pplication, but nothing happens.
- For whatever reason (another bug?), windows opened via the ssh://host .inetloc files don't show the "Command key" (β1, β2, etc) in the window's title bar. (Although the command keys still work if you're a good guesser.)
- The ssh:// addresses don't allow for many SSH options. From what I can tell, username is the only thing you can change, and even that can be problematic as robg pointed out.
- I had to tell QuickSilver where to look for the .inetloc files, but I noticed that it already indexes ~/Library/Application Support/Terminal/ by default.
My original objection to doing this was that .term files include every available Terminal setting. I like the ssh:// shortcuts because they would connect to a specific host, but use my default Terminal settings. By using .term files, I would have to recreate every single one to match the default settings if they ever changed or so I thought.
It turns out that you can create a bare-bones .term file that contains only the settings you want to change from the defaults, and the Terminal will know what to do with it. In this case, I just wanted to specify the command that gets run in the new Terminal window. The script linked below will scan ~/.hosts and create a .term file for each machine listed there in ~/Library -> Application Support -> Terminal. I used PHP because that's what was quickest for me, but this wouldn't be hard to implement in other languages.
- Download the script [macosxhints mirror]
- Unzip the script and put it somewhere in your $PATH.
- Create ~/Library/Application Support/Terminal/ if it doesn't exist.
- Create a file in your home directory called .hosts and add the hostnames of machines you want to connect to (one per line).
- Run the mkterms script
You could modify the script to add other options to the "shell command", such as a custom identity file or a different username. For example, the version I use is smart about how and when it creates .term files for root based on an LDAP database of machines we have where I work.

