sccs-editor(1)

💅 sccs-editor(1) — bestie edition ✨

ok so this is a page from Schily´s USER COMMANDS (manual name right there, in the flesh, slay) and it's literally all about sccs-editor(1). sit down, grab a drink, we're learning 🍓

---

✨ NAME ✨

sccs-editor — edit a file whether or not it is controlled by SCCS 🎀

🦋 SYNOPSIS 🦋

sccs editor [editor options] file1 .. filen

💖 DESCRIPTION 💖

okay so the whole vibe: this edits a file whether or not it is controlled by SCCS. (yes the original says "whether or not is is controlled", typo and all, we love a typo, moving on 💀)

Here's the tea, lowkey the whole point:

• if the file is controlled by SCCS and it's currently not checked out for editing → it gets checked out for editing first, and then edited. two-step. iconic.
• if the file is not under control of SCCS → the editor is just called directly. no drama, no checkout.

The SCCS_EDITOR or EDITOR environment variable must be set appropriately so a custom editor can be called. no cap, that's a requirement.

So there's a cute lil trick for hiding the fact that files need to be checked out for editing first — set SCCS_EDITOR and then alias the editor, like this:

SCCS_EDITOR=ved
alias ved='sccs editor'

And now the big brain part 🙈 — to minimize the side effects of calling the alias ved *, sccs editor will call unget(1) or sccs unedit on all files that have not been modified by the edit session and that have not been checked out for editing before. so it cleans up after itself, periodt.

⚠️ heads up: this subcommand is a SCHILY extension that does not exist in historic sccs implementations. she's new here. iykyk 💅

🌈 EXAMPLES 🌈

To edit the file xec.c in the current directory, call:

sccs editor xec.c

that's it. that's the example. ate. 💜

🌸 ENVIRONMENT VARIABLES 🌸

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

• SCCS_NO_HELP — if set, sccs editor 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. 🙏

👑 ATTRIBUTES 👑

See attributes(7) for descriptions of the following attributes — the table got turned into a lil list because we're cute like that:

• 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-diffs(1), sccs-edit(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-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).

like, that's a whole friend group fr fr 🫶

💀 AUTHOR 💀

sccs editor was originally written by Joerg Schilling in 2011 and is now maintained by the schilytools project authors. legends only 👑

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

(yes, both of those URLs end with a period in the original — that's just how she is, don't @ me 💅)

---

and that's the whole page bestie!! 🌟 brought to you by Joerg Schilling, dated 2022/10/06, and it's the sccs-editor(1) page — go forth and edit, mwah 😽💖