You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using this lib to build a snap compatible command line tool and while declaring the snap plugs for personal-files I found that it does not consider those paths.
After I connect the personal-files interface on my snap it still does not consider $HOME/.config a valid directory.
Maybe it could consider /home/$USER as a possible location on linux, even if $HOME is present, as those two can differ in a confined deployment.
I cant use LocalPath as the order is mixed. If I read or write a config, I prefer $HOME/.config over $HOME/snap/ and only if write access to former is not possible, I want to write to $HOME/snap. That does not mean that it should not detect a possible read-only config file in $HOME/.config.
Any idea how to handle this gracefully?
The text was updated successfully, but these errors were encountered:
Currently using this lib to build a snap compatible command line tool and while declaring the snap plugs for personal-files I found that it does not consider those paths.
Output of
QueryFolders()
on an unconfined binary:which is fine. As soon as I use the same method inside a snapped binary:
After I connect the
personal-files
interface on my snap it still does not consider$HOME/.config
a valid directory.Maybe it could consider
/home/$USER
as a possible location on linux, even if$HOME
is present, as those two can differ in a confined deployment.I cant use
LocalPath
as the order is mixed. If I read or write a config, I prefer$HOME/.config
over$HOME/snap/
and only if write access to former is not possible, I want to write to$HOME/snap
. That does not mean that it should not detect a possible read-only config file in$HOME/.config
.Any idea how to handle this gracefully?
The text was updated successfully, but these errors were encountered: