Skip to content
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

Force file storage without renaming executable #25

Closed
bastien30 opened this issue May 21, 2024 · 2 comments
Closed

Force file storage without renaming executable #25

bastien30 opened this issue May 21, 2024 · 2 comments

Comments

@bastien30
Copy link

Is there a possibility of specifying file storage without having to rename all executable and without appending "--file" parameter ?

I use file storage but it seems there is almost only registry versions released on Github.

Using renamed versions seems to break interaction between differents components.
For example, if I rename pageant.exe to pageant-file.exe, it still search for putty.exe and not puttie-file.exe (by the way, I think the fact that it calls putty.exe is a bug following the renaming of putty.exe to puttie.exe), so the quick session launch doesn't works.

I understand the convenience of renaming executables to choose storage type, but I don't find it practical to use, at least in my use-case.

Is there a possibility forcing storage type no matter what executable is used ?
Or can you provides file version of latest releases ?

Thanks.

@lalbornoz
Copy link
Owner

Agree actually, I'll be providing both releases again from now on. The *-.exe mechanism is useful but not for this purpose. And yes, it should be calling "puttie.exe", that's a bug, thanks for the report.

wrt. pageant-file.exe calling puttie-file.exe: it doesn't have to, it just passes whatever backend was selected along via --file/--registry/--ephemeral (or at least it should.)

@bastien30
Copy link
Author

Thank you so much 🙏

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

No branches or pull requests

2 participants