Jump to content

isometry

Member
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    1

isometry last won the day on October 23 2014

isometry had the most liked content!

About isometry

  • Rank
    Member

Recent Profile Visitors

771 profile views
  1. Perfect. Thanks, @okapi! I was thinking I'd like to update to using the Alfred 2.4+ environment variables, but your tracking use of static paths down to a real issue gave me the impetus to actually do so. The workflow has now been updated with enhanced Alfred 3 compatibility and is available on GitHub, here and on Packal.
  2. I've upgraded to Alfred 3 myself now, but haven't encountered the issue reported by @kecinzer. However, I'm tracking the issue here: https://github.com/isometry/alfredworkflows/issues/6
  3. Are you aware of iTerm2's Hotkey Window? It provides arguably more powerful functionality to that of TotalTerminal, and iTerm2's default behaviour as ssh protocol handler is "Open in a New Tab". Performance improvements over the past year combined with the addition of Infinite Scrollback leave me little reason to fallback to Terminal.app or hacking SIMBL plugins :-)
  4. Unfortunately, this is in the hands of the ssh protocol handler (i.e. Terminal.app or iTerm.app). Easy to do in iTerm2, I don't have guidance for open-in-tab with Terminal.app.
  5. OK. It looks like your ~/.ssh/known_hosts contains a line that the workflow couldn't handle: most likely a blank line (with which I reproduced the error). I've updated it to handle blanks at GitHub and Packal: download Thanks for reporting the issue! Bonus fix: it also now ignores encrypted entries in ~/.ssh/known_hosts.
  6. Given you're using this workflow, I'll assume you're happy at the command line :-) Change to the workflow's directory in Alfred preferences (found by right clicking on the Workflow and choosing "Show in Finder", if necessary), and run a query manually: % (Pythagoras:~/Dropbox/Alfred 2/Alfred.alfredpreferences/workflows/user.workflow.E2B2A958-21D2-42ED-B6DF-06AF15C6A201) /usr/bin/python -c 'import alfredssh; print alfredssh.complete("local");' <items><item arg="local" autocomplete="local" uid="ssh://local"><title>ssh://local</title><subtitle>Connect to ssh://loc
  7. This is odd. Even if you just type "ssh randomhost" it should offer to "Connect to ssh://randomhost (source: input)". That your .ssh/ssh_config is a symlink, or on Dropbox should make no difference whatsoever. Can you provide any more detail?
  8. Refer to the instructions earlier in the thread for instructions on how to configure iTerm2.
  9. Amended reply #8 to resolve a bug with the suggested iTerm2 configuration in which a username, if specified, would be ignored by the iTerm2 ssh:// handler.
  10. Something along the following lines should do the job: Create a new profile named "Man Page Handler" (or whatever) Set its command to "/usr/bin/man $$HOST$$" (without the quotes) Select "x-man-page" under "Schemes Handled"
  11. Use ~/.ssh/config (man ssh_config) to specify the private key to be used without having to type it every time. Robin
  12. iTerm2 will do this by default, but I'm not aware of a way to get Terminal.app to do this. iTerm2 also has the advantage that it can be made to set the tab title properly (see post #8).
  13. Your iTerm ssh: handling Profile needs to specify the Command as ssh $$HOST$$ (prefix ssh with the appropriate path if you've installed a new version through MacPorts/homebrew/fink). zsh shouldn't come into it. See post #8 in this thread.
  14. Oops. Not sure how that one slipped through. Download and source now fixed.
  15. ...and another update to add the 'pman' keyword to render and open PDF man pages in your default PDF reader.
×
×
  • Create New...