ninjin has quit [Remote host closed the connection]
drakonis has joined #nixos-chat
drakonis has quit [Read error: Connection reset by peer]
hedning has joined #nixos-chat
lassulus_ has joined #nixos-chat
lassulus has quit [Ping timeout: 250 seconds]
lassulus_ is now known as lassulus
hedning has quit [Remote host closed the connection]
hedning has joined #nixos-chat
sir_guy_carleton has quit [Quit: WeeChat 2.2]
rawreraw has joined #nixos-chat
endformationage has quit [Quit: WeeChat 2.3]
jD91mZM2 has joined #nixos-chat
<jD91mZM2>
So I've been having one or two applications disobey my gtk theme, and I've been too lazy to debug it. Turns out, I set QT_QPA_PLATFORMTHEME from home-manager which means it didn't affect programs launched from desktop entries.
<elvishjerricco>
Apparently VirtualBox needs `${virtualbox}/libexec/virtualbox` to be on the PATH in order to test for 3D acceleration support. But once I add that, it starts failing, complaining that the effective uid need to be root. Apparently on most systems, the installer uses the setuid bit to run some things as root -_-
endformationage has joined #nixos-chat
pie___ has joined #nixos-chat
pie__ has quit [Remote host closed the connection]
rawreraw has quit [Ping timeout: 252 seconds]
rawreraw has joined #nixos-chat
jD91mZM2 has quit [Quit: WeeChat 2.2]
rawreraw has quit [Ping timeout: 252 seconds]
rawreraw has joined #nixos-chat
sir_guy_carleton has joined #nixos-chat
sir_guy_carleton has quit [Quit: WeeChat 2.2]
sir_guy_carleton has joined #nixos-chat
rawreraw has quit [Ping timeout: 252 seconds]
pie__ has joined #nixos-chat
pie___ has quit [Remote host closed the connection]
<andi->
The things we do not run into with NixOS <3
jackdk has quit [Remote host closed the connection]
Synthetica has joined #nixos-chat
<joepie91>
,tofu
<{^_^}>
To get a sha256 hash of a new source, you can use the Trust On First Use model: use probably-wrong hash (for example: 0000000000000000000000000000000000000000000000000000) then replace it with the correct hash Nix expected.
jackdk has joined #nixos-chat
hedning has quit [Quit: hedning]
<joepie91>
in (third-party) documentation, would anybody have strong objections against referring to Nix the language as 'Nixlang'?
<__monty__>
I'd stylize it differently if you really have to.
<LnL>
nix expression language is the proper name, AFAIK
<joepie91>
'nix expression language' is about three times too long for reference in documentation :)
<joepie91>
ivan: I'm trying to resolve the ambiguity between the package manager and the language here, so 'Nix language' is not particularly effective at that
<__monty__>
LnL: Isn't "nix" the proper name?
<joepie91>
I'm basically looking for a name to give it that doesn't effectively require a paragraph of clarification every time it's used
<LnL>
don't see the problem, but you can use an acronym if you really want
<__monty__>
Yeah, NEL would be fine.
<__monty__>
I'd personally go for nix-lang.
<LnL>
just "nix" usually refers to the package manager or project in general
<joepie91>
I'm not sure anybody actually uses "NEL" and searching for 'nix nel' gives me some random fashion site, whereas 'nix-lang' does produce some relevant results
<joepie91>
('nel' is obviously too generic)
<joepie91>
(to search for)
<joepie91>
so yeah, 'nix-lang' is probably most practical here
<__monty__>
NEL wouldn't be the only thing you include though. You'd say "The Nix expression language (NEL)..." then every reference thereafter you just say "NEL."
<joepie91>
yeah, but that means that the 'page thereafter' -> google path isn't great