![]() |
![]()
| ![]() |
![]()
NAMEsccs-editor - Edit a file whether or not it is controlled by SCCS SYNOPSISsccs editor [editor options] file1 .. filen DESCRIPTIONEdit a file whether or not is is controlled by SCCS. If a file is controlled by SCCS and currently not checked out for editing, the file is checked out for editing first and then edited. If the file is not under control of SCCS, the editor is called directly. The SCCS_EDITOR or EDITOR environment variable must be set appropriately in order to call a custom editor. A way to hide the fact that files need to checked out for editing first, is to set SCCS_EDITOR and then alias the editor, e.g.:
Note that in order 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. This subcommand is a SCHILY extension that does not exist in historic sccs implementations. EXAMPLESTo edit the file xec.c in the current directory call:
ENVIRONMENT VARIABLESSee 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.
ATTRIBUTESSee attributes(7) for descriptions of the following attributes:
SEE ALSOsccs(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). AUTHORsccs editor was originally written by Joerg Schilling in 2011 and is now maintained by the schilytools project authors. SOURCE DOWNLOADThe 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.
|