NYCHECK(1)

πŸ“¦ version 2025.09.18.4, in nixos 26.05, nixpkgs unstable

πŸ’– nycheck(1) β€” the vibe check for your patches πŸ’–

okay bestie so you're looking at nycheck in the manual, section 1 (that's general commands, the classics section, we love her) πŸ’…


✨ NAME ✨

nycheck β€” the tool that checks the syntax of specialized-format patches, no cap πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

nycheck pam options [ print ] [ .go ]

🌸 DESCRIPTION 🌸

So nycheck is part of the Nypatchy squad of programs β€” the whole crew that works with Patchy Master Files (aka PAM files, iykyk) β€” peep nypatchy(1) for the rest of the family tree 🌈

But here's her main character energy: she is a syntax checker for these files, and she is more strict than nypatchy itself. literally her whole thing. she's the friend who reads the group chat receipts and goes "um actually that's not valid." πŸ•΅οΈβ€β™€οΈ


πŸ’œ USAGE πŸ’œ

k so let's break down the pieces, bestie:

  • pam β€” the name of the PAM file. if you don't say otherwise, she assumes a default extension of .car πŸš—βœ¨
  • print β€” the output file she writes to. if you just... don't include it? defaults to standard output. no stress 🫢
  • options β€” a sequence of single-character flags (the fun little toggles, we'll get to those)

and listen: the command should be ended with .go unless you actually want to drop into the Nypatchy interactive shell. .go = "ok go off, do the thing" 🏁

so like, nycheck something.car H .go is the whole mood. don't forget the .go unless you're trying to hang out in the shell fr fr

✨ OPTIONS ✨

first, the house rules, and yes they matter πŸ™ˆ

  • options go in as a single string of characters β€” no space separation between them!
  • no - character either, with one lil exception: you can use - in place of the options field if you genuinely don't want any options. that's it. that's the exception πŸ’€
  • alphabetic options are not case-sensitive. h and H? same girl, different font πŸ’…

now the actual flags:

  • H β€” print help information only. just the help, nothing else. a little "here's how I work" moment πŸŽ€
  • U β€” print a warning if user-defined types occur. she's looking out for you πŸ‘€
  • n β€” page length time, and she's got two modes for this, so pay attention 😭
    • for n a number from 0 to 4 inclusive: assume 58, 62, 74, 84, or 98 lines per page in the output. (that's the mapping, in that order β€” 0 β†’ 58, 1 β†’ 62, 2 β†’ 74, 3 β†’ 84, 4 β†’ 98) πŸ“
    • for n a number greater than or equal to 20: use that specific number of lines per page. you do you, icon πŸ‘‘
    • default is 110 lines per page if you don't pick anything πŸ¦‹
  • + β€” inhibit the initial page-eject. no first blank page, we go straight in πŸšͺπŸ”₯

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, love them for her:

fcasplit(1), nydiff(1), nyindex(1), nylist(1), nymerge(1), nypatchy(1), nyshell(1), nysynopt(1), nytidy(1), yexpand(1)

also!! the reference manual for the whole Nypatchy suite of programs is available in compressed PostScript format at this URL:

http://wwwasdoc.web.cern.ch/wwwasdoc/psdir/p5refman.ps.gz

and fun fact: running the command nycheck help .no also gives some brief help on usage. yes .no not .go β€” she's got range πŸ’€βœ¨


🫢 AUTHOR 🫢

this manual page was written by Kevin McCarty <kmccarty@debian.org> for the Debian GNU/Linux system (but may be used by others β€” she's generous like that). it is licensed under the GNU General Public License, version 2 or later (at your choice) πŸ“œ


Copyright (C) Kevin B. McCarty, 2008.


and that's the whole page, bestie!! πŸ’– dated Mar 12, 2008, stamped NYCHECK(1) at the bottom like a lil signature β€” go check those patches, you're gonna slay πŸ¦‹πŸŒΈπŸ’…

πŸ“¦ where this page comes from