The snap is currently using:
Your case for not usng SNAP_USER_DATA makes some sense, but I can say that you should be able to have vim conditionally use
$SNAP_USER_DATA/... through the ‘current’ symlink and fallback to $HOME. Can you comment why this doesn’t work for you?
As it stands, your snap is the clear owner of
$HOME/.strc is less clear and
$HOME/.local/log/stimmtausch won’t work well since
$HOME/.local/log/ is non-standard, not guaranteed to exist and your snap won’t have the permissions to create it.
Furthermore, the personal-files interface is most typically used for imported existing configuration and not for writing since a snap and its distro-packaged or locally-installed application may not be backward and forward compatible with the configuration files and data.
Since several requests are made in this topic and I made several points, I’ll ask a few questions to guide the conversation:
- Can you comment why using SNAP_USER_DATA through the current symlink (eg,
~/snap/ stimmtausch/current doesn’t work for you with vim?
- What is the relationship of
$HOME/.strc to your snap? (Eg, please provide a link to a doc if your snap is the owner)
- It seems like putting logs in SNAP_USER_DATA would be most appropriate. Can you comment?
- If only named pipes are in
$HOME/.local/share/stimmtausch, it seems like SNAP_USER_DATA or SNAP_USER_COMMON would be most appropriate. Can you comment?
- If you have existing users that are migrating to the snap, would read-only access to
$HOME/.local/log/stimmtausch (and possibly
$HOME/.strc depending on the answer to ‘2’) via personal-files be sufficient for you to copy these into SNAP_USER_DATA/SNAP_USER_COMMON?