Fork me on GitHub
#crux
<
2020-10-09
>
jaju14:10:44

Thanks for the session! And also, thanks for all the open source work beyond crux too! ๐Ÿ™‚

๐Ÿ™ 1
jonpither14:10:31

thank you, and thanks for attending!

tbrooke16:10:32

was this recorded?

jonpither16:10:03

yes - stay tuned, we will post on here when @taylor.jeremydavid has post-processed

Steven Deobald13:10:06

Jeremy uses emacs with a white background. Very worrisome.

๐Ÿ˜ฎ 1
refset14:10:22

Only during the daytime, to boost my energy levels ๐Ÿ˜…

โ˜€๏ธ 1
Steven Deobald14:10:27

oh thank god dark mode. ๐Ÿ™

jonpither14:10:28

yup ๐Ÿ™‚

victorb14:10:06

White background club :raised_hand: (it gets sunny here, it helps!)

โž• 3
๐Ÿ”ฅ 1
dharrigan14:10:40

That's all very exciting stuff @taylor.jeremydavid et. al I look forward to playing with the new stuff

๐Ÿ™ 1
dharrigan14:10:48

Thanks for the invite and doing the demo.

Steven Deobald15:10:39

@victorbjelkholm429 (that ๐Ÿ”ฅ is me burning white backgrounds, btw...haha) i'm in northern india... it's sunny here too, but i can't look at white screens without getting an instant headache due to a bizarre eye injury. #darkmode4ever

jonpither16:10:29

tomorrow-night theme

jonpither16:10:38

or Zenburn ๐Ÿ™‚

Steven Deobald17:10:37

wow, tomorrow-night-blue instantly reminds me of editing basic files on the family 386

๐Ÿ‘ 2
Steven Deobald17:10:29

i've always loved zenburn but since the eye damage low-contrast is actually really hard for me to read. currently using some extremely cartoony monokai variant.

Bryan17:10:35

question about time and deleting in crux. Assuming I have a key 123 with data at times t0, t4, t8, if I transact a delete at t4, the data at t4 disappears. Is there a way to delete at, say, t2 and also delete the data at t4 and t8 and t(n >= 2)? (evicting 123 isnโ€™t an option because we need to preserve everything prior to the t2 delete)

refset18:10:38

We don't have an API to do that in one step, but you can achieve the desired result by scanning through the entity history and deleting one by one (underneath the hood we'd still need to be doing the same kind of scanning anyway). The only downside of a non-native approach is the bloat in the transaction log for each delete op

Bryan20:10:43

thatโ€™s the route I was about to start heading down anyway, thank you!

๐Ÿ™‚ 1
๐Ÿ™ 1