Path: utzoo!attcan!uunet!pilchuck!ssc!fyl
From: fyl@ssc.UUCP (Phil Hughes)
Newsgroups: comp.unix.questions
Subject: Re: Why shouldn't ^J (linefeed) be used as a command in an application?
Keywords: line discipline, control characters, UNIX conventions
Message-ID: <1591@ssc.UUCP>
Date: 16 Dec 88 17:51:07 GMT
References: <4404@sfsup.UUCP> <713@auspex.UUCP>
Organization: SSC, Inc., Seattle, WA
Lines: 18

In article <713@auspex.UUCP>, guy@auspex.UUCP (Guy Harris) writes:
| >What are the historical or cultural reasons that ^J is not used in UNIX
| >tools?

> There *are* UNIX cbreak-mode or raw-mode applications that use ^J and ^M
> for different purposes; some versions of EMACS do (but then again they
> permit you to do fairly arbitrary key bindings).  The main problem is if
> you have a terminal that can't send them both, but that's a different
> matter.

Zebu, our records management product uses ^M to get to the next field
and ^J to get to a secondary record.  We have been using it this way
at SSC since 1983 and have been selling it for almost as long with no
problems/complaints.  Did I miss something as to why this could be a
problem?
-- 
Phil Hughes, SSC, Inc. P.O. Box 55549, Seattle, WA 98155  (206)FOR-UNIX
    uw-beaver!tikal!ssc!fyl or uunet!pilchuck!ssc!fyl or attmail!ssc!fyl