sccs-diffs(1)

πŸ“¦ version 2022.10.16, in opensuse-leap 16.0

πŸ’… sccs-diffs β€” like, the manual page, but make it make sense

Okay bestie, buckle up ✨ this is the sccs diffs page from Schily´s USER COMMANDS (that's the manual name, we're folding it in here so it doesn't get lonely), and it's genuinely one of the more useful little gremlins in the SCCS toolbox. Let's get into it 🫢


πŸ¦‹ NAME

sccs-diffs β€” compare the working copy of a file with the SCCS history

Like, you've been editing a file and now you wanna see what you actually changed versus what's safely checked in. That's the whole vibe. Iconic honestly.


🌸 SYNOPSIS

sccs diffs [options] [file1 .. filen]
sccs ldiffs [options] [file1 .. filen]

✨ DESCRIPTION

So here's the tea β˜• β€” the diffs subcommand compares, in diff(1) format, the working copy of a file that is checked out for editing against a version from the SCCS history. By default, sccs diffs uses the most recent checked-in version. Lowkey the most common thing you'll ever do with it.

And the fun part: the diffs subcommand accepts the same options as diff. Yeah. All of them. Go off πŸ‘‘

A few options get special treatment though, so pay attention bestie:

  • Any -r, -c, -i, -x, and -t options are passed to the subcommand get.
  • A -C option is passed to diff as -c.
  • An -I option is passed to diff as -i.

Also super important: the diffs subcommand calls the UNIX diff(1) command that is delivered with the SCCS packet. If you'd rather call your local diff(1) β€” the one sitting in your PATH β€” use the ldiffs subcommand instead. That's literally the whole difference between them, iykyk πŸ’…


πŸŽ€ OPTIONS

All diff(1) options are supported, plus these SCCS-specific ones:

  • -c date-time | -cdate-time β€” use the most recent version checked in before the indicated date and time for the comparison. The date-time takes the form yy[mm[dd[hh[mm[ss]]]]]. Any omitted units default to their maximum possible values β€” so like, -c7502 is equivalent to -c750228235959. Sneaky but iconic πŸ•°οΈ
  • -r[sid] β€” use the version corresponding to the indicated SID (delta). Peep sccs-get(1) for more info on what a SID even is 🧚

🌈 EXAMPLES

Wanna compare the file xec.c in the current directory with the state in the SCCS history? Just call:

sccs diffs xec.c

That's it. Slay. πŸ’–


πŸ“ ENVIRONMENT VARIABLES

See environ(7) for the descriptions of the following environment variables that affect the execution of sccs-diffs(1): LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.

  • SCCS_NO_HELP β€” if set, sccs diffs will not automatically call help(1) with the SCCS error code in order to print a more helpful error message. Scripts that depend on the exact error messages of SCCS commands should set the environment variable SCCS_NO_HELP and set LC_ALL=C.
Fr fr, if you're writing a script that greps error output, set SCCS_NO_HELP and LC_ALL=C. Otherwise help(1) might swoop in with extra text and wreck your parsing. No cap 😭

πŸ‘‘ ATTRIBUTES

See attributes(7) for descriptions of the following attributes:

  • Availability β€” SCHILYdeveloper-build-sccs
  • Interface Stability β€” Committed

πŸ’œ SEE ALSO

sccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(1), sccs-clean(1), sccs-comb(1), sccs-commit(1), sccs-create(1), sccs-cvt(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-edit(1), sccs-editor(1), sccs-enter(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(1), sccs-init(1), sccs-istext(1), sccs-log(1), sccs-print(1), sccs-prs(1), sccs-prt(1), sccs-rcs2sccs(1), sccs-remove(1), sccs-rename(1), sccs-rmdel(1), sccs-root(1), sccs-sact(1), sccs-sccsdiff(1), sccs-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), what(1), sccschangeset(5), sccsfile(5).

That's a lot of links, bestie β€” the whole SCCS family reunion 🌸


πŸ’€ BUGS

None currently known. Literally flawless, we love to see it ✨

Found something anyway? Mail bugs and suggestions to schilytools@mlists.in-berlin.de or open a ticket at https://codeberg.org/schilytools/schilytools/issues.

The mailing list archive may be found at:

https://mlists.in-berlin.de/mailman/listinfo/schilytools-mlists.in-berlin.de

🧚 AUTHOR

sccs diffs was originally written by Eric Allman at UCB in 1980. It was later maintained by various people at AT&T and Sun Microsystems. Since 2006, it has been maintained by Joerg Schilling and the schilytools project authors.

Honestly? A whole lineage. Main character energy across four decades πŸ‘‘


⭐ SOURCE DOWNLOAD

The source code for SCCS is included in the schilytools project and may be retrieved from the schilytools project at Codeberg at:

https://codeberg.org/schilytools/schilytools

The download directory is:

https://codeberg.org/schilytools/schilytools/releases

And that's the page, bestie πŸŽ€ go diff something and feel something. πŸ¦‹

Written by Joerg Schilling, dated 2022/10/06 β€” and this version of the sccs-diffs(1) page is, like, officially signed off. Bye bestie, ily πŸ’–

πŸ“¦ where this page comes from