sccs-histfile(1)

💖 sccs-histfile(1) 💖

okay bestie, welcome to the sccs-histfile(1) page from Schily´s USER COMMANDS — yes, that manual name is right there, and yes we are about to make SCCS history-file pathing make sense. 💅✨

🌸 NAME 🌸

sccs-histfile — converts a g-filename into the s-filename counterpart. literally that’s the whole job, and it ate. 🫶

🦋 SYNOPSIS 🦋

sccs histfile pathname

🎀 DESCRIPTION 🎀

The sccs histfile subcommand converts a g-filename into the appropriate s-filename counterpart that is used for SCCS history files. no cap, that’s the main-character move. 👑

Back in the day, sccs(1) just slapped SCCS/s. before the last path name component — iconic but old-school. Now there is support for off-tree history files that are located inside a directory .sccs in the project root directory. The histfile subcommand knows which operating mode is currently in use and returns the appropriate path to the history file. it’s giving “I know where your history lives.” 🕵️‍♀️

If the pathname argument refers to a directory, the result is the directory that holds the SCCS history files for the files in that directory. yep, directory in, directory out. 🗂️

This subcommand is an extension that does not exist in historic sccs implementations. so if some ancient SCCS is acting confused, that’s why. 💀

🔥 OPTIONS 🔥

None — literally no options, bestie. No flags, no switches, no secret menu. the original page says None and we respect the icon behavior. 💅

🌈 EXAMPLES 🌈

To retrieve the SCCS history filename for the file xec.c in the current directory, call:

sccs histfile xec.c

💜 ENVIRONMENT VARIABLES 💜

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

• SCCS_NO_HELP — if set, sccs histfile 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 attribute type and attribute value pairs are:

• Availability — SCHILYdeveloper-build-sccs
• Interface Stability — Committed

🌟 SEE ALSO 🌟

Go get your read on, bestie: 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-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).

💀 BUGS 💀

None currently known. slay. 💅

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

⭐ 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

---

xoxo, Joerg Schilling, 2022/10/06, sccs-histfile(1) — from Schily´s USER COMMANDS. that’s the footer vibe, bestie. 💖✨