Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!caip!clyde!cbatt!cbosgd!ihnp4!cuae2!ltuxa!ttrdc!levy From: levy@ttrdc.UUCP (Daniel R. Levy) Newsgroups: net.bugs.usg,net.bugs.4bsd Subject: vi bug? Message-ID: <1178@ttrdc.UUCP> Date: Thu, 4-Sep-86 19:21:47 EDT Article-I.D.: ttrdc.1178 Posted: Thu Sep 4 19:21:47 1986 Date-Received: Fri, 5-Sep-86 23:56:47 EDT Organization: AT&T, Computer Systems Division, Skokie, IL Lines: 34 Xref: mnetor net.bugs.usg:359 net.bugs.4bsd:913 I have found what I _think_ is a bug in several different versions of vi (on a VAX running BSD4.1, on a 3B2/400 running SysVR2, on a 3B20S running SysVR2, but not on a PDP 11/70 running the UNIX 4.0 system). The trouble seems to be that vi will intercept certain ASCII sequences in the input file on lines beginning with 'ex:' and will interpret them as if they were commands. For example, a file containing the two lines ex:: ex:3: will, when read into some versions of vi, produce the diagnostic "Not that many lines in buffer." This problem arose when using vi to edit ASCII database files structured into newline-separated records with the fields separated by colons (a la /etc/passwd) and where 'ex' was one possible entry in the first field of a record. Would someone who is in the know please tell me whether this behavior is a bug or a "feature"? I certainly cannot find any mention of it in what little documentation I have about vi (the SysV and BSD man pages on ex and vi, and a document called "An Introduction to Display Editing using Vi"). Thank you in advance. -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer or the administrator of any computer | at&t computer systems division | upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa, go for it! allegra,ulysses,vax135}!ttrdc!levy