sharkdp
Open to merge from LS_COLORS repo?
Hi! 👋 I co-maintain trapd00r/LS_COLORS.
You have a way better build system than we do. For instance, this issue https://github.com/trapd00r/LS_COLORS/issues/217 is something I can't support because the "colorscheme" is all manual.
However, we have more extensions categorized! Would you accept a PR to union our extension lists?
Hi! 👋 I co-maintain trapd00r/LS_COLORS.
Hi,
This project was a huge inspiration for vivid — thank you for still maintaining it!
However, we have more extensions categorized! Would you accept a PR to union our extension lists?
Absolutely! That would be fantastic.
@sharkdp If LS_COLORS is merged into this repo, we'd have a small bus-factor (you). I've had some useful tools die because the sole repo owner went missing and it's not possible for the community to converge on a successor fork in that scenario.
To address that, would you be open to moving vivid into a github org and/or accepting co-maintainers?
To address that, would you be open to moving vivid into a github org and/or accepting co-maintainers?
Yes, absolutely. Sorry for the late reply. I sent an invite.
@sharkdp Thank you! I shot you an email at "mail at david dash peter dot de". No hurry at all (this issue has been open for awhile, it can wait) but if there's a better way to get in touch please let me know :)