sccs-tell(1)

📦 version 2022.10.16, in opensuse-leap 16.0

💅 sccs-tell(1) — Schily´s USER COMMANDS ✨

okay so bestie, welcome to the little manpage trio that tells you what's currently checked out. this is sccs-tell(1) from Schily´s USER COMMANDS, and yes we're gonna go through the whole thing together, no skipping 🫶

🌸 NAME 🌸

sccs-check, sccs-info, sccs-tell — print information about file being edited 💖

✨ SYNOPSIS ✨

sccs check [options] [directory]
sccs info [options] [directory]
sccs tell [options] [directory]

🎀 DESCRIPTION 🎀

so like, there are three little siblings here and they all care about one thing: files currently being edited. here's the tea on each 🔥

sccs check checks for files currently being edited. it's like info and tell, but instead of producing a listing of files, it returns an exit code. check returns a non-zero exit status if anything is being edited. the whole intent is to have this included in an ``install'' entry in a makefile to insure that everything is included into the SCCS file before a version is installed. like a vibe check before you ship it 👑

sccs info displays a list of files being edited, including the version number checked out, the version to be checked in, the name of the user who holds the lock, and the date and time the file was checked out. it's giving full receipts, periodt 💅

if the -b flag is given, branches (i.e., SID's with two or fewer components) are ignored. if the -u flag is given (with an optional argument) then only files being edited by you (or the named user) are listed.

sccs tell displays the list of files that are currently checked out, one file per line. simple, iconic, no notes 🌈

if no directory argument is given, the current working directory is used.

💜 OPTIONS 💜

🦋 /usr/bin/sccs

check [-b] [-u[username] ]

🦋 /usr/xpg4/bin/sccs

check [-b] [-u [username] | -U ]
  • -b — Ignore branches.
  • -u[username] | -u [username] | -U — Check only files being edited by you. When username is specified, check only files being edited by that user. For /usr/xpg4/bin/sccs, the -U option is equivalent to -u <current_user>.

⭐ EXAMPLES ⭐

to create a list of files currently being edited, call:

sccs tell

that's it. that's the whole example. slay 🎀

🌸 ENVIRONMENT VARIABLES 🌸

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

  • SCCS_NO_HELP — If set, sccs check, sccs info and sccs tell 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.
ngl if you're writing scripts that grep error output, this is your girl. set it or regret it 😭

👑 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-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-init(1), sccs-istext(1), sccs-ldiffs(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-unedit(1), sccs-unget(1), sccs-val(1), what(1), sccschangeset(5), sccsfile(5).

like, the whole squad. go read them all bestie, i believe in you 💖

💀 BUGS 💀

None currently known. (we love a clean bug list, ate and left no crumbs 🍓)

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 check, sccs info and sccs tell were originally written by Eric Allman at UCB in 1980. They have later been maintained by various people at AT&T and Sun Microsystems. Since 2006, they have been maintained by Joerg Schilling and the schilytools project authors. literal legends, one might say 🌟

🌈 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.

okay that's the whole page bestie, go forth and sccs tell responsibly 💅✨ this cutie was brought to you by Joerg Schilling, dated 2022/10/06 — mwah, take care, bye 🎀🦋

📦 where this page comes from