On 07/09/16 11:58, Gustavo Niemeyer wrote:
> They can install it as devmode, and we can also introduce an
> "editor-support" interface which gives global read/write access to it.
I like the idea of this, specifically excluding global execute (which
something like a chef snap or juju agent snap
Hi Gustavo, devmode was what I was thinking, I'd not consider an interface
like that, I'll look into it
Thanks
Matty
On Wed, Sep 7, 2016 at 11:58 AM, Gustavo Niemeyer <
gustavo.nieme...@canonical.com> wrote:
> They can install it as devmode, and we can also introduce an
> "editor-support"
They can install it as devmode, and we can also introduce an
"editor-support" interface which gives global read/write access to it.
Would need to be manually connected for the time being, but assertion
control for that is coming very soon.
On Wed, Sep 7, 2016 at 7:40 AM, Matthew Williams <
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
Can you change neovim to look for these dot files elsewhere, like
$SNAP_USER_DATA (if I didn't typoed the var name)?
On Fri, Aug 26, 2016 at 1:19 PM, Matthew Williams <
matthew.willi...@canonical.com> wrote:
> Hey folks,
>
> So I decided to have a go at snapping neovim (htt
Hey folks,
>
> So I decided to have a go at snapping neovim (https://github.com/mattyw/
> neovim/blob/01-snapcraft/snapcraft.yaml)
>
> Getting it going with devmode was easy - I loved not having to mess around
> with confinement while getting the rest of the snap working, that'
Hey folks,
So I decided to have a go at snapping neovim (
https://github.com/mattyw/neovim/blob/01-snapcraft/snapcraft.yaml)
Getting it going with devmode was easy - I loved not having to mess around
with confinement while getting the rest of the snap working, that's a great
feature.
My problem
