compile option/static loading #67
Comments
Hi @mkwmms, Sorry, but I have no plans of adding this to the project mostly because of the issues you cited above... Thanks! |
I just realized a good way of doing that, it's kind of hacky, but will work just fine ;) |
@mkwmms please check the Hacking session of the readme, that should do the trick. https://github.com/caarlos0/antibody#hacking Let me know if it doesn't. Thanks! |
@caarlos0 clever hack! I like it. Will do! 😄 some thoughts: However, I like this go implementation a lot better than my ruby script. Would it be totally off this projects' design goal if you explored fish shell support? I haven't explored this idea much but it might be as simple as changing this line. Fish support is pretty easy because anything in Anyway if it is something you wouldn't mind exploring I can open a new issue and work on a fork. I would love to use antibody across linux and OS X, some of which I can't change my default shell to zsh (and I am stuck with bash) so it would be cool if antibody could handle multiple shells (as far as I can see it kind of already unofficially supports bash via |
@mwilliammyers check version |
@caarlos0 will do, thanks! |
@mwilliammyers just now I read your previous comment about fish support.. I guess we can do that, yes. Maybe some --fish global option or something... will require some changes in design... but, yeah, would work 👍 |
let me know if you still interested =) |
I can understand if this is beyond the scope of antibody/not the design goal of antibody but...
In an effort to make antibody even faster than it already is, what do you think about having an option to "compile"/statically load your current bundles?
For example, if you had a
plugins.txt
that looked like:and then had
antibody bundle < plugins.txt
in your~/.zshrc
; this "compile" option would simply create a file with all the full paths to source and would look something like:and then in
antibody.zsh
it would first check for the presence of this file and if it was found it would just dosource name_of_this_file.zsh
instead of doing what it does now (i.e. running the go binary and sourcing the necessary files)However, something that would have to be figured out would be if the user has a
~/.zshrc
like:instead of the faster way of doing
antibody bundle < plugins.txt
it would be tricky to know when to dosource name_of_this_file.zsh
, because you wouldn't want to dosource name_of_this_file.zsh
for everybundle <some repo>
in~/.zshrc
... That is, unlessantibody compile
was a completely separate command fromantibody bundle
.or am I missing something and this would not actually improve the speed of antibody? (not saying that antibody is slow by any means though...)
I guess my motive is to make my dotfiles completely modular in the sense that I would use antibody to bundle just about everything in my dotfiles. The only downside to doing this is that antibody would, I imagine, inherently be slower than just directly sourcing the files how I normally do in my dotfiles. (As well as it won't add things to
fpath
, if I am not mistaken, but that would be a separate issue...)The text was updated successfully, but these errors were encountered: