<lovesegfault>
pie_: subtrees will remain as separate repos, no?
<pie_>
n..o?
<lovesegfault>
guess idk how subtrees work
<pie_>
i recommend playing with it a bit
<lovesegfault>
abathur++
<{^_^}>
abathur's karma got increased to 23
<lovesegfault>
that sounds like it
<pie_>
i guess you could say git subtree is a sort of a frontend to a mere
<pie_>
merge
<pie_>
that link looks like it might be simpler and better here depending on what you want
<pie_>
(i.e. probably)
<lovesegfault>
I don't need this yet, mostly thinking if it'd be possible
<lovesegfault>
but I need to do it to like, 10 repos
<lovesegfault>
inb4 big brain moment
<pie_>
what if you put....all the repos in one repo
<MichaelRaskin>
You end up thinking about branch name, corruption resilience, etc., and reinvent Monotone
<MichaelRaskin>
Or suffer
<pie_>
:D
<pie_>
meguca is suffering
<pie_>
eyJhb: next thing to implement would be something like bidirectional i/o over files or something so i can do stuff like use a python repl remotely over HTTP GET but idk
<hodapp>
you can sorta already do that with Jupyter's protocol
<pie_>
huh
<pie_>
i guess that would make some sense
<pie_>
though maybe what i should really do is mosh over http get :P
<pie_>
because latency will be terrible since this is like, io over an sql injection exploit
<pie_>
though that in and of itself shouldnt necessarily be slow so idk
<hodapp>
o_O
slack1256 has joined #nixos-chat
<pie_>
hodapp: see the terrible repl i linked above :P
patagonicus0 has joined #nixos-chat
patagonicus has quit [Ping timeout: 246 seconds]
dotdotok has quit [Ping timeout: 240 seconds]
joe[m]1 has joined #nixos-chat
waleee-cl has quit [Quit: Connection closed for inactivity]
Sigyn has quit [Read error: Connection reset by peer]
Sigyn has joined #nixos-chat
patagonicus0 has quit [Ping timeout: 252 seconds]
slack1256 has quit [Ping timeout: 268 seconds]
<ashkitten>
now that i have a 49 inch 5120x1440 monitor, i can finally write python list comprehensions
* samueldr
sobs
<samueldr>
two identical (where it matters) user environments, yet somehow one works and the other doesn't with plasma mobile shell
<samueldr>
environment meaning: `env`
<samueldr>
and nixos configs mostly identical... but running the same wayland environment the same way
<samueldr>
there *must* be a difference for it to break, but I have yet to find it
<samueldr>
and it's software that doesn't complain when things are wrong :(
lukegb has quit [Quit: ~~lukegb out~~]
lukegb has joined #nixos-chat
<ashkitten>
i think the thing i didn't realize before i got the ultrawide monitor was actually how nice it would be to have all this horizontal screen space
<ashkitten>
i can have a game open, and open a window next to it, and the game still plays completely fine just slightly skinnier
<ashkitten>
whereas in 16:9 aspect ratio if i opened a window next to my game it would feel incredibly cramped
<Ke>
doesn't cargo support that vendoring thing where you don't have network access
<lovesegfault>
Should yea, cargo vendor
<Ke>
at least you can specify absolute local paths in that file I forgot the name of
<Ke>
Cargo.toml or whatever
<Ke>
or relative local paths
endformationage has quit [Quit: WeeChat 2.9]
<aaronjanse>
I like it lovesegfault
<cole-h>
lovesegfault: is that using zola?
<aaronjanse>
(I think it's zola, based on the HTML)
<lovesegfault>
nope, hugo
<aaronjanse>
Oh huh
<lovesegfault>
zola lacks too many features
<lovesegfault>
I tried it today
<lovesegfault>
and it was a pita
<aaronjanse>
I tried last week and came to the same conclusion
<aaronjanse>
Side note, it would be cool to have a `htop` mode that shortens /nix/store paths
<aaronjanse>
Probably as a patch applied via `overrideAttrs`
<aaronjanse>
If `h` stands for Haskell... hopefully it doesn't
<cole-h>
just go to setup and disable "Show program path"
<aaronjanse>
Oh no it's C
<cole-h>
F2 -> Display options -> Show program path
<aaronjanse>
Oooh
<aaronjanse>
:O TIL that page exists!
<aaronjanse>
WOW that's much easier to read
<lovesegfault>
I started writing a post on why arrays are not pointers in C years ago. I recall there were three main reasons. I stopped halfway and now I can't recall what the other reasons were
<lovesegfault>
:P
<ar>
there's no such thing as an array in C
<lovesegfault>
That's not true, they exist
<lovesegfault>
in their creation scope arrays are like fat pointers
<lovesegfault>
you just can't get them out of the creation scope, they get demoted to a pointer to the first element
<ar>
effectively it's just a continous blob of memory you choose interpret as a sequential list of entities and guess the number of elements of
<lovesegfault>
gchristensen: omg I can't believe you got that phone number, lol
<lovesegfault>
641-NIX-HELP lol
<lovesegfault>
gchristensen++
<{^_^}>
gchristensen's karma got increased to 448
<lovesegfault>
10/10
rajivr has joined #nixos-chat
waleee-cl has joined #nixos-chat
MichaelRaskin has quit [Ping timeout: 268 seconds]
<eyJhb>
Sometimes stuff like this is a little, why? `copying path '/nix/store/irqwv613fscy7bccixcjkc877h2wl6yl-openelec-dvb-firmware-0.0.51'`, why is this needed on my router? :\
<eyJhb>
lovesegfault: Where did you dox gchristensen ? :o
FRidh has joined #nixos-chat
<Ke>
what phone?
<Ke>
448 is a reasonable substring in a valid password, but not sufficient by itself
<samueldr>
I guess the disk image creation somewhat changes the dates
<samueldr>
the top one is what's in the not-working VM
<samueldr>
which is using a fresh squeaky clean disk image with fake'd time
<samueldr>
so I guess I will change that fake time to 1s
<MichaelRaskin>
Well, the bottom also has fresh ctime
<samueldr>
because, as can be observed on the other screenshot, indeed Modify is at 1s
<samueldr>
yeah, that also
<MichaelRaskin>
Maybe it is the rebuild that matters and after something (hm, what? copying between stores? optimise?) sets everything to Epoch+1s you get a failure again?
<samueldr>
but it's been a over another day of work lost on *yet* another caching shenanigan from KDE
<MichaelRaskin>
There is some small amount of point in the idea that KDE-based images are not really older than 1980…
<samueldr>
AFAIUI they're using "0" as value meaning that something is wrong
<samueldr>
instead of it being a totally cromulent value for a timestamp
<samueldr>
my main gripe is how awfully hard to debug those kind of issues are with KDE... no errors, generally and debug log is normally hidden
<samueldr>
I had to enable the firehose of debug logging to see that message that hinted at something being weird
Thunderbi is now known as nckx
<lovesegfault>
Is there a single term I can use to reference something when it's being either passed to a fn as an arg or being returned from a fn?
<lovesegfault>
scope-crossing?
<samueldr>
so yeah, having epoch+1 as a date is fine
* samueldr
commits angrily
<__monty__>
lovesegfault: Curious what you need such a concept for?
<lovesegfault>
__monty__: talking about the behavior of arrays in C
<lovesegfault>
and how whenever they cross a scope they are demoted to a pointer
<lovesegfault>
and I need to title the section
<lovesegfault>
and.. uhhh. I don't know what to call it
<__monty__>
Étude sur les vagaries d'un array cuand il se creuse une frontière d'étendue?
<__monty__>
Don't have serious advice. Something about demotion of arrays whenever they cross a scope boundary.
<samueldr>
d'un tableau* quand*
<samueldr>
:)
<__monty__>
I knew something about the cuand was wrong.
<__monty__>
Been practicing too much spanish with its cuatros.