apt-vim icon indicating copy to clipboard operation
apt-vim copied to clipboard

Error with json file construction

Open mpacer opened this issue 7 years ago • 3 comments

Just tried to do a fresh install from source, and ran into an issue:

I got:

Failed to write ~/.vimpkg/vim_config.json

(path replaced with ~ for more general search purposes)

and then

Completed setup successfully
Completed successfully.

Which looked a little odd to me, and then when I tried to do the full install, I got a bunch of json decoding errors.

Tried with envs for both python2 and python3, both had json errors (so it wasn't a unicode thing).

Then decided to actually look at the json that it wrote and discovered that the file ended with:

        "name": "tagbar",
        "pkg-url": "https://github.com/majutsushi/tagbar.git",
        "recipe": {}
    },
    {
        "depends-on": [],
        "name": "ctrlp.vim",
        "pkg-url":

I.e., it just ended in the middle of defining the piece of the json needed to grab ctrlp (which I already have installed via vundle).

I'm on OSX 10.11.6.

mpacer avatar Oct 11 '16 02:10 mpacer

Heads up…I think that this broke the rest of my vim setup. And there's no clear uninstall instructions.

mpacer avatar Oct 11 '16 03:10 mpacer

Sorry for the delayed response. First things first, to revert setup, in your home directory ($HOME, ~) you should see folders in the form of .vim.bak.1 .vim.bak.2 etc. Each time before install, apt-vim backs up the current ~/.vim folder, in case something goes wrong. To restore, inspect the backup directories to find your original (probably .vim.bak.1), and mv it to ~/.vim. Please use caution. I'll add better (any) documentation for this process.

Just for some extra details to help me try to replicate: I'm assuming you had vim plugins installed already by using another manager (ex. Pathogen) or just plain git?

egalpin avatar Oct 25 '16 16:10 egalpin

I had managed to get to a steady state after a while; but yes I had been using vundle, but not pathogen. I think pathogen might have been part of the problem but I could be wrong.

Regardless thanks for looking at this! Once that's all set up I'll try this out again.

On Tuesday, October 25, 2016, egalpin [email protected] wrote:

Sorry for the delayed response. First things first, to revert setup, in your home directory ($HOME, ~) you should see folders in the form of .vim.bak.1 .vim.bak.2 etc. Each time before install, apt-vim backs up the current ~/.vim folder, in case something goes wrong. To restore, inspect the backup directories to find your original (probably .vim.bak.1), and mv it to ~/.vim. Please use caution. I'll add better (any) documentation for this process.

Just for some extra details to help me try to replicate: I'm assuming you had vim plugins installed already by using another manager (ex. Pathogen) or just plain git?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/egalpin/apt-vim/issues/45#issuecomment-256093578, or mute the thread https://github.com/notifications/unsubscribe-auth/ACXg6H0vzbVo0CuxP8WSA24LbOmUKJw4ks5q3jPZgaJpZM4KTL7b .

mpacer avatar Oct 30 '16 18:10 mpacer