mralusw

You could also save the list of `.kak` files to be sourced for each plugin, to avoid the numerous `find`'s. I believe this is what `cork` does.. A `git` post-update...

An aside: while working on [caching `sed-bin`](https://github.com/kstr0k/sed-bin/tree/sed-cached), I've realized that a Linux filesystem allows you to use *any* string that doesn't contain NULs, and turn it into a path. For...

Ah. I was under the impression that there was going to be a huge rewrite in the way config files are generated... or something, from a discussion I can't quite...

> > However, more simply, it might also be possible to have a `dir` parameter to `plug`, which gets passed to `git clone`. Not sure what other changes this would...

> One thing I still want to do is to make it so plug.kak will have an option to skip rebuilding on each launch, in a case when you're not...

Will this be toggle-able though? One thing I like is that I can share both my `plugins` folder and my `kakrc` between `plug.kak`, `kak-bundle`, and soon probably `cork`. I'm not...

> the fact that right now `kak-bundle` works with it is a lucky coincidence It's more like `plug.kak` was already there, `git clone URL` seems the most obvious and easiest...

OK, so you're suggesting that inside the autoload part of the plugin I add ``` provide-module mod1 %{} provide-module mod2 %{} provide-module entry %{} require-module entry ``` and have users...

OK, I agree, that's what I thought would work best as well (and what I'm currently using for my [`mru-files.kak`](https://gitlab.com/kstr0k/mru-files.kak) plugin).

A more general extension could be something like `-t F!p,d`: - capitalization: F would test the symlink target (or inode itself if not a link) == file - concatenation for...