I don't get any jumplist entries

[GoogleCodeExporter]

What steps will reproduce the problem?
1. download futty + place it to some folder
2. pin futty to the taskbar + start menu
3. add a new session config + save
4. open session
5. no jump list :(

What is the expected output? What do you see instead?
No jumplist whatsoever there. Doesn't look different to e.g. the cmd window 
pinned

What version of the product are you using? On what operating system?
FuTTY-2012-06-22 Win7 x64

Any ideas? Thanks!

Original issue reported on code.google.com by text2t...@gmail.com on 17 Aug 2012 at 1:56

[GoogleCodeExporter]

Sorry for double posting.
Just wanted to say that it works perfectly with Kitty & puttytray with the same 
approach.

Original comment by text2t...@gmail.com on 17 Aug 2012 at 2:00

[GoogleCodeExporter]

I'm seeing similar behavior, but a little different.  Are you using file or 
registry storage for your sessions?

I'm a long-time PuTTY user and had some sessions in my registry.   FuTTY sees 
them ok, and I can double-click or load them in the main UI to open them.   I 
do see the jumplist getting updated with the names of the sessions.  However, 
when I select any of the jumplist entries, the session is not started, only the 
main UI.   All the jumplist entries behave this way.

Now as to how it is similar to your problem.  I started experimenting with 
"file" backed sessions.  As soon as I saved my first session to file, the 
jumplist stopped working.

Another small detail that might help debug or workaround this for you:

Before PuTTY added jumplist support, I used a tool called Jumplist Extender[1] 
to decorate my pinned Putty shortcut with lots of custom shortcuts in the 
jumplist.  These were not limited to putty sessions, I had custom shortcuts for 
paegent and openvpn and things.

When Putty added jumplist support, this tool stopped working becuase PuTTy was 
continuously updating the jumplist itself, and overriding my custom jumplist.  
I could manually reapply my jumplist with the tool, but as soon as I opened 
another PuTTy instance, it would get lost and replaced with PuTTy's jumplist.

I'm describing this becuase I'm seeing the same behavior in FuTTy, but only 
when I only have registry-backed sessions.  When I add file-based sessions, the 
jumplist is empty as I described above.   I can apply my custom jumplist with 
the jumplist extender, and the changes will persist indefinitely.  This 
suggests that not only is FuTTy not adding jumplist entries, there isn't even 
some attempt to set nothing deliberately.  It just stops jumplisting altogether.

I think I actually quite like this defect.   I can add a dummy file-based 
session to disable jumplist updating and use jumplist extender to add my custom 
menu just like I used to do.

One particular reason this is valuable is becuase I don't want to create actual 
sessions for each host I connect to.  If i had sessions, they would only differ 
by hostname or user.  If I wanted to change a default setting globally, I'd 
have to visit each session and change them manually.   By using shortcuts of 
the form "futty.exe user@host", I can make shortcuts for all my stuff and just 
let them all inherit the default settings.  And in m case I'm using 
jumplist-extender to present these shortcuts.

If the jumplists actually worked as designed, then my jumplist would be limited 
to actual defined sessions, which is counterproductive.  If the jumplists ever 
get fixed, hopefully there will be a way to disable them.

FuTTY-2012-06-22.exe
Windows 8 x64

[1]https://code.google.com/p/jumplist-extender/

Original comment by ajith.an...@gmail.com on 10 Aug 2013 at 3:57

[GoogleCodeExporter]

OK, a few more details now that I'm testing things.

In my original comment, I mentioned how with registry-backed sessions, that the 
jumplist was properly updating, but that the sessions actually didn't load when 
selecting the jumplist shortcut.

It appears that there is perhaps an underlying defect where the "-load 
<session_name>" command line option, and subsequently the jumplist 
"@<session_name> invocation only succeed for file-backed sessions.

When a session is not found, both the @ and -load command invocation, open the 
main UI.  If I create a file-backed session and load by its name, it loads 
properly.

So, in summary, jumplists only update when only using registry-backed sessions, 
and the jumplist shortcut("@<session_name>" would only work if there exists a 
file-back session by that name.

Original comment by ajith.an...@gmail.com on 10 Aug 2013 at 4:25

[GoogleCodeExporter]

RE: my second comment 3, the -load behavior is already reported in Issue 31, so 
I suppose that is nothing new.

Original comment by ajith.an...@gmail.com on 10 Aug 2013 at 5:38

[GoogleCodeExporter]

Since there's only upstream code dealing with jumplists now, please report any 
bugs regarding them to PuTTY and/or PuTTY Tray.  (Make sure you re-test to make 
sure it's broken in the latest builds of PuTTYTray first.)

https://github.com/FauxFaux/PuTTYTray/issues

Original comment by FireEgl on 31 Aug 2013 at 7:39

• Changed state: Unverified
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Appears to be working as of FuTTY-2013-09-01.exe

Original comment by ajith.an...@gmail.com on 10 Oct 2013 at 9:45