In reply to @raboof:matrix.org
maybe use 'attribute set' rather than just 'set' in that description? ('set' may invoke different expectations to people not familiar with nix)

In reply to @raboof:matrix.org
cool! the 'bind set arguments' (bottom-right) can't decide between 'set' or 'args' it seems?

The inspiration was the nixcademy cheat sheet.
https://nixcademy.com/cheatsheet.html

I changed the bind arguments variable to args because it's contextually different. Also a lot of examples I've seen usually call that variable args or inputs in the case of flakes.

Wow thanks for all the feedback everyone. For reference, we are trying to emulate something similar to the nixcademy cheat sheet (https://nixcademy.com/cheatsheet.html). This one being just for the nix language.

The design goals I am working with are

• printable (so we can hand them out at cons)
• start with just the nix language (no nix commands for now)
• ideally 1 page
• cover enough basics that users can get going (i.e. it's not comprehensive)

We could go to 2 pages but ideally it would be 1 for the nix language and 1 for nix commands.
Built-ins would be a great addition. Trying to figure out how to make it all fit.
Creating this in latex. The default font size, which you all see, is 10pt. I could try 9pt... would need to do some test prints to see if it would look okay.

Doesn't it still hold true in this case?

nix-repl> (x: rec {inherit x;}) 10
{ x = 10; }

nix-repl> :p (x: rec {inherit x;}) { y = { z = 20; }; }
{ x = { y = { z = 20; }; }; }

In reply to @raboof:matrix.org
good point, maybe point to 'further references' like https://nixos.org/manual/nix/stable/language/builtins.html and https://nixos.org/manual/nixpkgs/unstable/#id-1.4 ? Getting hard to fit in, though, I can imagine ;)

I'm being overly pedantic here on purpose so feel free to push back. With that in mind:

• For Path, change to Path with context? Or string with context? This would give ppl a keyword to search for
• in the let ... in example, isn't there too many times the word "return"?
• Merge attribute sets using //, I would use a nested attribute for x on the left side, this way in the second example where the right attrset overrides x, it is clear that the value of the right attrset replaces completely the value on the left. So { x.a = 1; } // { x = 2; } => { x = 2; }
• concatenate paths and strings IMO is confusing because it doesn't answer the questions what and why is there a difference between a path and a string
• Named arguments as attribute set; I would rename this to Attribute set as first argument. IMO it makes it a bit more obvious that it's a function with one argument that is an attribute set.

In reply to @garbas:matrix.org
I also won't be able to attend. I'm too exhausted.