GTS_COMPARE(1)

πŸ’– GTS_COMPARE(1) πŸ’–

okay bestie, buckle up 🫢 this is the manual page for gts_compare, and it lives in the User Commands corner of your manual. It's short, it's spicy, and it will absolutely tell you if two files are lying about being the same. Let's get into it. 🌸


✨ NAME ✨

gts_compare β€” manual page for gts_compare

πŸŽ€ DESCRIPTION πŸŽ€

Compare GTS messages contained in two files. If some differences are found it fails returning an error code. The default behaviour is bit-by-bit compare, same order in files. That's the whole vibe. No cap. πŸ’…

ngl the original page says all of this stuff twice, like it's manifesting. Every single detail is here β€” once β€” so you don't have to read it two times. You're welcome. 🧚

πŸ¦‹ USAGE πŸ¦‹

gts_compare [options] file file

Two files. That's it. Two. Not one, not three. πŸ“

πŸ‘‘ OPTIONS πŸ‘‘

  • -b key,key,... β€” every key in this list gets skipped during the comparison. Bit-by-bit compare stays on. ✨
  • -c key[:i|d|s|n],key[:i|d|s|n],... β€” only the listed keys or namespaces (:n) are compared. That little optional letter after the colon is there to force the type in the comparison: iβ†’integer, dβ†’float, sβ†’string, nβ†’namespace. Peep the -a option too. This one is incompatible with the -H option β€” do not try it, it's giving chaos. πŸ’€
  • -a β€” the -c option's little modifer bestie 🫢. The keys you listed with -c get added to the list of keys compared without -c.
  • -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,... β€” the Where clause. Messages are processed only if they match all the key/value constraints. A valid constraint looks like key=value or key!=value. For each key you can specify a string type (key:s), a double (key:d) or an integer (key:i). Default type is string. In the value you can also use the forward-slash character / to specify an OR condition (i.e. a logical disjunction). 🌈
⚠️ Note: only one -w clause is allowed. One. Singular. Don't push it. πŸ™ˆ
  • -f β€” forcefully compare, do not stop after the first difference. Main character energy, it sees everything. πŸ‘‘
  • -V β€” print version. πŸ“’
  • -7 β€” does not fail when the message has wrong length. Chill about it. 😌
  • -v β€” verbose. It'll yap. πŸ’¬

and that's the entire page, fr fr. lowkey iconic that a tool this small can ruin your whole afternoon with one mismatched bit. πŸ’œ

k byeeee β€” this was gts_compare, dated October 2026, manual page GTS_COMPARE(1). slay, stay compared. πŸ’–βœ¨

πŸ“¦ where this page comes from