<FromGitter>
<watzon> Lol ⏎ ⏎ > Just running kak launch a new kak session with a client on local terminal. Run kak -help to discover the valid command line flags.
<FromGitter>
<watzon> kak
<FromGitter>
<watzon> That's awfully close to another word...
wymillerlinux has quit [Ping timeout: 248 seconds]
wymillerlinux has joined #crystal-lang
<alex``>
watzon which word?
<FromGitter>
<watzon> kak
<FromGitter>
<watzon> Sounds like a New Yorker saying something else
chemist69 has quit [Ping timeout: 252 seconds]
chemist69 has joined #crystal-lang
sz0 has quit [Quit: Connection closed for inactivity]
pabs has quit [Ping timeout: 268 seconds]
alex`` has quit [Ping timeout: 248 seconds]
alex`` has joined #crystal-lang
<FromGitter>
<watzon> How do you provide multiple requirable files? For instance I want people be able to say either `require "tourmaline/bot"`, `require "tourmaline/client"`, or `require "tourmaline"` which requires both.
<FromGitter>
<mwlang> That's how I'd structure it... tourmaline.cr can have the two require statements for client and bot and that would satisfy your goal.
<FromGitter>
<watzon> Awesome. Just making sure that that's how it works
<FromGitter>
<mavu> @alex`` "kak" is short for "Kacke" in german, which is colloquial term for "shit" in the context of swearing when things are not working or going wrong. ⏎ In my day to day life most often encountered when I need to touch anything related to / coming from Microsoft.
<FromGitter>
<mavu> The editor sounds very interesting though.
<FromGitter>
<watzon> @mavu it does, but for some reason can't get it to compile on my system
<FromGitter>
<mavu> I can just install it with apt on debian.
<FromGitter>
<watzon> Oh really? Let me try lol
<FromGitter>
<watzon> @mavu where's the repo?
<FromGitter>
<mavu> @watzon I use debian testing, so if it is not available in stable, you will probably have to add testing to your sources.list
<jokke>
speaking of editors: anyone here using (neo)vim with neomake for crystal?
<jokke>
i find the errors pretty unhelpful :/
<jokke>
e.g. just "in block..." at the outer block if something inside the block causes compile errors
<jokke>
is syntastic doing a better job?
<FromGitter>
<mavu> I still have not managed to seriously test neovim. Just played around with it for some hours.
<jokke>
it's exactly the same in vim. That's why i put it in parentheses
<jokke>
for me switching to neovim was just a matter of aliasing vim to neovim :P
<FromGitter>
<mavu> I think I'll need to weed out some stuff, neovim seems to have trouble finding my colorscheme and throws some python errors on startup when I give it my vimrc.
<mps>
j8r: thanks. I'm short on time these days but will look it deeply when we release new stable Alpine
<FromGitter>
<j8r> 1) 29.0 will be out soon, wand this PR will likely not be inside it :/
<mps>
aha. did you tried to build it with this patch
<FromGitter>
<j8r> why having 0.29.0 2 months after 0.28.0, but 0.28.0 6 months after 0.27.0? Don't know
<FromGitter>
<j8r> not yet
<FromGitter>
<j8r> not yet on armhf, just x86-64
<mps>
it shouldn't be problematic on x86_64 and aarch64
<FromGitter>
<j8r> I have to cross compile :/ Or, I may be able to build an armhf compiler on aarch64
<mps>
I tried cross compiler on alpine, but without good results
<mps>
simple programs works but more complicated is problematic
<FromGitter>
<straight-shoota> @j8r 0.28.0 was simply way to much delayed
<FromGitter>
<straight-shoota> we aim to release more often
<FromGitter>
<straight-shoota> So 0.30.0 won't be too far away
<z64>
i wanted to ask about the changelog, maybe it was discussed before, but there's a lot of conversation in other threads; should deprecations be marked as `(breaking-change)`? i feel a `(depreacted)` annotation is more apropriate as code should still work, and the `(breaking-change)` would be listed when the old api is removed
<FromGitter>
<straight-shoota> z64, there was a discussion on this, and we decided to mark deprecations as breaking change. While not *immediately*, the code will eventually break.
<alex``>
mavu Debian has a *very* old (maybe 2y) release
<alex``>
you should compile from source
<alex``>
I added support for Crystal a few days ago, so better to use the master branch for Crystal anyway
<z64>
@straight-shoota alright, that's fine i guess. was just curious if it was brought up. thanks
<alex``>
if you install from source, you just have to make sure to have a recent gcc or clang, with ncruses (wide-characters support)