Skip to content

Launch PuTTY, FileZilla or WinSCP with arguments #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jdrews opened this issue Sep 26, 2016 · 8 comments
Closed

Launch PuTTY, FileZilla or WinSCP with arguments #126

jdrews opened this issue Sep 26, 2016 · 8 comments

Comments

@jdrews
Copy link

jdrews commented Sep 26, 2016

I am unable to launch putty with an IP argument via tab.

putty-keypiriniha

Steps to reproduce:

  1. Use keyboard shortcut to launch keypirinha (ALT + Space for me)
  2. Type putty until it is highlighted
  3. Hit tab and fill in an IP
  4. Press enter should launch putty and SSH to that IP. Pressing Enter does nothing. Keypirinha stays open.

Using Windows 10 with keypirinha-x64-portable. Version 2.9.5. PuTTY package is enabled.

@polyvertex
Copy link
Member

Just to be sure, could you please hit Alt+Enter once you have selected the item, before you hit Tab, and copy the whole Item properties text block from the console to here?

Also, this doesn't look like the regular PuTTY icon to me, what variant is it?

@jdrews
Copy link
Author

jdrews commented Sep 27, 2016

You are correct in that it's not the standard PuTTY. It is KiTTY (http://www.9bis.net/kitty/). 0.66.6.3p

Here are the Item properties when using KiTTY

09:31:38.792 Item properties:
  label:           PuTTY
  args:            
  short_desc:      
  target:          C:\KiTTY\PUTTY.EXE
  category:        file (20)
  args_hint:       accepted
  hit_hint:        keepall
  plugin:          PuTTY.PuTTY
  item_id:         17934029581963432542
  loop_on_suggest: false
  data_bag:

I double checked I could launch C:\KiTTY\PUTTY.EXE 192.168.1.2 via command line and connect.

I then grabbed putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and replaced the kitty version with the official putty.exe version 0.67. I then clicked Refresh Catalog in Keypirinha and then restarted Keypirinha. Now it shows the putty icon.

image

Unfortunately repeating the steps above (Steps to reproduce) does not result in a putty session launch.

Here are the Item properties when using the official PuTTY

09:35:15.087 Item properties:
  label:           PuTTY
  args:            
  short_desc:      
  target:          C:\KiTTY\PUTTY.EXE
  category:        file (20)
  args_hint:       accepted
  hit_hint:        keepall
  plugin:          PuTTY.PuTTY
  item_id:         17934029581963432542
  loop_on_suggest: false
  data_bag:

Note they are the same. This wasn't a copy paste error.

@polyvertex
Copy link
Member

polyvertex commented Sep 27, 2016

Confirmed, it will be fixed in the next release.
Thanks for your thorough reply.

Meanwhile, may you need a workaround you can reference your putty.exe directly into the catalog using the Apps package via the extra_paths setting, simply by appending C:\KiTTY\PUTTY.EXE to it. Be careful though to use the item created by the Apps package then, instead of the one created by the PuTTY package, by watching the status bar once you have selected the item (i.e. should be written: Apps item).

@jdrews
Copy link
Author

jdrews commented Sep 27, 2016

Thanks! Workaround confirmed.

@jdrews
Copy link
Author

jdrews commented Sep 28, 2016

Looks like the same issue is happening with the WinSCP package. I can launch a WinSCP session via tab then IP if it's an Apps item but not if it's a WinSCP item

@polyvertex
Copy link
Member

Yes, I forgot to mention that, these packages share the same code base so they have the same lack of feature: FileZilla, PuTTY and WinSCP.

@polyvertex polyvertex changed the title Launch putty with IP argument via tab Launch PuTTY, FileZilla or WinSCP with arguments Sep 28, 2016
@polyvertex
Copy link
Member

Corrected in v2.9.6

@jdrews
Copy link
Author

jdrews commented Oct 4, 2016

Confirmed v2.9.6 corrects issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants