[comp.lang.c++] VI and Turbo C++

pda@rsiatl.UUCP (Paul D. Anderson) (08/24/90)

patrickd@chinet.chi.il.us (Patrick Deupree) writes:
>				I've just gone down to make files and using
>TCC.  That way I can use VI for my editor instead of the turbo editor.
>The Window idea in the integrated environment was a nice idea though.  I
>wish I could make good use of it.  (Maybe if I read a manual for once I
>could figure it all out, eh?)

WAIT!  Following is a way to invoke VI EASILY from within the integrated
environment.

I'll admit, it took reading the manual to get the integrated environment 
closer to what I was comfortable using (One of the few times I have had 
to RTFM  :-).

Invoke TC and close ALL projects and open files.  If you don't do this, the
scope of your change will only be for the current project.  You want this
to be applied to all projects.  (Unfortunately, the change will not be 
applied to projects you have created prior to the change, since when you
create a project, a copy of the 'current' TC environment is made for the
project.)

Anyhow, to get VI to work with TC++, go to the Options menu, select Transfer.
Then select Edit.  You are going to modify this entry, then save it as a
new entry.  Change the 'Program Title' to read '~Vi'.  Change the 'Program
Path' to read 'vi.exe'  (or an explicit path, which makes loading VI faster).
Change the 'Command Line' to read '$MEM(256) $SAVE CUR $EDNAME'.  Then
select a new 'Hot Key' from the hot key menu.  The grayed out entries are 
already in use by other programs.  I chose F8, since on my keyboard, that
makes invoking the editor (via shift/f8) an easy sequence to hit.  Leave the
Translator check box empty.

When complete, select 'New', to save this as a new entry.  (You could select
modify, but you would lose the entry for 'grep'.)  Finally, select OK to 
save your changes, then save your entire environment by doing 'alt/O', 
'S'ave, o'K'.

Now open a text window with a file, punch shift/f8, and you should be up
in the vi.

By the by- by using the same set of setup windows, you can install lex,
yacc and other translators to do preprocessing for you (and get it to work
with the project make files).

Good luck.
-paul
-- 
* Paul Anderson * Crossroads Computing * (404) 565-0761 * emory!rsiatl!pda * 
              "SCCS: The condom of promiscuous programmers"

patrickd@chinet.chi.il.us (Patrick Deupree) (08/30/90)

In article <3699@rsiatl.UUCP> pda@rsiatl.UUCP (Paul D. Anderson) writes:
>WAIT!  Following is a way to invoke VI EASILY from within the integrated
>environment.

Thanks for the tip.  I'll give this a shot and see what I can do with
the Integrated Environment now.

-- 
"What's in a name?  That which we call a rose by any other name would smell
 as sweet."             William Shakespeare
Patrick Deupree ->	patrickd@chinet.chi.il.us   (708) 328-3800
(Please note there are both a patrick and a patrickd at this site)