jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
<dlcusa> beerman, nice!
<dlcusa> beerman, ignore typo ^
<Romster> core/zstd links with contrib/lz4 I feel lz4 should be moved to core, comments, vote?
<beerman> you feel? :D
<beerman> is this for aria2c support you are working on? what benefits do we have from lz4 in core?
<braewoods> beerman: we can compress Romster's beard in realtime now. :P
<beerman> XD
<braewoods> but i see no harm in more compression libs in core
<braewoods> they usually don't consume much space as it is
<braewoods> i often use lz4 for quick compression jobs where i don't want to wait on xz
<braewoods> having it as an option for stuff like makepkg could be helpful if you're doing multiple builds of a port to test stuff
<braewoods> it's the fastest compression algorithm i know of
<braewoods> err pkgmk
<braewoods> sorry, used to ARCH :P
<SiFuh> I use lz4 for my kernel
<Romster> that's a shame
<Romster> kidding
groovy2shoes has quit [Ping timeout: 252 seconds]
<ivandi> about vim: perl and python3 are in core, so it makes sense to compile vim with --enable-perlinterp=dynamic --enable-python3interp=dynamic
<ivandi> for example clang_complete plugin needs python compiled in
<beerman> i thought about it, i even had a vim fork for a long time for python3 support, but neovim is where the fun is
<beerman> if opt/neovim can't replace core/vim, i'd say lets keep core/vim as lean as possible
<beerman> but nowadays there are CRUX installs i don't have core/vim installed at all anymore, nvim is just better ¯_(ツ)_/¯
groovy2shoes has joined #crux-devel
<ivandi> well, adding stuff that is in core wont make vim less lean, and vi is lean enough
<beerman> i'd say talk to jue and jaeger about it
<beerman> if sudo and its visudo is the only reason we build vi anyway i'd say replace both with saner defaults ;)
<beerman> any specific reason you want that in vim and not install neovim?
<ivandi> never used neovim
<beerman> it really depends on your personal vimrc, but it should be perfectly compatible with it...
<ivandi> vim + clang_complete is just enough for my needs
<beerman> neovim has a native lsp plugin that works with clangd
<ivandi> i will look at it when i have some time to waste
<beerman> ¯\_(ツ)_/¯ can only recommend checking it out
ivandi has quit [Quit: WeeChat 3.2.1]
ivandi has joined #crux-devel
ivandi has quit [Quit: WeeChat 3.2.1]
ivandi has joined #crux-devel
SiFuh_ has joined #crux-devel