Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Shougo
    @Shougo
    I think neocomplete is not installed properly.
    plugin/neocomplete.vim is installed, but autoload/neocomplete/* is not.
    Tobias Witt
    @ohcibi
    hm... it got installed by dein
    Shougo
    @Shougo
    You should check dein cache directory.
    Tobias Witt
    @ohcibi
    @Shougo i've deleted that multiple times 8-)
    Shougo
    @Shougo
    So, you should check it :-)
    Tobias Witt
    @ohcibi
    @Shougo what should I actually check? I don't know how dein installs plugins, so I wouldn't see how its installed unproperly?
    plus I wouldn't knew how to fix that as I don't know what I can do else except from dein#add to add a plugin "properly"
    I cannot reproduce it anyway as it's gone after the upgrade, so it looks indeed like an issue of neocomplete that got solved by either upgrading it or by recaching
    Shougo
    @Shougo
    You can check it by ~/.vim/dein/.cache/.vimrc/.dein/autoload directory.
    I cannot reproduce it anyway as it's gone after the upgrade, so it looks indeed like an issue of neocomplete that got solved by either upgrading it or by recaching
    OK. I think so, too
    Tobias Witt
    @ohcibi
    pity that I still can't use nvim as it randomly segfaults (mostly when I Denite file_rec)
    Shougo
    @Shougo
    This is neovim problem.
    Tobias Witt
    @ohcibi
    yea
    Shougo
    @Shougo
    Please report it in neovim issues.
    I cannot fix neovim SEGV
    Using plugins.
    Tobias Witt
    @ohcibi
    i didnt ask you to... but I cannot report an issue as I cannot reproduce it with a minimal vimrc
    Shougo
    @Shougo
    I think the stacktrace and the additional information are needed.
    Tobias Witt
    @ohcibi
    so its definitly caused by some plugin.. when I use the minimalvimrc I pasted above, denite works without a problem, so there is no issue I can report
    yea but the issue will be closed as I cannot provide the minimalvimrc 8-)
    Shougo
    @Shougo
    You can create minimal vimrc denite.nvim + another plugin or configurations.
    Tobias Witt
    @ohcibi
    the issue policiy is to strict
    Shougo
    @Shougo
    I can check your minimal vimrc.
    I have read many minimal vimrcs.
    No plugins vimrc is the best. But few plugins and the minimal plugins are better.
    s/minimal plugins/minimal configurations/
    If you create it, I can check and test.
    Tobias Witt
    @ohcibi
    @Shougo I added all of my plugins to this minimalvimrc now and I still cannot reproduce it... so it must be either one of the results or something other in my vimrc
    Shougo
    @Shougo
    So it seems from configurations.
    Tobias Witt
    @ohcibi
    @Shougo i need to go to lunch now... the minimal vimrc is pasted above, but as I said: it works for me with this. my actual vimrc is here: https://github.com/ohcibi/prezto/blob/ohcibi/runcoms/vimrc maybe there is something you see on first sight.. i'll investigate this further later on
    Shougo
    @Shougo
    Hm.
    Your vimrc is not so long.
    The investigation seems easy.
    Tobias Witt
    @ohcibi
    @Shougo the complete config (including bundlrc and stuff) is in this repo in the ohcibi branch
    if you need to see something else than the vimrc
    i'll also try to bisect that file after lunch
    Shougo
    @Shougo
    Bisecting is needed...
    less than 50 lines are better.
    Tobias Witt
    @ohcibi
    @Shougo it must be the results
    of the file_rec
    if I change the directory, there is no segfault
    Shougo
    @Shougo
    Hm.
    Zhaosheng Pan
    @brglng
    Hi @Shougo , I would like to ask a question about the correct use of dein. Before using dein, I have long used vim-plug, and I put all my plugins at ~/.vim/plug, where ~/.vim is actually a symlink to a synced directory in my Dropbox, so that the whole vim configuration is synced. I continued this habit when started using dein, but I found the configuration if often broken when I have synced between different OS'es, e.g., between Linux and macOS. Then I checked the cache_* file in dein's directory and found dein records absolute paths in its cache, so that the paths are broken between different OS'es, e.g., on Linux it may be /home/username/.vim/dein/.cache and macOS it may be /Users/username/.vim/dein/.cache. I read the doc and it says the typical directory for dein is ~/.cache/dein or ~/.local/share/dein. So does that mean the correct use of dein is to put its directory at some OS-specific path, which should not be synced? As a result, do we have to :call dein#install() or :call dein#update() when setting up the vim configuration for a new computer? Thank you!
    Shougo
    @Shougo
    You can set g:dein#cache_directory for it.
    Zhaosheng Pan
    @brglng
    Thank you! This solves my problem!
    Shougo
    @Shougo
    :-)
    Zhaosheng Pan
    @brglng
    I found the caching is really a good feature. When I was using vim-plug, I have to clone several copies for YouCompleteMe and rename them to different names, and pick a specific name on specific OS. I wrote a long function doing all those. With caching, I just need to keep only one copy of the original YouCompleteMe repo at ~/.vim/dein/repo and cache it to ~/.cache/dein, which is a OS-specific path. I don't need to care about the directory names anymore, and the long function is no longer necessary.
    Zhaosheng Pan
    @brglng
    It seems Dein does not cache hooks, so the plugins add in .vimrc with hook_post_update dict entry are only correctly installed for the first time. After the vim restarted, dein#load_state() returns 0 and the hooks are not loaded for the plugins, so no hooks will be called for dein#update(). Does that mean I have to call dein#set_hook() after the dein#begin() and dein#end() block?