HDTenEightyP/NetNews huggingface dataset:
From: hamjavar@carina.unm.edu (Farid Hamjavar)
Newsgroups: comp.editors
Subject: VI Book
Date: 26 Sep 92 23:55:17 GMT
Article-I.D.: lynx.+5!p64m
Organization: University of New Mexico, Albuquerque



@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
Article: 6613 of comp.editors
From: srikant@skorpio.usask.ca (Srikant Subramaniam)

Hello net.world:

Is there a  definitive reference book on vi ? I would like to be able to use the
full capabilities of vi (macros, et al ...). Could somebody give me some info?
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 



Learning the vi Editor   by    O'Rilly & Associates, Inc.
ISBN  0-937175-17-X

PS: This book also, not in details, covers 'ex' as well.



Farid Hamjavar
Newsgroups: comp.editors
From: lwv26@cas.org (Larry W. Virden)
Subject: Re: Vi Formating without using fmt
Followup-To: comp.editors
Reply-To: lvirden@cas.org (Larry W. Virden)
Organization: Nedriv Software and Shoe Shiners, Uninc.
Date: Tue, 6 Oct 1992 11:41:58 GMT

In article <1992Oct4.183159.851@mlb.semi.harris.com> rliles@spuds.mlb.semi.harris.com (Ray Liles) writes:

:1. How do you insert text into an existing paragraph AND reformat/fill that
:   paragraph so that all text observes the wrapmargin, without part of a word
:   on one line and the rest of the word on the next?
:
:2. How do you justify text for both the left AND right margins without running
:   through fmt?
:
:Ray

Isn't the answer to the first question that you use fmt?  As for the second
question - why do you ask that you don't run through fmt - are you concerned
about your current version of fmt having a problem, does fmt do something
in a manner you do not like, etc.?  In other words, what are you really
after?
-- 
Larry W. Virden                 UUCP: osu-cis!chemabs!lvirden
Same Mbox: BITNET: lvirden@cas  INET: lvirden@cas.org
Personal: 674 Falls Place,   Reynoldsburg, OH 43068-1614
America Online: lvirden@aol.com
From: wek@point.uucp (Bill Kuykendall)
Newsgroups: comp.editors
Subject: PEN Editor
Date: 30 Sep 92 23:01:21 GMT
Organization: The Point BBS


I recently posted an announcement for a new editor named THE to this
newsgroup.  In 1.5 years of reading this newsgroup, I had never seen any
reference to an editor of this name, but within 24 hours of making our
announcement, I had mail from Brisbane, AUS, informing me that "The Hessling
Editor" had recently been released with the moniker, "THE".  

OK, I can live with that, and I certainly wouldn't want our editor to be
confused with one that had originally been announced in comp.os.os2 8-).
Besides, Mark Hessling seems like a nice guy and definitely has a better
reason for wanting THE name.

The problem that we face now, is selecting a new name and trying to make
reasonably sure that we have clear title to it before we get too deeply
invested in it.

I have two requests.  The first is for a general procedure to follow in the
future for such cases.  The second is for any information about the names
PEN and WE.  Does anyone know of an editor or wordprocessor, commercial or
otherwise, which uses either of these names? If so (to eliminate cases of 
"intent to release under that name") could you supply information about 
where such a product can be obtained, i.e., archive site, or software 
publisher info.

Thanks much for any information or insight you may have.  And hopefully,
we'll have Point to Point's $EDITOR out the door without too much delay.

-----------------------------------
Bill Kuykendall
Point to Point Communications, Inc.
wek@point.uucp
From: barr@pop.psu.edu (David Barr)
Newsgroups: comp.editors
Subject: Re: <CR> in VI macros
Keywords: vi, macros, carriage returns
Date: 7 Oct 92 00:03:25 GMT
Organization: Penn State Population Research Institute

In article <1992Oct6.213438.11555@bnr.ca> mschee@bcarh600.bnr.ca (Michael SamChee) writes:
>Example
>-------
>- first, edit a file: "vi file1"
>- then from within file1, edit another file: ":!vi file2"  
>
>Problem
>-------
>Write a macro that would "pop" the user from file2 back to file1
>in *one* keystroke.

It's already there.  ^^.

(ctrl-^, depending on the teriminal this is ctrl-6, or ctrl+shift-6)

--Dave
-- 
System Administrator, Population Research Institute    barr@pop.psu.edu
  loose: v. to set free, or adj. not securely fastened.
  lose: v. to miss from one's possession.
Newsgroups: comp.editors,comp.graphics,comp.lang.smalltalk,alt.hypertext
From: bprescot@nyx.cs.du.edu (Barry Prescott)
Subject: BitBlt usage in document editors
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Sat, 3 Oct 92 20:10:40 GMT


I am implementing a hypertext document editor in Smalltalk. I've just come to
the point of optimizing the screen display system. I would be very grateful
if anyone could provide me with references on:

  The efficient use of BitBlt (RasterOp) in an interactive document editor.

I have a paper by Michael Hammer et al. on the Etude document production
system, but am in need of more, especially when I come to write my thesis!

Thanks in advance,

Barry Prescott
--
Barry Prescott, Hypermedia Systems Group, Dept. of Computer Science,
INTERNET: bp@cs.hull.ac.uk, ehgabp2@uts.mcc.ac.uk,    | The University, 
    bprescot@nyx.cs.du.edu    Phone: +44 482 465016   | Hull, HU6 7RX,
UUCP:	  ..!uknet!hu-cs!bp   Fax: +44 482 466666     | United Kingdom
Newsgroups: comp.editors
From: Richard.Kooijman@dnpap.et.tudelft.nl (Richard Kooijman)
Subject: Re: Elvis 1.6
Organization: Delft University of Technology, Dept. of Electrical Engineering
Date: Sat, 3 Oct 1992 18:58:11 GMT

ericm@hummer.ims.com (Eric Martinson) writes:


>:map ^[[11~   :r   /engr/ericm/templates/method.C^M

>When I press the key associated with ^[[11~ I get dumped out of elvis.
>I have never used mapping before but from the manuals and docs I read,
>the above seems like it should work.  It works for Sun's vi.

I experienced the same bug. It just doesn't work in Elvis.
I have reported the bug to Steve Kirkendall who would look into it.
I have checked the sources and something is going very wrong, I haven't
looked into those sources enough to fix it , though.



Richard.

--
-- ir. Richard Kooijman ------------------ Email: R.Kooijman@ET.TUDelft.NL --
-- Intelligent Network Management Project (INEMA) ---------------------------
-- CARDIT, Delft University of Technology ------------ Tel: (31)-15-786209 --
-- P.O.Box 5031, 2600 GA Delft, The Netherlands ------ Fax: (31)-15-784898 --
Newsgroups: comp.editors
From: rohit@NeoSoft.com (Rohit Mehrotra)
Subject: Re: ViX -- vi for x???
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Sun, 04 Oct 1992 20:51:54 GMT
Keywords: Vi, X, editor

In article <tlukka.718221154@vipunen.hut.fi> tlukka@vipunen.hut.fi (Tuomas Lukka) writes:
>I've been thinking of making a vi-compatible X editor for some time now and
>would like to have other peoples' opinion about taking up such a project:
>  First of all: has anything like this been done?
>    i.e. am I reinventing the wheel here?
>
>  2. The actual implementation -- my current plans are as follows:
>	-the editor part is one widget class. Inside the editor class,
>	 there are two different types of buffers: the editor buffer and
> 	 the small buffers, i.e. cut,paste, what you type etc.
>
>  3. The shell around the widget: I'm thinking of things like several 
>	 windows to the same file, buttons/symbolic representation of
>	 the named buffers, menus (if you want them, definable by resources)
>	etc.
>
>  4. Thoughts -- what should it be like --
>	I'd like to spare the general features of vi, small size, speed,
>  	fast commands etc, but add more.. 
>	And most importantly, make vi X-aware, to make it more usable.
>	backwards-compatible of course, if you want, you can just use it
>	like the old vi, but then again, multiple windows and things like
>	that seem pretty nice to me.
>
>Please reply by email, and tell me if I'm wasting my time or making a
>well-niched effort here.
>
>Of course, the editor will be publicly available, NOT however in public
>domain.. something like the copyleft, maybe, will have to see about that
>in due time.

CRISP3.0+ the X version has a VI emulation. It lets one emulate VI in an X
environment and has all the features that you mentioned above, i.e. multiple
windows, vi regular expressions, vi macros, buttons, scrollbars, highlighting,
etc etc. It even passes the turing machine VI-Macro test.



-- 
Rohit Mehrotra
------------------------------------------------------------------------------
VITAL				| 	10755 Meadowglen Lane, #238
Ph: 713-781-7406		| 	Houston, TX 77042.
Newsgroups: comp.editors
From: eric@ils.nwu.edu (Eric Goldstein)
Subject: Paragraphs and vi
Organization: The Institute for the Learning Sciences
Date: Sun, 4 Oct 1992 02:16:32 GMT

Hi! 

I'm looking for a way to automatically format paragraphs using vi.

I've been using vi for years, (and I love it, and I've resisted
switching to Emacs), and all this time I've just used "J" and the
return keys.  But I really wish there was less annoying way to do it.

(At least on my system, setting the wrapmargin to greater than zero
doesn't influence the behavior of the "J" command.)


If it isn't clear what I mean by "formatting paragraphs", here is
an example:

------------------------------------------------------------------
This is a sample sentence.
This is sample sentence number two, which is longer than the others.
This is sample sentence number three.
This is sample sentence number four.

       |
       |     I want a way to automatically convert the above four lines 
       |     of text into a nicely formated paragraph.
       V 

This is a sample sentence. This is sample sentence number two, which
is longer than the others. This is sample sentence number three.  This 
is sample sentence number four.

---------------------------------------------------------------------

I would greatly appreciate any help on this!

                 -- Eric  (eric@ils.nwu.edu)

-- 

Newsgroups: comp.editors
From: rac@sherpa.uucp (Roger Cornelius)
Subject: Re: UNIX COMMAND IN VI SESSION.
Organization: Personal System Computing :-) Gulfport, FL
Date: Fri, 02 Oct 1992 14:13:43 GMT

In article <=1=p9lb@lynx.unm.edu>, hamjavar@carina.unm.edu (Farid Hamjavar) writes:
> 
> Hello : 				OCT-01-92
> 
> VI allows you to execute UNIX commands in a VI session.
> How can I enter AT THE CURSER, the output of the  UNIX's  "date" command ?

vi has no builtin way to do this.
!!date
will overwrite the contents of the current line, or
:<address>r !date
will insert the date at <address> or after the current line if
<address> is not specified.  Otherwise, create a macro to do what
you want.

--
Roger Cornelius        sherpa!rac@uunet.uu.net       ...!uunet!sherpa!rac
Newsgroups: comp.editors
From: bt@irfu.se (Bo Thide')
Subject: Re: vi options 
Date: Fri, 2 Oct 1992 10:28:28 GMT
Organization: Swedish Institute of Space Physics, Uppsala, Sweden

In article <1992Sep30.221957.6250@infonode.ingr.com> "Vilva Natarajan <vilva@madras.b23b.ingr.COM>" writes:
>
> Hi,
>
>    From inside vi, a ":r!<cmd>" reads in the output of the
>    shell command into the file. Is there a way to do this
>    on the command line? I tried the -c option as follows
>	
>	vi -c ":r\!pwd" test
>
>    but the command output never shows up in the file.
>    Any help would be appreciated.
>
>
>
>vn
>
>----
>
>____________________________________________________________________
>
>Vilva Natarajan				Intergraph Corporation
>email: vilva@madras.b23b.ingr.com	Tel: 205-730-8544
>____________________________________________________________________


Say you want to enter the date on a line by using the UNIX date(1)
command.  Then, move to the line where you want the date.  There, in vi
command mode enter "!!date".  That's it.  the duble bang (!!) is
analogous to "dd" and "cc" etc, i.e., it means act on the whole line.

A useful thing for this command is to enter mathematical constants
without the risc of typos.  For instance, entering

a(1)*4

on a line and acting on this line with "!!bc -l" will give you pi with a
large number of correct decimals, the exact number probably depending on
your system's implementation of bc(1).  On my system (HP9000/720 HP-UX
8.07), the result is that the above line "a(1)*4" will be replaced by

3.14159265358979323844

which is enough precicison for most of my applications.

Bo
-- 
   ^   Bo Thide'--------------------------------------------------------------
  |I|        Swedish Institute of Space Physics, S-755 91 Uppsala, Sweden
  |R|      Phone: (+46) 18-303671.  Fax: (+46) 18-403100.  IP: 130.238.30.23
 /|F|\          INTERNET: bt@irfu.se      UUCP: ...!mcvax!sunic!irfu!bt  
 ~~U~~ ----------------------------------------------------------------sm5dfw-
From: imc@comlab.ox.ac.uk (Ian Collier)
Newsgroups: comp.editors
Subject: Re: Paragraphs and vi
Date: 5 Oct 92 11:49:07 GMT
Organization: Oxford University Computing Laboratory, UK
X-Local-Date: Monday, 5th October 1992 at 12:48pm BST
Originator: imc@msc3.comlab

In article <1992Oct5.075455.27645@cbfsb.cb.att.com>, nh@cbnewsg.cb.att.com (nicholas.hounsome) wrote:
>From article <1992Oct4.050951.2469@ils.nwu.edu>, by eric@ils.nwu.edu (Eric Goldstein):
>> ------------------------------------------------------------------
>> stty: TCGETS: Operation not supported on socket
>> This is a sample sentence.  This is sample sentence number two, which
>> is longer than the others.  This is sample sentence number three.  This
>> is sample sentence number four.
>> ------------------------------------------------------------------

>#!/bin/sh
>fmt "$@" 2>/dev/null

The message is generated by the shell - not by fmt - so that will not work.
I do not use vi, but it seems that it uses the value of $SHELL to carry out
any shell commands - even though it lies in such a way that "!}ps aux$$"
inserts the text "... sh -c ps aux$$" (the -c flag of ps correctly reports
that it is a csh).

Eric must be using a csh (or some such) and his .cshrc file contains an stty
command which generates that message whenever the standard output is not a
terminal.  The solution is to surround the stty (and anything else that
doesn't make sense in a non-interactive shell) by the following:

if $?prompt then   # it is an interactive shell
   stty -tostop
   ... blah blah
endif

Ian Collier
Ian.Collier@prg.ox.ac.uk | imc@ecs.ox.ac.uk
Newsgroups: comp.editors
From: dattier@ddsw1.mcs.com (DWT)
Subject: Re: UNIX COMMAND IN VI SESSION.
Date: Fri, 2 Oct 1992 17:37:38 GMT
Organization: Contributor Account at ddsw1, Chicago, Illinois  60657

hamjavar@carina.unm.edu (Farid Hamjavar) wrote in <=1=p9lb@lynx.unm.edu>:

| VI allows you to execute UNIX commands in a VI session.
| How can I enter AT THE CURSER, the output of the  UNIX's  "date" command ?

You mean at the current cursor position, even in the middle of a line?
That's not so easy.

Above the current line: :-r !date
Below the current line: :r !date

To put it after the cursor, does anyone have any better ideas than this one?

a<cr><esc>
:-r !date<cr>
k3J

It's inelegant but it works.  !l and !<sp> to give the ! command a scope that
isn't in whole lines don't agree with the version of vi running here.

[The following is equally awful but does the same thing:

a<cr><cr><esc>
-!!date<cr>
k3J

Yecch.]

David W. Tamkin   Box 59297   Northtown Station, Illinois  60659-0297
dattier@ddsw1.mcs.com    CompuServe: 73720,1570    MCI Mail: 426-1818
From: feoh@hal.gnu.ai.mit.edu (Chris Patti)
Subject: CRISP information wanted
Organization: MIT Laboratory for Computer Science
Date: Mon, 5 Oct 1992 19:27:16 GMT

Hello, I've recently acquired CRISP 2.1e and am trying to set it up on our
system V 3.2 systems. I'm encountering some serious problems that I was
wondering if anyone had solutions to..


Firstly: The instructions given contradict each other repeatedly regarding
SCO SysV3.2 setup/installation. one set says to use mapkey and mapstr, another
set says to use kbd (which won't even compile under sco, and when I compiled
it on another system and dragged the binary file over, it complained about an
invalid IOCTL call!) but this doesn't work..

I've tried dragging the compiled SCO binaries over to an AT*T system, which
works.. somewhat, however the screen handling is totally fouled up (highlights
obscure the characters they're supposed to be highlighting, etc) ..

We have tried myriad different configurations and tweaks, and none of them
appear to work for AT*T or SCO system V 3.2 systems.


If anyone has any hints/tips/fixes PLEASE Let me know, 

Also, does anyone know how/where / from whom to get the commercial version of
CRISP? My boss (whom this is for) has expressed interest in buyig a version 
if it would provide good solid support across all platforms...

Sincerely,
	Chris Patti
	chrisp@ncm.interlan.com	
	feoh@gnu.ai.mit.edu


Newsgroups: comp.editors
From: mpalmer@encore.com (Mike Palmer)
Subject: Writing a "block" of lines to another file
Organization: Encore Computer Corporation
Date: Sat, 26 Sep 1992 11:12:21 GMT

I'd like to be able to write a "block" of lines to a file, without having to
count the lines, or get the start & end loine number.  Can I use the temp
buffers something like:

mx
y'x
write x to file
Newsgroups: comp.editors
From: ant@mks.com (Anthony Howe)
Subject: Ae September '92 Patch 1
Organization: Mortice Kern Systems, Waterloo, Ontario, CANADA
Date: Tue, 29 Sep 1992 15:38:52 GMT

I've just found a bug with insert_mode() and K_STTY_ERASE not being
recognised.  The following patch will move the initscr() condition in main.c
to just before the initkey().  initkey() wants to be able to call erasechar()
or killchar() which requires that Curses be already initialized.

-ant
----->8 patch 1 >8-----
*** main.c.orig Tue Sep 29 11:26:05 1992
--- main.c Tue Sep 29 11:26:26 1992
***************
*** 62,67 ****
--- 62,69 ----
  		}
  	}
  
+ 	if (initscr() == NULL)
+ 		fatal(EXIT_INITSCR);
  	if (initkey(config, &key_map) != INITKEY_OK)
  		fatal(EXIT_CONFIG);
  
***************
*** 82,89 ****
  		}
  	}
  
- 	if (initscr() == NULL)
- 		fatal(EXIT_INITSCR);
  	noecho();
  	lineinput(FALSE);
  	idlok(stdscr, TRUE);
--- 84,89 ----
-- 
ant@mks.com                                                   Anthony C Howe 
Mortice Kern Systems Inc. 35 King St. N., Waterloo, Ontario, Canada, N2J 6W9
"Nice legs.  For a human that is." - Worf (Q-pid)
Newsgroups: comp.editors
From: ericm@hummer.ims.com (Eric Martinson)
Subject: Elvis 1.6
Organization: Integrated Measurement Systems, Inc.
Date: Fri, 2 Oct 1992 21:39:41 GMT

I am running Elvis 1.6 on a Sun IPX with Sun O/S 4.1.2.  Yesterday I tried
to use the map key to map a few of the function keys.  I want to create a
command on a function key that automatically reads in a code comment 
template and the current cursor position.  The following is the
map command I used:


:map ^[[11~   :r   /engr/ericm/templates/method.C^M

When I press the key associated with ^[[11~ I get dumped out of elvis.
I have never used mapping before but from the manuals and docs I read,
the above seems like it should work.  It works for Sun's vi.

Does anyone know how I get this to work in Elvis1.6.  Much appreciation
will be given for a solution.

-- 
==========================================================================
Eric C. Martinson                           Integrated Measurement Systems
ericm@ims.com                                               (503) 626-7117
==========================================================================
From: frechett@spot.Colorado.EDU (-=Runaway Daemon=-)
Newsgroups: comp.editors
Subject: Re: Overstrike mode in vi. Is there a way?
Date: 29 Sep 92 02:41:19 GMT
Organization: University of Colorado, Boulder

In article <1992Sep26.163713.14508@Celestial.COM> bill@Celestial.COM (Bill Campbell) writes:
>In <1992Sep25.153244.3116@fs7.ece.cmu.edu> sutton@dart.ece.cmu.edu (Peter Sutton) writes:
>
>:Simple: use 'R' (replace characters)
>
>Or R as in R(ead the manual :-).
>
>Bill

yes. yes.. I realize it was a simple question.  That's not a problem.  However
unless you have a nonstandard manual, then I'd have to say that YOU have 
not read the manual.  This command and about 100 more just like it are not
in TFM.

You want to see what I mean.. Here's a command you might try..
man vi | grep R

     Beginner's Reference Card and "An Introduction to Display Editing with
          <CTRL/L>     Reprints current screen.
          <CTRL/Y>     Exposes one more line at top of screen.
          <CTRL/E>     Exposes one more line at bottom of screen.
          <CTRL/F>     Pages forward one screen.
          <CTRL/B>     Pages back one screen.
          <CTRL/D>     Pages down half screen.
          <CTRL/U>     Pages up half screen.
          <RETURN>     Moves cursor to beginning of next line.
          n            Repeats last / or ? pattern search.
          rx           Replaces current character with x.
     -r name   Retrieves the last saved version of the name'd file in the
   Restrictions
     The Little Gray Book: An ULTRIX Primer
     The Big Gray Book: The Next Step with ULTRIX


Funny.. I READ the manual.  Did you?

The basic problem I had was that it wasn't in my handy keymap.  It's 
ussually got what I'm looking for, but it skipped that one.  It's been
added.

Thanks to all who replied.

	ian
Newsgroups: comp.editors
From: frechett@spot.Colorado.EDU (-=Runaway Daemon=-)
Subject: Re: Paragraphs and vi
Organization: University of Colorado, Boulder
Date: Tue, 6 Oct 1992 18:39:36 GMT

In article <1992Oct4.050951.2469@ils.nwu.edu> eric@ils.nwu.edu (Eric Goldstein) writes:
>The advice in each case was to use the Unix fmt command.
>In vi, fmt can be invoked for the paragraph in question by
>using the !}fmt command.
Unfortunately fmt is very limited and it may not be desired to format the 
whole paragraph to 78 columns only.  See my other responce for how to do 
it in vi.  (BTW, I'd love to see some way to automate those key bindings)


>stty: TCGETS: Operation not supported on socket

I've seen many responces to this and some of them are correct, some of
them are misguided.  The best way to avoid this problem all together
is to put 'stty', 'tset', 'biff', and 'mesg' commands in your .login
file which is only read when you login.  Assuming one is using a
csh variant .cshrc is loaded every time you execute a command unless
the '-f' flag of csh is used.

When you execute a command from vi it spawns a subshell which is not 
controlling a tty so anything that would try to modify the status of your tty 
(see above commands) get's very confused.  Unfortunately, they gave stty some 
strange error messages.  You'll notice two frequent ones. 
stty: Not a typewriter  and 
Where are you?
They both basically mean that stty knows there is no tty to muck with.
Keep an eye out. The solution that someone suggested by checking whether
it's an interactive shell or not can be useful in certain circumstances
but it's still easiest just to avoid the hassle all together and move it
out of your .cshrc.  Nuff said.

	ian