sccs-print(1)
β¨ sccs-print β the sccs-print(1) glow-up β¨
okay so bestie, welcome to sccs-print(1) β Schily's USER COMMANDS era, and this one is literally the "tell me everything" command π«Ά
πΈ NAME πΈ
sccs-print β print out verbose information about the named files
like, all the tea. every last drop π
π¦ SYNOPSIS π¦
sccs print [options] [file1 .. filen]
π DESCRIPTION π
so here's the vibe: the print subcommand prints the entire history of each named file. the whole saga, start to finish, no skips π
it's equivalent to running an sccs prs -e followed by an sccs get -p -m β that's the combo meal, fr fr β¨
π OPTIONS π
-Aβ annotates each line of the output with the programmer and the date (peepsccs-get(1)for the deets) π§-aβ includes all deltas, even the ones marked as removed (checksccs-rmdel(1)β yes, we're bringing the deleted ones back out, dramatic π)-mβ annotates each line with the%M%ID and a TAB (again,sccs-get(1)is your bestie here)-rsidβ specify the SID (seesccs-get(1))
π EXAMPLES π
wanna print the file xec.c in the current directory? say less, just call:
sccs print xec.c
and boom, history unlocked ποΈβ¨
π ENVIRONMENT VARIABLES π
see environ(7) for the descriptions of these environment variables that affect how sccs-print(1) runs: LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.
SCCS_NO_HELPβ if this is set,sccs printwill not automatically callhelp(1)with the SCCS error code to print a more helpful error message. so if your script depends on the exact error messages of SCCS commands, you should set the environment variableSCCS_NO_HELPand setLC_ALL=C. no cap, that's the move π
π FILES π
(this section is literally empty in the original β nothing listed, no files named, iconic minimalism π )
β ATTRIBUTES β
see attributes(7) for descriptions of the following attributes:
- Attribute Type: Availability Attribute Value:
SCHILYdeveloper-build-sccs - Attribute Type: Interface Stability Attribute Value:
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-diffs(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-ldiffs(1), sccs-log(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).
like, the whole friend group π«
π BUGS π
none currently known π (we love a clean record)
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.
πΈ AUTHORS πΈ
sccs print 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. a whole lineage, honestly π§¬β¨
π§ SOURCE DOWNLOAD π§
the source code for sccs print 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.
k that's the whole page bestie, go print some history π
β with love from Joerg Schilling, dated 2022/10/06, on the sccs-print(1) page ππ¦β
π¦ where this page comes from
- opensuse-leap 16.0: sccs 2022.10.16-160000.2.2 Β· CDDL-1.0
- opensuse-leap 16.0: sccs 2022.10.16-160000.2.2 Β· CDDL-1.0
- opensuse-leap 16.0: sccs 2022.10.16-160000.2.2 Β· CDDL-1.0
- opensuse-leap 16.0: sccs 2022.10.16-160000.2.2 Β· CDDL-1.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms