I have packaged an alternative version of Portable KiTTY adopting the same approach used by Portable PuTTY ie using the registry instead of KiTTY's savedir.
My purpose is to avoid generating session files with special characters as they are not synced by OneDrive 
I modified AppInfo/Launcher/KiTTYPortable.ini (https://pastebin.com/QHi2BccC) as well as DefaultData/kitty.ini (https://pastebin.com/fhyK0XXs) and placed kitty.exe in the App/kitty directory.
Feel free to incorporate any of the above.
L
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Could you tell more about what kind of files OneDrive doesn't sync?
Thank You.
I'll have a look at that, when I find some time. Maybe you could leave Cyd (the dev of the base app) a note for the special charakters. Perhaps he could avoid them being created somehow.
I prefer a specific data directory over moving registry keys around as its much more robust.
@Drazick: OneDrive does not support % (among others) and the sessions files names contain %20 when there are spaces in the session names.
@depp.jones: I agree the savedir approach would be ideal, this is a quick fix taking advantage of the backward compatibility with putty.
Is there another character on the list, that is created by KiTTY appart from % in %20? The latter could be easily avoided by not using spaces in sessions names. Maybe Cyd could add a switch for avoiding these characters. Feel free to ask on their forum.
IS there a list of files names it doesn't support?
Thank You.
"list" in my previous post is linked to https://support.office.com/en-us/article/Invalid-characters-in-file-or-f...
The dark red is not the most obvious color for that.
Does anybody remember the times when links where underlined by default?
For clarification, OneDrive works fine with percent symbols in characters except for one specific circumstance. If you're using OneDrive for Business on SharePoint Server 2013, you have a big list of characters that it considers "invalid":
~ " # % & * : < > ? / \ { | }.
If running OneDrive for Business on Office 365, SharePoint Online, and SharePoint Server 2016, the list of "invalid" characters is somewhat more reasonable and basically overlaps with what Windows considers invalid in filenames:
" * : < > ? / \ |
Source: https://support.office.com/en-us/article/Invalid-characters-in-file-or-f...
If this was a widespread issue with OneDrive itself, I was going to suggest we come up with a universal solution for all apps, but as this is rather niche, I don't think this will be necessary. I may check if it's possible for the platform to determine if it's running on a OneDrive instance connected to SharePoint 2013 to warn the user since that large set of invalid characters will break quite a few apps.
Sometimes, the impossible can become possible, if you're awesome!