sccs-status(1)

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

πŸ’… sccs-status(1) β€” show changed files in the project ✨

Okay so this page is sccs-status(1) from SchilyΒ΄s USER COMMANDS, and it's literally here to give your project a status check. Bestie, it's giving β€œlet me see what changed” energy, and all the facts below are staying exactly where they belong. 🫢


🌸 NAME 🌸

sccs-status - show changed files in the project πŸ’–


✨ SYNOPSIS ✨

sccs status [options] [file1 .. filen]

πŸ¦‹ DESCRIPTION πŸ¦‹

The status subcommand shows the status of the files in the repository. No cap.

If no file argument is given, the current list of files in the project is checked. Slay.

This subcommand is a project extension that does not exist in historic sccs implementations. Periodt β€” it's an extension, not a historic thing. πŸ’…


πŸŽ€ EXAMPLES πŸŽ€

To check for changed files in the current directory, call:

sccs status

🌈 ENVIRONMENT VARIABLES 🌈

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

πŸ’œ SCCS_NO_HELP

If set, sccs status 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. Very β€œdon't touch my exact output” of them, honestly. 😌


πŸ‘‘ ATTRIBUTES πŸ‘‘

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

  • Availability: SCHILYdeveloper-build-sccs
  • Interface Stability: Evolving

πŸ”₯ SEE ALSO πŸ”₯

All the besties in the sccs cinematic universe:


πŸ’€ BUGS πŸ’€

None currently known. Iconic, honestly.

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 status was originally written by Joerg Schilling in 2015 and is now maintained by the schilytools project authors.


πŸ“ 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

Later, bestie! πŸ’– Joerg Schilling Β· 2022/10/06 Β· sccs-status(1) πŸŒˆπŸŽ€

πŸ“¦ where this page comes from