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
    OK. I will fix the issue.
    I think neovim json implementation is mature than Vim.
    It seems Vim 8.0.685 still have this problem. Well, I was just doing a test with Vim but I actually use Neovim most of the time. I can just stick with Neovim at the moment.
    Update Vim and call dein#recache_runtimepath() does not fix the problem?
    Zhaosheng Pan
    @brglng
    No, it does not.
    Shougo
    @Shougo
    Hm...
    I will use json_encode() / json_decode() instead.
    js_encode()/js_decode() is faster, but it seems broken.
    Zhaosheng Pan
    @brglng
    Thanks. I will try to figure out a minimal test case to reproduce the problem and report to Vim if I get time...
    kronos29296
    @kronos29296
    Hi, I use dein to manage my plugins. Since I have a slow internet connection I increased the timeout and the number of processes to 1. But when the processes is 1 it blocks the ui and I cannot edit text. Is it a bug or the default behaviour? For now I have set it to 2.
    Shougo
    @Shougo
    It is not a bug.
    If it is 1, asynchronous feature is disabled.
    kronos29296
    @kronos29296
    Thanks
    MiSawa
    @MiSawa
    It looks on_source event is not fired for non-lazy plugins. Is this an intended feature?
    Shougo
    @Shougo
    Yes. 
                            *dein-options-on_source*
on_source    (List) or (String)
        Load the plugin before the listed plugins are loaded.
        Note: The plugins must be lazy loaded plugins.
    Because, the on_source() event slows your startup time.
    You can call on_source() manually by dein#call().
    MiSawa
    @MiSawa
    Oh sorry, my bad.
    I don't find dein#call in :help / autoload/dein.vim. Is that dein#call_hook?
    (And I'm guessing that call_hook is the thing to fire hook_*)
    Shougo
    @Shougo
    Ah, dein#call_hook().
    MiSawa
    @MiSawa
    Hmm... Is there a way to source plugin B before plugin A is loaded (same as A depends B) where we can write the config in B's configuration section?
    Shougo
    @Shougo
    on_source
    MiSawa
    @MiSawa
    ... and applicable for non-lazy?
    Shougo
    @Shougo
    Nothing. You must use be lazy.
    The source order is complex.
    The startuptime is important for me.
    MiSawa
    @MiSawa
    Oh I see, I guess I should ... Thank you!!!
    Shougo
    @Shougo
    And other plugin managers does not support the feature.
    MiSawa
    @MiSawa
    Oh I can't edit message above. *I should trigger something when A is loaded, and add hook on B
    May be it's for-me thing, but I think it's good to have that feature for something like unite sources.
    I personally don't want to enumerate them to unit's config section.
    Shougo
    @Shougo
    I use on_source for it.
    MiSawa
    @MiSawa
    That's sounds correct approach. May be I should try make unite lazy.(I didn't investigate my configuration yet, but I got an error so I tried to find a simpler solution.) Anyway, thank you for your quick responses!
    Hendrik Roth
    @HendrikRoth
    This message was deleted
    Tobias Witt
    @ohcibi
    is build for dein#add() executed after updating the plugin as well or do I need to specify the same script in hook_post_update if a plugin needs to re-execute the build script after every update?
    Shougo
    @Shougo
    is build for dein#add() executed after updating the plugin as well
    Yes.
    You don't need to write the script.
    gisochre
    @gisochre

    Hi, @Shougo!
    do you have any examples of how you used

                                *dein#rollback()*
dein#rollback({date}[, {plugins}])

    function ? all {plugins} have to be specified explicitly?

    Shougo
    @Shougo
    all {plugins} have to be specified explicitly?
    Yes. No example though.
    Tobias Witt
    @ohcibi
    can I temporarily disable the cache competely? i'm currently debugging which of my plugins are incompatible with each other and i'm permanently unsure if I actually disabled/enabled the plugin now or not
    Shougo
    @Shougo
    You can use merged.
    I think dein#load_toml() or dein#load_dict() is easy way.
    You can specify the default option.
    Tobias Witt
    @ohcibi
    @Shougo yep i know about merged it helps for a single plugin. I was thinking about a way that disables it at once for all plugins (i.e. the equivalent of putting merged: 0 in every single call dein#add() call
    Tobias Witt
    @ohcibi
    is your idead to call load_toml or load_dict with an empty dictionary or something like that?
    Shougo
    @Shougo
    call dein#add() does not support default option.
    So you should use dein#load_toml() or dein#load_dict() or create the wrapper function instead.