Re: One vi question, one emacs question

2003-02-06 Thread fred smith
On Thu, Feb 06, 2003 at 06:24:03AM -0800, exits funnel wrote: > First the vi question: I primarily use emacs but like > to be able to fire up vi every once in a while if I > just have a quick edit to make. Anyway, I've recently > installed RedHat 7.3 and when I launch vi ther

Re: One vi question, one emacs question

2003-02-06 Thread exits funnel
--- Gordon Messmer <[EMAIL PROTECTED]> wrote: > > Now the emacs question: I use emacs to edit c/c++ > > files. So far I like it, but there is one small > > annoyance I've run into. It indents blocks like > this: > > Put this in your .emacs file: > (setq c-default-style "bsd") > > If you like

Re: One vi question, one emacs question

2003-02-06 Thread exits funnel
--- Matthew Saltzman <[EMAIL PROTECTED]> wrote: > On Thu, 6 Feb 2003, exits funnel wrote: > > > First the vi question: I primarily use emacs but > like > > to be able to fire up vi every once in a while if > I > > just have a quick edit to make. Anyway, I&#x

Re: One vi question, one emacs question

2003-02-06 Thread Gordon Messmer
On Thu, 2003-02-06 at 06:24, exits funnel wrote: > First the vi question: Matthew seems to have answered that well enough... > Now the emacs question: I use emacs to edit c/c++ > files. So far I like it, but there is one small > annoyance I've run into. It indents blocks lik

Re: One vi question, one emacs question

2003-02-06 Thread Matthew Saltzman
On Thu, 6 Feb 2003, exits funnel wrote: > First the vi question: I primarily use emacs but like > to be able to fire up vi every once in a while if I > just have a quick edit to make. Anyway, I've recently > installed RedHat 7.3 and when I launch vi there is a > bit o

One vi question, one emacs question

2003-02-06 Thread exits funnel
First the vi question: I primarily use emacs but like to be able to fire up vi every once in a while if I just have a quick edit to make. Anyway, I've recently installed RedHat 7.3 and when I launch vi there is a bit of a problem with the display color. The tildes along the left edge o

Re: OT: vi and "|" - Another vi question

2002-06-15 Thread Anthony E. Greene
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-Jun-2002/12:09 -0400, Chris Mason <[EMAIL PROTECTED]> wrote: >No, that didn't so what I wanted. >I want to do this: >:s/HTML/CSS/ > >and then move down a line, and do it again >Moving down a line and pressing "." did not repeat it. At the next

Re: OT: vi and "|" - Another vi question

2002-06-15 Thread Dave Ihnat
On Sat, Jun 15, 2002 at 09:46:38AM -0700, Keith Morse wrote: > For a line by line case, the only solution I've come up > with is to copy the string :s/HTML/CSS/ with the mouse and paste it > (middle button) each time I need it. Oh, no, there are several approaches. The simplest would be to do

RE: OT: vi and "|" - Another vi question

2002-06-15 Thread Keith Morse
On Sat, 15 Jun 2002, Chris Mason wrote: > No, that didn't so what I wanted. > I want to do this: > :s/HTML/CSS/ > > and then move down a line, and do it again > Moving down a line and pressing "." did not repeat it. The form ":%s/HTML/CSS/g" will replace every instance in the documents witho

RE: OT: vi and "|" - Another vi question

2002-06-15 Thread Chris Mason
, June 14, 2002 2:58 PM To: [EMAIL PROTECTED] Subject: RE: OT: vi and "|" - Another vi question The "." is repeat last action... but... Here is a how-to site on vi http://helpme.scudc.scu.edu/vi-use.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE

RE: OT: vi and "|" - Another vi question

2002-06-14 Thread Linh Huynh
OT: vi and "|" - Another vi question How do you repeat the last action in vi? I run a search and replace on a line, then need to do it on another line, do I have to retype it? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of David Talkington S

RE: OT: vi and "|" - Another vi question

2002-06-14 Thread Chris Mason
How do you repeat the last action in vi? I run a search and replace on a line, then need to do it on another line, do I have to retype it? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of David Talkington Sent: Friday, June 14, 2002 1:08 PM To: [EMAIL PRO

Re: vi question

2000-09-21 Thread Vidiot
>I telnet into my box and vi into a file I try and push the arrow down key >and it pops a "B" character on the screen. But when I try to do the same >thing locally it works fine. Whats going on? >SK Are you running an Xterm when doing the telnet? If not, it doesn't know your terminal type. MB -

Re: vi question

2000-09-21 Thread Rob Tanner
Wrong terminal type set -- you probably need to set TERM=vt100 -- Rob --On 09/21/00 02:17:47 PM -0700 Stephen King <[EMAIL PROTECTED]> wrote: > I telnet into my box and vi into a file I try and push the arrow down > key and it pops a "B" character on the screen. But when I try to do > the same t

Re: vi question

2000-09-21 Thread Steve Borho
On Thu, Sep 21, 2000 at 02:17:47PM -0700, Stephen King wrote: > I telnet into my box and vi into a file I try and push the arrow down key > and it pops a "B" character on the screen. But when I try to do the same > thing locally it works fine. Whats going on? You're running vim locally and the re

Re: vi question

2000-09-21 Thread Michael R. Jinks
Sounds like terminal emulation discrepencies between the two machines. Are they both Linux boxes? What happens when you say "echo $TERM" on each machine? If they aren't both Linux boxes, it could be that the remote machine is running a different version of vi. "Real" vi doesn't recognize arro

vi question

2000-09-21 Thread Stephen King
I telnet into my box and vi into a file I try and push the arrow down key and it pops a "B" character on the screen. But when I try to do the same thing locally it works fine. Whats going on? SK ___ Redhat-list mailing list [EMAIL PROTECTED] https://l

vi question...

1998-03-19 Thread LG
Hi, I was recently sent a perl script that came from a windows machine. It wouldn't run as it was, so I opened it up in vi to see what was wrong, and I noticed at the bottom that it said the file was in [TEXTMODE]. Well, never seeing that before, I looked to see if I could change the mode some