GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
sccs-editor(1) Schily´s USER COMMANDS sccs-editor(1)

sccs-editor - Edit a file whether or not it is controlled by SCCS

sccs editor [editor options] file1 .. filen

Edit 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.:

SCCS_EDITOR=ved alias ved='sccs editor'

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.

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

See environ(5) 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.

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

ATTRIBUTE TYPE ATTRIBUTE VALUE
Availability SCHILYdeveloper-build-sccs
Interface Stability Committed

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(4), sccsfile(4).

sccs editor was originally written by Joerg Schilling in 2011 and is still maintained by Joerg Schilling.

A frequently updated source code for the SCCS suite is included in the schilytools project and may be retrieved from the schilytools project at Sourceforge at:

http://sourceforge.net/projects/schilytools/

The download directory is:

http://sourceforge.net/projects/schilytools/files/

Check for the schily-*.tar.bz2 archives.

Less frequently updated source code for the SCCS suite is at:

http://sourceforge.net/projects/sccs/files/

Separate project informations for the SCCS project may be retrieved from:

http://sccs.sf.net

2020/06/29 Joerg Schilling

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.