<abathur>
I'll just imagine you were waiting for me to go first
neeasade has quit [Ping timeout: 240 seconds]
endformationage has quit [Quit: WeeChat 2.9]
abstrn has joined #nixos-chat
<aleph->
infinisil: heh
cole-h has quit [Quit: Goodbye]
waleee-cl has quit [Quit: Connection closed for inactivity]
neeasade has joined #nixos-chat
__monty__ has joined #nixos-chat
<MichaelRaskin>
Me, looking at my bag of chili powder: maybe infinisil is on the middle ground between the fearful and those in need of external spices anyway.
<MichaelRaskin>
(I don't buy ramen: either of spaghetti, rice, or lentils is cheaper, and if I am not in the mood for the raw taste of those, I can just add a bit more chili powder…)
<Synthetica>
do we have data on what percentage of installs use stable/unstable?
Guest75645 has quit [Quit: Connection closed]
Synthetica has quit [Quit: Connection closed for inactivity]
<MichaelRaskin>
Theory: typing is not the hard part of your job. Practice: a ton of developers having wrist pain as a bottleneck. Hm, maybe comfortably typing _is_ the hard part for those for whom any part can be called easy?
<gchristensen>
that is sometimes true for me :)
<gchristensen>
but I should still not create variables named pcbsgttm
<MichaelRaskin>
… just variables that can be completed by pcbsgttm as a query?
<MichaelRaskin>
I think «typing is not the hard part» is more often applied to «single polished binding layout vs. whatever horror best fits the target language from som other point of view», though
<MichaelRaskin>
Intriguing: stamping relief on pasta so that pasta can be shipped flat (better logistics, also: less plastic needed to wrap) but take a shape when put into water for cooking.
<__monty__>
Cool.
<MichaelRaskin>
Might also be eventually easier to manufacture than shaping in 3D right at the factory!
<__monty__>
Isn't that just extrusion? That's a pretty simple mechanical process, no?
<MichaelRaskin>
Well, relatively. Sometimes you need a twist during extrusion, etc.
<__monty__>
Isn't that determined by the shape of the nozzle? Like the spirals that's just extruded with slanted openings I think?
<MichaelRaskin>
Relief-rising-on-flat might be easier to manufacture than those extrusion guiding parts.
omnd has joined #nixos-chat
omnd has quit []
waleee-cl has quit [Quit: Connection closed for inactivity]
<__monty__>
But I do wonder whether there's any company that has done more for programming education, kinda by accident : )
<__monty__>
They should make asm programmable from the calculators.
<ldlework>
One of my first languages was assembly because of game development back on the TI-89
<ldlework>
It's where I was first exposed to C through TIGCC
<ldlework>
One summer my friend and I built a game that was a mix of a classic roguelike and JRPG combat in TI-Basic. It took up all the calculator's memory and took 45 minutes to boot. It used overlayed saved images to implement armor and weapons you could see your character using during combat. We used graphing animations for magic spells.
<ldlework>
I think it would've been pretty awesome Python had been available. When you're in middle school your world is really smal.
<gchristensen>
I completely agree
<gchristensen>
I flunked geometry after my teacher accused me of plagiarism after I showed her some programs I made ..
<siraben>
gchristensen: what the heck, that's crazy
<siraben>
__monty__: asm technically is programmable from the calculators, but it's in hex 😂
<MichaelRaskin>
Frankly, nowadays. the calculators are abominations propelled by testing procedures. We need more people do hardware replacement hacks to undermine the trust.
<gchristensen>
that single incident didn't cause me to fail, but I stopped having any respect for her or care about what she thought or taught, so
cole-h has joined #nixos-chat
<__monty__>
I kinda enjoyed the zen experience of programming the calculator using only the calculator.
<__monty__>
Train commutes once or twice a week were when I had most time for this. Re-interpreting a bunch of hex once a week doesn't sound like a sustainable activity : )
<ldlework>
looks exactly the same
<ldlework>
i remember when i was 12 or 14 or someshit, following a tutorial to implement a custom interrupt handler to allow my games to show pixels for a certain percentage of the time which made for greyscale
<ldlework>
it was like the most complex thing i had ever thought about at the time and i remember anguishing over it for weeks lol
<cole-h>
cleaned up my IRC autojoins a bit. from ~30 down to ~20
<siraben>
ldlework: yeah ti-calc is great
<gchristensen>
I'm having one of those "why is my terminal history not infinite" days ...
<cole-h>
the first thing I do when configuring a terminal is to bump the history up to like 1 million lines
<MichaelRaskin>
If you are configuring a terminal, that's scrollback\
<MichaelRaskin>
History is in shell
<ar>
gchristensen: because you didn't check the checkbox in Konsole settings?
<MichaelRaskin>
(And anything you want to find later, belongs to scripts or at least snippets!)
<gchristensen>
half of it is because I haven't changed bash to stop thething where it overwrites its own history
<MichaelRaskin>
oh right
tomberek has joined #nixos-chat
<gchristensen>
ah, no matter, I found the command I needed in the distributed command history log
<hyperfekt>
ugh. i've been trying to get these systemd units right for so long now and i don't think i can do it
<hyperfekt>
maybe the pr is not meant to be
<__monty__>
Maybe you should strive for "Meh, good 'nuff." Rather than "right?"
<hyperfekt>
maybe. it *does* work, it just spams the journal with all the failed attempts lol
<__monty__>
Ouch, ok. That's kinda painful when you need to troubleshoot 😬
lunc has joined #nixos-chat
<abathur>
gchristensen cole-h I have yet to actually build or bolt a good search onto it, but I've been databasing my history for a while now in part because I wanted ~infinite retention without having to pay the load-time penalty for a large history (partly because I leave a fairly large number of terminal tabs open, so it's like ~25x the penalty...)
<gchristensen>
:D how do you do that?
<abathur>
which is mostly just to say, if you uncap your history, and notice some day that your terminal seems to take a while to load, remember to check how big your histfile is, and maybe intentionally time how long the history builtin takes to load it
lunc has quit []
<MichaelRaskin>
I would assume temporary suffixes for history files, instructing shell to flush history on each command, and processing the history files left behind from time to time…
cole-h has quit [Ping timeout: 240 seconds]
lunc has joined #nixos-chat
<abathur>
gchristensen: not sure how generally or specifically you mean, but specifically I've been developing it as https://github.com/abathur/shell-hag for a while, though I haven't had time to really sand down sharp corners enough to encourage anyone else to live with it
<abathur>
there are other presumably better-polished options here (in fact there's one on lobsters atm), though some involve web services while I've been bolting my ~sync mechanism on top of my git/dotfiles
<abathur>
I mostly DIYed because I wasn't happy with the overlap between some things in my profile that needed the same data and all had their own hooks and were re-doing the same work; I wanted to drop down one level and build a more abstract/agnostic shell profile thing (https://github.com/abathur/shellswain) that smaller/less-totalizing profile modules can build on
<abathur>
surprised I've only accumulated a little under 63k commands over ~2 years
rajivr has quit [Quit: Connection closed for inactivity]
<hyperfekt>
yay
<hyperfekt>
i figured it out
<hyperfekt>
it's always a recipe for confusion when there's a lot of magic instead of a lot of abstraction
<gchristensen>
gosh I regret not setting up compression ...
<gchristensen>
up to 4G ... not sure if I should give up and start again with compression or not
<lukegb>
nit: why ssh host1 -- ssh host2 rather than ssh -J host1 host2
<gchristensen>
yeah maybe a good idea
<gchristensen>
this query took 11 minutes: update Builds set finished = 1, buildStatus = '0', startTime = '1620488400', stopTime = '1620488467', size = '5904848', closureSize = '5904848', releaseName = NULL, isCachedBuild = '0', notificationPendingSince = $4 where id = '142731055'; th
<lukegb>
presumably blocked on something else?
<gchristensen>
yea
<hyperfekt>
nvm it still doesn't work 🙃
<gchristensen>
the builds table seems to be the only table blocking queries
<gchristensen>
I'm betting it is the transaction loading a new evaluation's derivations
<aleph->
What's pg-badger for?
<gchristensen>
checking on the health of hydra's database server
<samueldr>
to badge postgresql databases
<gchristensen>
looking for obvious problems
<MichaelRaskin>
Hm. So the fastest way to get «immune» relaxation of disease control measures in Germany is to get CoViD-19 then recover… Hmm but I might have had it but PCR came back negative (not that low rate of false negativity, though). Hmm but new strains?
<{^_^}>
ellie/atuin#19 (by ellie, 7 weeks ago, closed): Do away with FZF usage
<supersandro2000>
if anything goes wrong there and we know things usually go wrong eventually then you can be pretty fucked
<gchristensen>
yep
waleee-cl has joined #nixos-chat
<gchristensen>
this is fantastic
<supersandro2000>
technically bash can already add the date via HISTTIMEFORMAT
<supersandro2000>
fzf strips that by default but I am sure you that can be changed
dotlambda has joined #nixos-chat
<supersandro2000>
we know npm depedencies dumped ENVs/ran commands and uploaded that somewhere. If such an attack would dump ``~/.local/share/atuin`` then they could maybe remotely download your history which might contain sensitive data without you knowing
<supersandro2000>
they could do that with the initial attack but that could be fixed after a few months and wouldn't be a continuous stream of what you type
dotlambda has quit [Client Quit]
<supersandro2000>
similar to when someone has an active iCloud login of you and just syncs all data down
dotlambda has joined #nixos-chat
<supersandro2000>
worst part you actually wouldn't notice it at all. Hosting your own server might or might not fix that. Probably depends on if it is publicly reachable.
<gchristensen>
yeah, this doesn't land with me. my shell history isn't the most sensitive stuff on my computer. I'll just have to host it well :)
dotlambda has quit [Client Quit]
tomberek has quit [Ping timeout: 240 seconds]
dotlambda has joined #nixos-chat
dotlambda has quit [Client Quit]
<MichaelRaskin>
The eternal integrity/privacy/availability tradeoff…
dotlambda has joined #nixos-chat
dotlambda has quit [Client Quit]
dotlambda has joined #nixos-chat
<elvishjerricco>
gchristensen: Got a nixos module for setting up atuin? :)
<aaronjanse>
Ahaha I was about to ask the same thing
dotlambda has quit [Client Quit]
dotlambda has joined #nixos-chat
<gchristensen>
I just bodged it on a test system :) playing with it now
<aaronjanse>
Yay
dotlambda has quit [Client Quit]
dotlambda has joined #nixos-chat
<aaronjanse>
Aww it doesn't have fish compatibility
<MichaelRaskin>
Fun. Arithmetic average predicted time of reentry from time to time gives a point far north — but perigee is actually to the south of the equator, so reentry far north is out of question
<aaronjanse>
Tbf fish already records a lot of histor metadata
<samueldr>
anyone has a good strategy to annotate a source tree without directly adding comments in it?
dotlambda has quit [Client Quit]
<samueldr>
trying to make sense of a semi-large codebase
<__monty__>
I'd like to know too.
<samueldr>
right now I add comments and hope I don't accidentally include them in a commit
<__monty__>
I've been using markdown with codeblocks with inline comments : /
<__monty__>
For something small though.
<samueldr>
e.g. right now I adde // <-- see otherfile.c 'some textual comment'
<MichaelRaskin>
Another worktree with a different branch just for adding comments?
<samueldr>
that would be basically the same as how I do, but with the added benefit of probably not adding comments to commits, but losing the ability to "merge" my WIP with the annotations
<samueldr>
I think that this is something an IDE would need to handle
<MichaelRaskin>
Well, you can merge the work commit into annotations branch
<samueldr>
maybe, though I was looking forward to recommendations of things people were actively using :)
<MichaelRaskin>
I would hope that «let's write down what's going on and never tell anyone» is not that frequent of a usecase…
<samueldr>
hm?
<samueldr>
in my case it's things like // what the hell is going here?
<samueldr>
hoping to later solve the question
<samueldr>
or even simplet
<samueldr>
"bookmarking" places I'm looking at
<samueldr>
simpler*
<__monty__>
I'm sure people do use vim marks : )
<MichaelRaskin>
Presumably the end state of each comment is a comment that should be there! But right now, some are just TODO:NAC (needs a comment)
<samueldr>
doesn't seem to allow adding a comment to the mark
<samueldr>
or making different "topic" sets of marks
<__monty__>
No, but you said "even simpler, bookmarking places I'm looking at."
<samueldr>
I might also never need to figure out what is going on at a place, MichaelRaskin, since it often happens in my case I'm looking at the wrong place :)
<__monty__>
That's what vim's marks are pretty much.
<samueldr>
yeah
<__monty__>
Especially capitals.
<samueldr>
too simple
<elvishjerricco>
Not even sure how to install this on nixos. Never messed with rust+nixos
<samueldr>
I'm not easy to please!
<elvishjerricco>
470 dependencies for this thing... whoa
<elvishjerricco>
gchristensen: I'm happy to IFD naersk itself until I switch to flakes
<lovesegfault>
example Naersk + Fenix + Flake
* colemickens
got his answer, I think. thanks :)
<gchristensen>
colemickens: ah, I got around that pretty easily
<elvishjerricco>
gchristensen: I'm a bit surprised you had to add the libsodium stuff. When I built with nixos-unstable, I didn't need anything like that.
<andi->
does naersk properly work with large workspaces where I package a few targets with the same dependencies?
<elvishjerricco>
Hm, with naersk, it appears I will need that libsodium stuff
<lovesegfault>
andi-: I tried it with my work's workspace, which is very large, and it worked fine fwiw
<lovesegfault>
it was a while ago, so I don't remember details
<andi->
alright gotta try that
supersandro2000 has quit [Killed (card.freenode.net (Nickname regained by services))]
supersandro2000 has joined #nixos-chat
<andi->
lovesegfault: but it isn't caching the dependencies between different targets, is it? I remember that was one of the selling points but it is recompiling them now :/
<gchristensen>
remarkable ... it looks like the bash manual doesn't document the `time` builtin?
<samueldr>
it does
<samueldr>
but it's not a builtin
<gchristensen>
oh?
<samueldr>
it's under `SHELL GRAMMAR`
<samueldr>
under Pipelines
<samueldr>
because
<gchristensen>
ah ha!
<samueldr>
yeah, just because
<samueldr>
ain't that just fun :)
<gchristensen>
I wish it had a "print on one line" mode
<abathur>
not just because? time is a shell keyword
<abathur>
oops, "time is a shell keyword"
<abathur>
because it can time command-lists and stuff
cole-h has joined #nixos-chat
<abathur>
i.e. time { echo heh; sleep 2; echo heh; }
<samueldr>
abathur: yeah, because! :)
<abathur>
it's a good reason, though! :)
<elvishjerricco>
Hm. Trying to build atuin on darwin, I get `ld: framework not found SystemConfiguration` and `ld: library not found for -liconv`
<elvishjerricco>
Do I need to add some build inputs?
tomberek has joined #nixos-chat
<abathur>
gchristensen: oh, duh, you can customize it with TIMEFORMAT; search that in the manual
<abathur>
not quite sure that does what you mean; there is a note that it prints a trailing newline, but it should at least be possible to collapse the timing info all onto a single line
<abathur>
and the default string prepends a linebreak, so I guess it can immediately follow the output with no break
<samueldr>
if you're timing not a pipeline, but a program, you can use GNU time
<abathur>
elvishjerricco: I think you can add SystemConfiguration and libiconv
<elvishjerricco>
nix search SystemConfiguration returned nothing
<abathur>
grepping in nixpkgs turns up results, at least
<colemickens>
the constant struggle between wanting the config rev in the system toplevel name, and not wanting to rebuild my toplevels every time I touch my mono-repo -_-
<colemickens>
(mono-repo in I'm-not-google air quotes)
<gchristensen>
samueldr: timing an `eval` :(
<samueldr>
gchristensen: you mean timing an `sh -c 'eval ...'` no?
<samueldr>
;)
<samueldr>
(no you don't)
<gchristensen>
hehe
<elvishjerricco>
I wonder why naersk doesn't break the deps up into different derivations.