<cole-h>
The reason that PR didn't get evaluated originally is because the eval filter was choking on an unknown variant at the time. This has since been fixed.
<hexa->
ok
<hexa->
thank you
<cole-h>
:)
<LnL>
also unicode / inconsistency is annoying for other usecases like grep
<cole-h>
s/for other usecases like grep//
<LnL>
why not have git log | grep '->' just work?
<cole-h>
Would be nice...
<cole-h>
And just think about all the Unicode right arrows... We'd have to support a lot more than just `->` if we ever implement 318
<cole-h>
Some are obviously nonsense, but there are a few that are somewhat vanilla (yet different)
<hexa->
fwiw, it's the result of compose + - + >
<hexa->
→
<LnL>
there's a convention to make these kind of things nice, if we don't follow it there's not really a point to having the conventions
<cole-h>
Or you could cut out 3 keys and just do `->` like the rest of us plebeians without a compose key ;^)
<hexa->
I will :)
<cole-h>
<2
<cole-h>
<3
<LnL>
at least that's how I think about it
<hexa->
makes total sense
<cole-h>
LnL++
<{^_^}>
LnL's karma got increased to 59
<MichaelRaskin>
cole-h: As for keys, for me -> is three keys (minus; shift-dot=greater) and → is actually 2 (ISO_Level3_Shift+i)!
<cole-h>
Fair enough.
<cole-h>
Maybe we change it to `attr: v1 to v2` :D
<MichaelRaskin>
But improving simple grep usability is indeed an argument for unification, and -> is probably best from the _maximum_ keypress point of view across layouts
<MichaelRaskin>
(note to self: create a «to» package for… something)
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<cole-h>
Might also explain the 2 missing aarch builders
<LnL>
probably
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<LnL>
urgh build error with the update, could you also restart it?
<gchristensen>
hm?
<cole-h>
The travis run, I assume
<cole-h>
LnL: (though pedantry still fails)
<LnL>
yeah, but the nix-build too
<cole-h>
Right, but if you push a commit fixing the pedantry check, it'll start a new job, including nix-build... :P
<LnL>
don't follow
<LnL>
no `native_tls_crate` external crate
<cole-h>
I was saying you could restart the travis run yourself just by pushing another commit (e.g. fixing the cargo fmt error from the pedantry check)
<LnL>
gchristensen: restarting the comment poster
<cole-h>
lol sorry :D
<cole-h>
I completely misunderstood
<cole-h>
(and caused gchristensen to restart the travis build on the lapin bump lmao)
<LnL>
oh boy
<cole-h>
x)
<LnL>
I certainly confused y'all didn't I :)
<cole-h>
Or me, at least hahaha
<gchristensen>
restarted :)
<LnL>
ok great, hopefully somebody looks at the issue soon
<LnL>
maybe it's something straightforward that could still be fixed before 1.0 :)
<cole-h>
But I think it will be fixed anyways. The guy(s) in charge seem eager to clean out their issue tracker (by fixing bugs and answering questions, that is).
<LnL>
yeah
<LnL>
part of the reason why I liked the idea of switching to it
<cole-h>
Don't forget being able to drop openssl 1.0.2u :D
orivej has quit [Quit: No Ping reply in 180 seconds.]
<LnL>
last real change in rust-amqp was 2 years ago