I've commented on the bug, but there's a larger question here I can't work out the answer to, which is how would a user expect neovim to be restricted when installed via a snap? It could be reasonable to suggest it can only edit files in $HOME, but that's not useful to sysadmins, so why would a sysadmin use snaps to install neovim?
Matty On Fri, Aug 26, 2016 at 6:23 PM, Leo Arias <[email protected]> wrote: > On 2016-08-26 10:53, Andreas Hasenack wrote: > > Can you change neovim to look for these dot files elsewhere, like > > $SNAP_USER_DATA (if I didn't typoed the var name)? > > That is right for the config files of Neovim itself. However, I would > like to be able to edit something like ~/.bashrc. We have a bug for that: > > https://bugs.launchpad.net/snappy/+bug/1607067 > > It doesn't have a lot of information, so feel free to expand it in the > comments. > > pura vida. > > > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > >
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
