GTS_COPY(1)

🌸 NAME 🌸

gts_copy β€” bestie, it's literally just the manual page for gts_copy. That's it. That's the name. It lives in section 1 of the manual, so say hi to GTS_COPY(1) πŸ’–


πŸŽ€ DESCRIPTION πŸŽ€

Okay so before we even get into the real talk, the page opens by introducing itself again, like a main character doing a dramatic re-entrance. Here's round one, verbatim energy and all πŸ‘‘

πŸ’– NAME πŸ’–

gts_copy

✨ DESCRIPTION ✨

Copies the content of GTS files printing values of some keys. That's the whole gig, no cap.

πŸ¦‹ USAGE πŸ¦‹

gts_copy [options] file file ... output_file

So you feed it a bunch of files, and last comes the output_file. Order matters, bestie, the output goes last 🫢

πŸ‘‘ OPTIONS πŸ‘‘

  • -f β€” Force. Makes the execution not fail on error, so it just pushes through no matter what.
  • -p key[:{s|d|i}],key[:{s|d|i}],... β€” Declares the keys you wanna print. For each key you can ask for a string (key:s), a double (key:d) or an integer (key:i). If you don't say, the default type is string ✨
  • -P key[:{s|d|i}],key[:{s|d|i}],... β€” Same as -p, except it adds the declared keys to the default list instead of replacing anything πŸ’…
  • -w key[:{s|d|i}]=value,key[:{s|d|i}]=value,... β€” The where clause, aka the vibe check. Only the GTS messages that match your key/value constraints get copied to the output_gts_file. For each key you can define a string (key:s), a double (key:d) or an integer (key:i). Default type is string.
  • -V β€” Print version. Show me the numbers πŸ”₯
  • -W width β€” Minimum width of each column in the output. Default is 10.
  • -g β€” Copy the GTS header. Give the header its flowers πŸ‘‘
  • -7 β€” Does not fail when the message has the wrong length. Forgiving queen energy πŸ™ˆ
  • -v β€” Verbose. Say more, bestie, I'm listening πŸ‘‚

πŸŒ€ and then… the page does it ALL over again πŸŒ€

No seriously. The manpage just repeats the entire block, top to bottom. Not me being extra β€” this is genuinely what it says. So here it is, second pass, same details, because no detail gets left behind πŸ’€βœ¨

πŸ’– NAME πŸ’–

gts_copy

✨ DESCRIPTION ✨

Copies the content of GTS files printing values of some keys.

πŸ¦‹ USAGE πŸ¦‹

gts_copy [options] file file ... output_file

πŸ‘‘ OPTIONS πŸ‘‘

  • -f β€” Force. Force the execution not to fail on error.
  • -p key[:{s|d|i}],key[:{s|d|i}],... β€” Declaration of keys to print. For each key a string (key:s), a double (key:d) or an integer (key:i) type can be requested. Default type is string.
  • -P key[:{s|d|i}],key[:{s|d|i}],... β€” Same as -p but adds the declared keys to the default list.
  • -w key[:{s|d|i}]=value,key[:{s|d|i}]=value,... β€” Where clause. Only GTS messages matching the key/value constraints are copied to the output_gts_file. For each key a string (key:s), a double (key:d) or an integer (key:i) type can be defined. Default type is string.
  • -V β€” Print version.
  • -W width β€” Minimum width of each column in output. Default is 10.
  • -g β€” Copy GTS header.
  • -7 β€” Does not fail when the message has wrong length.
  • -v β€” Verbose.

πŸ’‘ pro tip from your girl: the repetition is the page's thing, so don't panic and think you're reading double. You're not. It's just like that. πŸ“

okay that's the whole thing, we ate, no crumbs left πŸ’… this page is gts_copy, dated October 2026, and it comes to you from manual page GTS_COPY(1). mwah, go copy some GTS files πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from