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

Initial teradesk.inf save location is the current (last used) path on given drive #15

Open
mikrosk opened this issue Feb 10, 2025 · 0 comments

Comments

@mikrosk
Copy link
Member

mikrosk commented Feb 10, 2025

I have noticed this only now, when not starting teradesk via shell = in xaaes.cnf.

Basically, Teradesk is looking for the initial teradesk.inf via shel_find. If it doesn't find it, it just asks for current drive's current directory and attaches teradesk.inf to it. And that's the path used for the first "Save settings" menu option (unless you use "Save settings as" of course).

In my case, it's c:\mint\teradesk.inf (imagine my surprise...). This is because @skaftetryne's desk_sel stores its configuration file there.

As soon as I move teradesk.inf into my $HOME or any other path visible to shel_find, it's all fine after next reboot.

I realise this is not a trivial thing to solve: if Teradesk stored teradesk.inf into e.g. $HOME, there's no guarantee the AES in use would include $HOME into its shel_find list. If it stored directly into its folder, that's barely better than the current behaviour (only more deterministic) -- user would have to manually move the file to the location where shel_find would find it.

I wonder whether using shel_find is the best idea here. TosWin2, for example, uses $HOME + $HOME/defaults + start folder + current folder. And if not found in neither of them, uses $HOME/defaults*, $HOME, start folder and finally current folder as default save path.

* actually now I see there's a bug and $HOME/defaults would never be used since it's set only if $HOME doesn't exist which is nonsense

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

1 participant