Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple pack/ dirs #20

Open
alter2000 opened this issue May 27, 2019 · 7 comments
Open

Support multiple pack/ dirs #20

alter2000 opened this issue May 27, 2019 · 7 comments

Comments

@alter2000
Copy link

I have my plugins separated in 3 pack/ directories: base/ for must-have plugins, langs/ for language-specific (mostly syntax files) and colorschemes/. The Python script reports only base/start without taking into account the other directories (which have more plugins, especially base/opt, but that one has all the lang-specific stuff I've been to lazy to move), while the rest fail.

Any idea how I can fix this? I'd really like to see the plotting features.

@hyiltiz
Copy link
Owner

hyiltiz commented Mar 9, 2020

That sounds like a situation we'd definitely want to support. Could you take a look at the .sh file and see how to run vim in your setup such that:

  • it loads every plugin in those directories (this may already be the default behavior);
  • no lazy loading is happening?

Once you can confirm that, I'll work on parsing and plotting the data. I

@alter2000
Copy link
Author

I found a bunch of stuff that is useful and some more that isn't:

  • packadd {name} works for everything that is pack/*/opt/{name}; packadd! does lazy(ish) loading
  • packloadall reloads some plugins and adds the rest from pack/*/start/*; again appending an exclamation mark tells it to cancel that if e.g. --noplugin is used.

Therefore I guess the easiest way is to just glob for everything in start/ and opt/ but I'm not sure.

@hyiltiz
Copy link
Owner

hyiltiz commented Mar 11, 2020

Therefore I guess the easiest way is to just glob for everything in start/ and opt/ but I'm not sure.

What are the Cons for doing that? If it is not much, then it is easy to implement.

@alter2000
Copy link
Author

Given that what is in start/ is loaded by default whenever vim starts (or at least for the majority of users, not sure if it's really all), I don't think there's any. After all, that's how most plugin packages work.

@hyiltiz
Copy link
Owner

hyiltiz commented Mar 12, 2020

Could you test out this file and let me know what needs to be further changed to make it work? I added a regex pattern for start and opt:
https://github.com/hyiltiz/vim-plugins-profile/blob/feature/vim8pack/vim-plugins-profile.sh

If you like, you can send me a minimal version of your vim config (.vimrc, ~/.vim etc.), so I can test it out.

@alter2000
Copy link
Author

My config is here, and a patch with some small hiccups. I have no idea how R works, but in Nix you cannot install anything through an external package manager, so I think I might also need a list of the R dependencies (because this and this) to install manually.

patch.randomextension.txt

@hyiltiz
Copy link
Owner

hyiltiz commented Mar 13, 2020

Installing the R package called tidyverse should be more than enough; I tried to rely only on ggplot2 and the base R (no packages), so a minimal requirement should just be the ggplot2 package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants