Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-05 Thread Matt Miller
> > I don't want the editor to do whatever special screen buffer > > swapping, or whatever it is, that prevents me from scrolling back in > > my terminal history when the editor is open, and then clears away > > the screen and redisplays what was there before after the editor is > > closed. > > Thi

Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-04 Thread Aneurin Price
On Tue, Nov 4, 2008 at 6:36 AM, Cameron Hutchison <[EMAIL PROTECTED]> wrote: > Sven Joachim <[EMAIL PROTECTED]> writes: > >>On 2008-11-04 06:28 +0100, Matt Miller wrote: > > Also, I don't want the editor to do whatever special screen buffer > swapping, or whatever it is, that prevents me

Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-03 Thread Cameron Hutchison
Sven Joachim <[EMAIL PROTECTED]> writes: >On 2008-11-04 06:28 +0100, Matt Miller wrote: >>> > Also, I don't want the editor to do whatever special screen buffer >>> > swapping, or whatever it is, that prevents me from scrolling back in >>> > my terminal history when the editor is open, and then c

Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-03 Thread Sven Joachim
On 2008-11-04 06:28 +0100, Matt Miller wrote: >> > Also, I don't want the editor to do whatever special screen buffer >> > swapping, or whatever it is, that prevents me from scrolling back in >> > my terminal history when the editor is open, and then clears away >> > the screen and redisplays what

Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-03 Thread Matt Miller
> > From GNOME terminal, when I: > > > > vi x :set nu > > > > the line numbers are colored, and I want to get rid of that. > > you could change the default alternative setup to point to nvi > instead. Thanks, that got rid of the colorized line numbers. > > Also, I don't want the editor to do what

Re: vi -- Turn off Line Number Colors and Screen Buffering

2008-11-03 Thread Bob McGowan
On Sat, 2008-11-01 at 23:16 +0100, Matt Miller wrote: > >From GNOME terminal, when I: > > vi x > :set nu > > the line numbers are colored, and I want to get rid of that. Also, I > don't want the editor to do whatever special screen buffer swapping, or > whatever it is, that prevents me from scro

Re: vi issue in etch

2007-12-04 Thread s. keeling
[EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > Vim really is Improved. I agree. However, that can be a feature or a detriment, depending on the situation. Don't expect vim features in all instances where you'd expect vi to fill the bill. Bare metal commercial Unix comes to mind. /bin/bash isn't

Re: vi issue in etch

2007-12-02 Thread cls
[This message has also been posted to linux.debian.user.] In article <[EMAIL PROTECTED]>, David Fox wrote: > On 11/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> I tried to use the equivs package to inform Etch that my >> custom vim "provides vi", and link it to the >> /etc/alternatives/v

Re: vi issue in etch

2007-12-01 Thread Thomas Dickey
Joseph L. Casale <[EMAIL PROTECTED]> wrote: > While you are at it, consider using vim instead of vi unless you have a good > reason not to do so. this statement leads naturally into the next: > Well, therein lies my lack of experience! I didn't even know there was a > difference, vim is what I

Re: vi issue in etch

2007-11-30 Thread David Fox
On 11/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I tried to use the equivs package to inform Etch that my > custom vim "provides vi", and link it to the > /etc/alternatives/vi, but I got lost in the complexity of it. I am not so sure that you need to go that far to get the same functio

Re: vi issue in etch

2007-11-30 Thread cls
[This message has also been posted to linux.debian.user.] [use vim, not [n]vi] In article <[EMAIL PROTECTED]>, Joseph L. Casale wrote: > > Well, therein lies my lack of experience! I didn't even know there >was a difference, vim is what I "meant" to use but didn't know I wasn't, >hence the apt-get

RE: vi issue in etch

2007-11-29 Thread Joseph L. Casale
-Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Kamaraju S Kusumanchi Sent: Thursday, November 29, 2007 10:01 PM To: debian-user@lists.debian.org Subject: Re: vi issue in etch Joseph L. Casale wrote: > Hi everyone, > I have my keyboard setup as us and in the c

Re: vi issue in etch

2007-11-29 Thread Kamaraju S Kusumanchi
Joseph L. Casale wrote: > Hi everyone, > I have my keyboard setup as us and in the console every key works > correctly. In vi though everything is messed up! The standard shortcuts > don't work. While following a tutorial, after an apt-get of a series of > apps I noticed it start working like it s

Re: vi, vim, and update-alternatives

2007-03-19 Thread Paul E Condon
On Mon, Mar 19, 2007 at 09:45:31PM -0400, Joey Hess wrote: > Paul E Condon wrote: > > 'vi' is not in this list, so I can't say what vim.tiny should do when > > it is invoked via the update-alternatives symlink, vi, but I think it > > is not doing something that its maintainers intend. Is this a bug

Re: vi, vim, and update-alternatives

2007-03-19 Thread Joey Hess
Paul E Condon wrote: > 'vi' is not in this list, so I can't say what vim.tiny should do when > it is invoked via the update-alternatives symlink, vi, but I think it > is not doing something that its maintainers intend. Is this a bug? Or > is it working in some mode that is useful, but only to those

Re: vi, vim, and update-alternatives [solved]

2007-03-19 Thread Thomas Jollans
On Monday 19 March 2007 22:22, Paul E Condon wrote: > Now, I think I have never actually used vi. Instead, I have always been > using versions of vim that were loaded when I typed 'vi'. My ignorance is > revealed, but I learn, slowly. The closest free piece of software you can get is, AFAIK, nvi (

Re: vi, vim, and update-alternatives [solved]

2007-03-19 Thread Paul E Condon
On Mon, Mar 19, 2007 at 05:02:09PM -0400, Kamaraju S Kusumanchi wrote: > Paul E Condon wrote: > > > > When I was using Sarge, and early upgrades to Etch, I had avoided > > using vim because I never felt I had the time to learn about its > > 'improved features'. Now, when I run vi, it behaves in a

Re: vi, vim, and update-alternatives

2007-03-19 Thread Kamaraju S Kusumanchi
Paul E Condon wrote: > When I was using Sarge, and early upgrades to Etch, I had avoided > using vim because I never felt I had the time to learn about its > 'improved features'. Now, when I run vi, it behaves in a strange > way that I dislike, and I can get back to what I thought was vi > behavi

Re: vi, vim, and update-alternatives

2007-03-19 Thread Ron Johnson
On 03/19/07 15:32, Paul E Condon wrote: > I have done a new install of etch, and discovered a situation > that I find problematic. I don't know vi or vim well enough to > recognize which I am actually running by observing the behavior > of the running program, so some of my description of the situa

Re: Vi problems from recent upgrade

2006-05-25 Thread Glenn Becker
You should know that Vim behaves differently when invoked as vi then when invoked as vim. Therefore, you may want to use vim from now on. or use elvis. i have come to like elvis quite a lot. the debian install defaults to the elvis GUI, which i can take or leave, but i'm sure there is a way

Re: Vi problems from recent upgrade

2006-05-25 Thread Felix C. Stegerman
* David Baron <[EMAIL PROTECTED]> [2006-05-24 16:15]: > In more recent versions of vi (vim), the insert/replace keyed > functionality is no longer working as it was. The prompt "insert" or > "replace" does not appear, one cannot go to the very end (after last > character) of the line, and the direc

Re: Vi problems from recent upgrade

2006-05-25 Thread Paul Dwerryhouse
On Wed, May 24, 2006 at 05:15:19PM +0300, David Baron wrote: > In more recent versions of vi (vim), the insert/replace keyed > functionality is no longer working as it was. The prompt "insert" or > "replace" does not appear, one cannot go to the very end (after last > character) of the line, and th

Re: Vi problems from recent upgrade

2006-05-24 Thread Richard
On 24/05/06, David Baron <[EMAIL PROTECTED]> wrote: In more recent versions of vi (vim), the insert/replace keyed functionality is no longer working as it was. The prompt "insert" or "replace" does not appear, one cannot go to the very end (after last character) of the line, and the direction key

Re: vi flashes in KDE shell

2006-02-19 Thread A. F. Cano
On Sat, Feb 18, 2006 at 09:09:35PM -0800, Rob Blomquist wrote: > Is there anyway to fix this problem? It drives me nuts. Basically the gui > flashes occassionally and seems to miss commands I give it. Could this be the visual bell? I have encountered this in sarge, although it (the regular beep)

Re: vi trying to connect to X

2006-02-06 Thread Anthony Simonelli
On Monday 06 February 2006 03:20 am, Karsten M. Self wrote: > You've apparently got the gvim variant of vim installed, and it may be > doing stupid things presuming it's got an X display active. > > Try: > >unset DISPLAY >vi foo > > ... and see if that resolves the issue. If it doesn't, po

Re: vi trying to connect to X

2006-02-06 Thread Chris Howie
Kumar Appaiah wrote: > I think vim is trying to change the title of the Konsole window to > Vim. Setting the title is done through escape codes, not X: echo -e '\033]2;Hello, World!\a' -- Chris Howie http://www.chrishowie.com -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS/IT d-(--) s:- a--->

Re: vi trying to connect to X

2006-02-06 Thread Kumar Appaiah
On Mon, Feb 06, 2006 at 01:20:04AM -0800, Karsten M. Self wrote: > > Xlib: connection to ":0.0" refused by server > > Xlib: No protocol specified > > > > Xlib: connection to ":0.0" refused by server > > Xlib: No protocol specified > > > > Xlib: connection to ":0.0" refused by server > > Xlib: No

Re: vi trying to connect to X

2006-02-06 Thread Chris Howie
Karsten M. Self wrote: > You've apparently got the gvim variant of vim installed, and it may be > doing stupid things presuming it's got an X display active. vim tries to connect X for access to the X clipboard. :help x11-selection -- Chris Howie http://www.chrishowie.com -BEGIN GEEK CODE

Re: vi trying to connect to X

2006-02-06 Thread Karsten M. Self
on Sun, Feb 05, 2006 at 05:08:15PM -0600, Anthony Simonelli ([EMAIL PROTECTED]) wrote: > Hi there. I'm tried to get used to vi as an editor since it is found on > nearly every Unix and Unix-like system and I've heard that those who are > proficient at it are able to edit files faster than using

Re: vi trying to connect to X

2006-02-05 Thread Duncan Anderson
On Monday, 6 February 2006 04:58, Anthony Simonelli wrote: > On Sunday 05 February 2006 08:50 pm, Duncan Anderson wrote: > > On Monday, 6 February 2006 04:19, Shawn Lamson wrote: > > > On Sun, 05 Feb 2006 17:08:15 -0600 > > > > > > Anthony Simonelli <[EMAIL PROTECTED]> wrote: > > > > I'm running KD

Re: vi trying to connect to X

2006-02-05 Thread Anthony Simonelli
On Sunday 05 February 2006 08:50 pm, Duncan Anderson wrote: > On Monday, 6 February 2006 04:19, Shawn Lamson wrote: > > On Sun, 05 Feb 2006 17:08:15 -0600 > > > > Anthony Simonelli <[EMAIL PROTECTED]> wrote: > > > I'm running KDE and use Konsole but everytime I invoke vi from Konsole, > > > I get t

Re: vi trying to connect to X

2006-02-05 Thread Duncan Anderson
On Monday, 6 February 2006 04:19, Shawn Lamson wrote: > On Sun, 05 Feb 2006 17:08:15 -0600 > > Anthony Simonelli <[EMAIL PROTECTED]> wrote: > > I'm running KDE and use Konsole but everytime I invoke vi from Konsole, I > > get the following: > > > > Xlib: connection to ":0.0" refused by server > > X

Re: vi trying to connect to X

2006-02-05 Thread Shawn Lamson
On Sun, 05 Feb 2006 17:08:15 -0600 Anthony Simonelli <[EMAIL PROTECTED]> wrote: > I'm running KDE and use Konsole but everytime I invoke vi from Konsole, I get > the following: > > Xlib: connection to ":0.0" refused by server > Xlib: No protocol specified have you restarted X recently? If not,

Re: vi globally append question

2004-07-15 Thread Patrick Albuquerque
From: Rick Pasotto <[EMAIL PROTECTED]> > On Thu, Jul 15, 2004 at 10:05:43PM -0500, Patrick Albuquerque wrote: > > From: Sean <[EMAIL PROTECTED]> Date: Thursday, July 15, 2004 8:49 > > am Subject: vi globally append question > > > > > hi all, > > > > > > i have a file like; > > > > > > # one 123

Re: vi globally append question

2004-07-15 Thread Rick Pasotto
On Thu, Jul 15, 2004 at 10:05:43PM -0500, Patrick Albuquerque wrote: > From: Sean <[EMAIL PROTECTED]> Date: Thursday, July 15, 2004 8:49 > am Subject: vi globally append question > > > hi all, > > > > i have a file like; > > > > # one 123 > > > > and i would like to APPEND a # at the beginning

Re: vi globally append question

2004-07-15 Thread Patrick Albuquerque
From: Sean <[EMAIL PROTECTED]> Date: Thursday, July 15, 2004 8:49 am Subject: vi globally append question > hi all, > > i have a file like; > > # > one > 123 > > and i would like to APPEND a # at the beginning of > each line which is not started with a # . how can i do > it with vi or ed, so fa

Re: vi globally append question

2004-07-15 Thread Matthias Czapla
On Thu, Jul 15, 2004 at 02:25:52PM -0400, Rick Pasotto wrote: > On Thu, Jul 15, 2004 at 07:45:26PM +0200, Matthias Czapla wrote: > > On Thu, Jul 15, 2004 at 11:05:32AM -0400, David Turetsky wrote: > > > > i have a file like; > > > > > > > > # > > > > one > > > > 123 > > > > > > > > and i would li

Re: vi globally append question

2004-07-15 Thread Rick Pasotto
On Thu, Jul 15, 2004 at 07:45:26PM +0200, Matthias Czapla wrote: > On Thu, Jul 15, 2004 at 11:05:32AM -0400, David Turetsky wrote: > > > i have a file like; > > > > > > # > > > one > > > 123 > > > > > > and i would like to APPEND a # at the beginning of > > > each line which is not started with a

Re: vi globally append question

2004-07-15 Thread Ken Irving
On Thu, Jul 15, 2004 at 12:06:07PM -0400, David Turetsky wrote: > > David Turetsky wrote: > > >>:%s/^[a-z]:[0-9]/#/g > > > Try something like: > > > %g!/^#/s/^/#/ > > > Steve Lamb replied: > > >Personally I'd do it this way: > >%s/\(.*\)/#\1/g > > David responded: > > Steve's ap

Re: vi globally append question

2004-07-15 Thread Matthias Czapla
On Thu, Jul 15, 2004 at 11:05:32AM -0400, David Turetsky wrote: > > i have a file like; > > > > # > > one > > 123 > > > > and i would like to APPEND a # at the beginning of > > each line which is not started with a # . how can i do > > it with vi or ed, so far, i 've tried; > > > > :%s/^[a-z]:[0

Re: vi globally append question

2004-07-15 Thread Robert Waldner
On Thu, 15 Jul 2004 06:49:20 PDT, Sean writes: >and i would like to APPEND a # at the beginning of >each line which is not started with a # . how can i do >it with vi or ed, so far, i 've tried; > >:%s/^[a-z]:[0-9]/#/g > >but this would CHANGE the first character of each line >to a hash, pls help.

Re: vi globally append question

2004-07-15 Thread Steve Lamb
David Turetsky wrote: > Steve's approach would put a # in the front of ALL > lines whether or not they initially contain an existing > # to begin with Oh, uh, whoops. :) Well, at least he'd see the \(.*\) and \1 move the text over and hopefully know to take the set he constructed, plac

RE: vi globally append question

2004-07-15 Thread David Turetsky
David Turetsky wrote: >>:%s/^[a-z]:[0-9]/#/g > Try something like: > %g!/^#/s/^/#/ > Steve Lamb replied: >Personally I'd do it this way: >%s/\(.*\)/#\1/g David responded: Steve's approach would put a # in the front of ALL lines whether or not they initially contain an existi

Re: vi globally append question

2004-07-15 Thread Steve Lamb
David Turetsky wrote: >>:%s/^[a-z]:[0-9]/#/g > Try something like: > %g!/^#/s/^/#/ Personally I'd do it this way: %s/\(.*\)/#\1/g I know there are more concise ways to do it but this at least shows why the approach the OP took was not working. -- Steve C. Lamb | I'

RE: vi globally append question

2004-07-15 Thread David Turetsky
> -Original Message- > From: Sean [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 15, 2004 9:49 AM > To: debian-user > Subject: vi globally append question > > hi all, > > i have a file like; > > # > one > 123 > > and i would like to APPEND a # at the beginning of > each line which is

Re: vi globally append question

2004-07-15 Thread Derrick 'dman' Hudson
On Thu, Jul 15, 2004 at 10:24:32AM -0400, Rick Pasotto wrote: | On Thu, Jul 15, 2004 at 06:49:20AM -0700, Sean wrote: | > hi all, | > | > i have a file like; | > | > # one 123 | > | > and i would like to APPEND a # at the beginning of each line | | 'append' means to add to the end. It is imposs

Re: vi globally append question

2004-07-15 Thread Rick Pasotto
On Thu, Jul 15, 2004 at 06:49:20AM -0700, Sean wrote: > hi all, > > i have a file like; > > # one 123 > > and i would like to APPEND a # at the beginning of each line 'append' means to add to the end. It is impossible to append to the beginning of something. > which is not started with a # . h

Re: vi Qustion

2003-07-11 Thread Richard Heycock
On Sat, 2003-07-12 at 10:01, Steve Lamb wrote: > On 12 Jul 2003 00:52:25 +1000 > Richard Heycock <[EMAIL PROTECTED]> wrote: > > On Fri, 2003-07-11 at 12:29, Steve Lamb wrote: > > > On 11 Jul 2003 12:23:21 +1000 > > > Richard Heycock <[EMAIL PROTECTED]> wrote: > > > > The easiest way to do this is t

Re: vi Qustion

2003-07-11 Thread Steve Lamb
On Fri, 11 Jul 2003 20:10:34 -0500 Kirk Strauser <[EMAIL PROTECTED]> wrote: > Seriously, I find that the Emacs-style keybinds are nearly universal. > Honestly, I've never once found myself wishing that I had a home key. I rarely do. However I find that I can keep tabs on what is needed for ho

Re: vi Qustion

2003-07-11 Thread Kirk Strauser
At 2003-07-11T23:56:50Z, Steve Lamb <[EMAIL PROTECTED]> writes: > Ungh, now I know why I never got one of those. :/ Seriously, I find that the Emacs-style keybinds are nearly universal. Honestly, I've never once found myself wishing that I had a home key. Now, if only Konqueror wouldn't launch

Re: vi Qustion

2003-07-11 Thread Steve Lamb
On 12 Jul 2003 00:52:25 +1000 Richard Heycock <[EMAIL PROTECTED]> wrote: > On Fri, 2003-07-11 at 12:29, Steve Lamb wrote: > > On 11 Jul 2003 12:23:21 +1000 > > Richard Heycock <[EMAIL PROTECTED]> wrote: > > > The easiest way to do this is to type: > > > A [insert at the beginning of

Re: vi Qustion

2003-07-11 Thread Steve Lamb
On Fri, 11 Jul 2003 09:08:28 -0500 Kirk Strauser <[EMAIL PROTECTED]> wrote: > Here's a picture of mine: Ungh, now I know why I never got one of those. :/ -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your PGP Key: 8B6E99C5 | main connection to the sw

Re: vi Qustion

2003-07-11 Thread Richard Heycock
On Fri, 2003-07-11 at 12:29, Steve Lamb wrote: > On 11 Jul 2003 12:23:21 +1000 > Richard Heycock <[EMAIL PROTECTED]> wrote: > > The easiest way to do this is to type: > > A [insert at the beginning of the line] > > > > j [moves down one line] > > . [re-does the last c

Re: vi Qustion

2003-07-11 Thread Kirk Strauser
At 2003-07-11T02:29:10Z, Steve Lamb <[EMAIL PROTECTED]> writes: > Ungh. You're the second person to advocate the stupid home keys. That > isn't easy. Point me to a keyboard made in the last 20 years without > them. Hell, even my *PALM* keyboard has them! Here's a picture of mine: http://

Re: vi Qustion

2003-07-10 Thread Steve Lamb
On Thu, 10 Jul 2003 22:42:35 -0400 Rick Pasotto <[EMAIL PROTECTED]> wrote: > :%s/^/text/ > is all you need. Showing the regex was also covering the other base which is if the entire line isn't needed, or repeating text in the line. IE *any regex can go here*. > You sure like to do things t

Re: vi Qustion

2003-07-10 Thread Rick Pasotto
On Thu, Jul 10, 2003 at 07:29:10PM -0700, Steve Lamb wrote: > On 11 Jul 2003 12:23:21 +1000 > Richard Heycock <[EMAIL PROTECTED]> wrote: > > The easiest way to do this is to type: > > A [insert at the beginning of the line] > > > > j [moves down one line] > > . [re-do

Re: vi Qustion

2003-07-10 Thread Steve Lamb
On 11 Jul 2003 12:23:21 +1000 Richard Heycock <[EMAIL PROTECTED]> wrote: > The easiest way to do this is to type: > A [insert at the beginning of the line] > > j [moves down one line] > . [re-does the last command] > > This will work in both vi and vim. Un

Re: vi Qustion

2003-07-10 Thread Richard Heycock
On Fri, 2003-07-11 at 09:25, Jake Johnson wrote: > I used to be able to use the arrow keys to move around with out any > problems, but know when I move (with the arrow keys after pressing "i") to > the beginning of the line I have to press I again. How do I change it so > that I don't always have

Re: vi Qustion

2003-07-10 Thread Zhao YouBing
Jake Johnson wrote: Thanks Nicos, This has been bugging me for a while now. I just installed vim and it works perfectly. Thanks again, Jake Johnson [EMAIL PROTECTED] __ Plutoid - http://www.plutoid.com - Shop Plutoid for the best

Re: vi Qustion

2003-07-10 Thread Jake Johnson
Thanks Nicos, This has been bugging me for a while now. I just installed vim and it works perfectly. Thanks again, Jake Johnson [EMAIL PROTECTED] __ Plutoid - http://www.plutoid.com - Shop Plutoid for the best prices on Rims, Car

Re: vi Qustion

2003-07-10 Thread Nicos Gollan
On Friday 11 July 2003 01:25, Jake Johnson wrote: > I used to be able to use the arrow keys to move around with out any > problems, but know when I move (with the arrow keys after pressing "i") to > the beginning of the line I have to press I again. How do I change it so > that I don't always have

Re: vi temporary files remaining in dir

2003-02-10 Thread Joris Huizer
--- Gregory Seidman <[EMAIL PROTECTED]> wrote: > Joris Huizer sez: > } I hope someone can help on this problem I have: > each > } time I edit a file using VIM, " Vi IMproved 6.1 > (2002 > } Mar 24, compiled Apr 14 2002 20:41:29)" I get a > } "temporary" copy of the original file. > } > } The nami

Re: vi temporary files remaining in dir

2003-02-10 Thread Gregory Seidman
Joris Huizer sez: } I hope someone can help on this problem I have: each } time I edit a file using VIM, " Vi IMproved 6.1 (2002 } Mar 24, compiled Apr 14 2002 20:41:29)" I get a } "temporary" copy of the original file. } } The naming is as follows: when I edit, say, trash.txt, } the "temporary" c

Re: vi alternate problem

2002-12-19 Thread Tom Allison
Bob Proulx wrote: Tom Allison <[EMAIL PROTECTED]> [2002-12-17 20:12:29 -0500]: One day I installed 'vim'. Now I have nothing that is recognized as 'vi' What do I actually install in order to regain this tidy little editor? update-alternatives --config vi Then select nvi as the alternative.

Re: vi alternate problem

2002-12-19 Thread Tom Allison
Nathan E Norman wrote: On Tue, Dec 17, 2002 at 08:12:29PM -0500, Tom Allison wrote: One day I installed 'vim'. Now I have nothing that is recognized as 'vi' What do I actually install in order to regain this tidy little editor? Hrm. Post the output of 'update-alternatives --display vi' ide

Re: vi alternate problem

2002-12-18 Thread Michael Naumann
On Wednesday 18 December 2002 03:20, Eric G. Miller wrote: > Vim has a compatibility mode (vim -v) to more like the > original vi... That would be "vim -C". Though I never had the need to use this. "vim -c" starts in vi-mode, not compatibility mode. The difference is, that vi-mode is to be seen ve

Re: vi alternate problem

2002-12-18 Thread Bob Proulx
Tom Allison <[EMAIL PROTECTED]> [2002-12-17 20:12:29 -0500]: > One day I installed 'vim'. > Now I have nothing that is recognized as 'vi' > What do I actually install in order to regain this tidy little editor? update-alternatives --config vi Then select nvi as the alternative. Or you could re

Re: vi alternate problem

2002-12-17 Thread Eric G. Miller
On Tue, Dec 17, 2002 at 08:12:29PM -0500, Tom Allison wrote: > One day I installed 'vim'. > > Now I have nothing that is recognized as 'vi' > > What do I actually install in order to regain this tidy little editor? nvi maybe? Vim has a compatibility mode (vim -v) to more like the original vi...

Re: vi alternate problem

2002-12-17 Thread Nathan E Norman
On Tue, Dec 17, 2002 at 08:12:29PM -0500, Tom Allison wrote: > One day I installed 'vim'. > > Now I have nothing that is recognized as 'vi' > > What do I actually install in order to regain this tidy little editor? Hrm. Post the output of 'update-alternatives --display vi' ideally you'd see som

Re: vi as a text editor

2002-11-21 Thread Derrick 'dman' Hudson
On Wed, Nov 20, 2002 at 07:37:57PM -0500, Nori Heikkinen wrote: | on Wed, 20 Nov 2002 06:25:57PM -0500, Derrick 'dman' Hudson insinuated: | > The problem with using TERM=xterm on Solaris is that all you get is | > bold and underlines for "highlighting" because programs will think | > your terminal

Re: vi as a text editor

2002-11-20 Thread Nori Heikkinen
on Wed, 20 Nov 2002 06:25:57PM -0500, Derrick 'dman' Hudson insinuated: > On Sun, Nov 17, 2002 at 01:58:28PM -0500, Nori Heikkinen wrote: > > | really? i've been beating my head against this for a while now, and > | have to date only managed to get dark-blue-and-pink syntax > | highlighting on th

Re: vi as a text editor

2002-11-20 Thread Nori Heikkinen
on Wed, 20 Nov 2002 11:44:22AM -0600, Andy Wettstein insinuated: > This works for me in .bashrc on solaris 8: > > if [ `uname` = "SunOS" ]; then > export TERM=xtermc > fi exporting TERM to be xtermc doesn't seem to do anything here. > i Compiled vim with ncurses5, not the sun curse

Re: vi as a text editor

2002-11-20 Thread Derrick 'dman' Hudson
On Sun, Nov 17, 2002 at 01:58:28PM -0500, Nori Heikkinen wrote: | really? i've been beating my head against this for a while now, and | have to date only managed to get dark-blue-and-pink syntax | highlighting on the Suns i work on ... exporting TERM=dtterm doesn't | seem to do much, either. do

Re: vi as a text editor

2002-11-20 Thread Andy Wettstein
On Sun, Nov 17, 2002 at 01:58:28PM -0500, Nori Heikkinen wrote: > on Sat, 16 Nov 2002 06:15:20PM -0500, Derrick 'dman' Hudson insinuated: > > On Sat, Nov 16, 2002 at 03:05:38AM -0600, Rob VanFleet wrote: > > | since Solaris never seems to understand my remote terminal well > > | enough to allow sy

Re: vi as a text editor

2002-11-17 Thread Nori Heikkinen
on Sat, 16 Nov 2002 06:15:20PM -0500, Derrick 'dman' Hudson insinuated: > On Sat, Nov 16, 2002 at 03:05:38AM -0600, Rob VanFleet wrote: > | since Solaris never seems to understand my remote terminal well > | enough to allow syntax highlighting. Does anyone know how to fix > | that? :) > > export

Re: vi as a text editor

2002-11-17 Thread Rob Weir
On Sat, Nov 16, 2002 at 05:26:43PM -0600, Rob VanFleet wrote: > I can't really comment on emacs other than the fact that when I have > large chunk of time open, I'll try to learn it. I forced myself to > learn vim when I first started using Linux by using it to write mail. > Emacs is a little hef

Re: vi as a text editor

2002-11-17 Thread Vineet Kumar
* Rob VanFleet ([EMAIL PROTECTED]) [021115 23:26]: > > moreover, i have spell, ispell and aspell installed. is there a way i > > can use them while in vi? > > If the file has been saved, just run > > :!ispell % > > I think there is a way to spell check an unsaved file, but I can't > recall it a

Re: vi as a text editor

2002-11-16 Thread Tim St. Croix
On Sun, 17 Nov 2002 14:17:28 +1100, you wrote: > "remove .sig from messages I am replying to >au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1dgg > I got that line about >removing the .sig from someone on here, but it doesn't actually seem to >work... I'm not sure but it looks like you're l

Re: vi as a text editor

2002-11-16 Thread Rob Weir
On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: > hello all > > i have recently started using vi and i like it for its simplicity - > 'clean-ness'. somethings are missing though. Try vim: VI iMproved. It has all sorts of nifty extras. > one is managing words towards end of li

Re: vi as a text editor

2002-11-16 Thread Matthew Weier O'Phinney
-- Stephen Gran <[EMAIL PROTECTED]> wrote (on Saturday, 16 November 2002, 01:12 PM -0500): > This one time, at band camp, Sandip P Deshmukh said: > > i have recently started using vi and i like it for its simplicity - > > 'clean-ness'. somethings are missing though. > > > > one is managing words t

Re: vi as a text editor

2002-11-16 Thread Rob VanFleet
On Sat, Nov 16, 2002 at 05:03:34PM -0600, Shyamal Prasad wrote: > I've used vi for at least 14 years now, I switched to emacs for > "heavy" editing about 10 years ago. But you *must* know vi if you ever > want to be real Unix user. Learn it. You will be rewarded. That is the > only reason I don't u

Re: vi as a text editor

2002-11-16 Thread Derrick 'dman' Hudson
On Fri, Nov 15, 2002 at 10:59:17PM -0800, nate wrote: | You can test this by typing several lines, then going back to | command mode () and scroll up and down the file, it will | scroll one line at a time, if it jumps 2-3 lines at once, that is | just 1 really long line. Actually, if you use a ma

Re: vi as a text editor

2002-11-16 Thread Shyamal Prasad
"Osamu" == Osamu Aoki <[EMAIL PROTECTED]> writes: Osamu> On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh Osamu> wrote: >> >> one is managing words towards end of line. as i type, towards >> the end of the line, it juts cuts the word. it neither >> hyphanate

Re: vi as a text editor

2002-11-16 Thread Derrick 'dman' Hudson
On Sat, Nov 16, 2002 at 03:05:38AM -0600, Rob VanFleet wrote: | On Sat, Nov 16, 2002 at 01:30:09PM +0530, Sandip P Deshmukh wrote: | > On Sat, Nov 16, 2002 at 01:24:27AM -0600, Rob VanFleet wrote: | > > On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: | > no. someone asked me t

Re: vi as a text editor

2002-11-16 Thread Stephen Gran
This one time, at band camp, Sandip P Deshmukh said: > hello all > > i have recently started using vi and i like it for its simplicity - > 'clean-ness'. somethings are missing though. > > one is managing words towards end of line. as i type, towards the end > of the line, it juts cuts the word. i

Re: vi as a text editor

2002-11-16 Thread Rob VanFleet
On Sat, Nov 16, 2002 at 01:30:09PM +0530, Sandip P Deshmukh wrote: > On Sat, Nov 16, 2002 at 01:24:27AM -0600, Rob VanFleet wrote: > > On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: > > > hello all > > > > > > one is managing words towards end of line. as i type, towards the e

Re: vi as a text editor

2002-11-16 Thread Sandip P Deshmukh
On Sat, Nov 16, 2002 at 01:24:27AM -0600, Rob VanFleet wrote: > On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: > > hello all > > > > one is managing words towards end of line. as i type, towards the end > > of the line, it juts cuts the word. it neither hyphanates nor pushes >

Re: vi as a text editor

2002-11-15 Thread Rob VanFleet
On Sat, Nov 16, 2002 at 01:24:27AM -0600, Rob VanFleet wrote: > :map! longhash 60i#o > > The above creates a macro that prints 60 "#" characters when you type > the word 'longhash'. The  is Control-v,Esc to simulate going into Actually, 'simulate' was a poor choice of word on my part. It *d

Re: vi as a text editor

2002-11-15 Thread Rob VanFleet
On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: > hello all > > i have recently started using vi and i like it for its simplicity - > 'clean-ness'. somethings are missing though. > > one is managing words towards end of line. as i type, towards the end > of the line, it juts cu

Re: vi as a text editor

2002-11-15 Thread Sandip P Deshmukh
On Fri, Nov 15, 2002 at 10:59:17PM -0800, nate wrote: > Sandip P Deshmukh said: > > hello all > > > > i have recently started using vi and i like it for its simplicity - > > 'clean-ness'. somethings are missing though. > > > > one is managing words towards end of line. as i type, towards the end of

Re: vi as a text editor

2002-11-15 Thread nate
Sandip P Deshmukh said: > hello all > > i have recently started using vi and i like it for its simplicity - > 'clean-ness'. somethings are missing though. > > one is managing words towards end of line. as i type, towards the end of > the line, it juts cuts the word. it neither hyphanates nor pushes

Re: vi as a text editor

2002-11-15 Thread Osamu Aoki
On Sat, Nov 16, 2002 at 12:18:11PM +0530, Sandip P Deshmukh wrote: > hello all > > i have recently started using vi and i like it for its simplicity - > 'clean-ness'. somethings are missing though. > > one is managing words towards end of line. as i type, towards the end > of the line, it juts cu

Re: vi saved file message from root

2002-09-13 Thread Karl E. Jorgensen
On Thu, Sep 12, 2002 at 06:45:56PM -0600, Bob Proulx wrote: [snip,snip,snip] > Perhaps someone will suggest a package that cleans /tmp and /var/tmp > in Debian? yes (for /tmp): tmpreaper Note that /var/tmp is meant to be more permanent (or less temporary, depending on how you look at it) than

Re: vi saved file message from root

2002-09-12 Thread Bob Proulx
Richard Otte <[EMAIL PROTECTED]> [2002-09-12 14:50:52 -0700]: > On Thu, Sep 12, 2002 at 09:51:19AM -0600, Bob Proulx wrote: > > You can list files that are available for recover with 'vi -r'. At > > boot time or perhaps by cron this is being mailed to users. > > I tried this, and it didn't list

Re: vi saved file message from root

2002-09-12 Thread Richard Otte
On Thu, Sep 12, 2002 at 09:51:19AM -0600, Bob Proulx wrote: > You can list files that are available for recover with 'vi -r'. At > boot time or perhaps by cron this is being mailed to users. I tried this, and it didn't list any files. Thanks for suggesting RTFM, but I had done that and wrote th

Re: vi saved file message from root

2002-09-12 Thread Bob Proulx
> >saved for recovery. You can recover most, if not all, of the > >changes to this file using the -r option to vi: > > > > vi -r /tmp/vi.7faEP4 Richard Otte <[EMAIL PROTECTED]> [2002-09-11 21:23:12 -0700]: > For almost a year a person with an account on my machine has been > getting email fro

Re: vi cmd / replacing a certain line only.. pls help!! urgent..

2002-02-04 Thread Steve Mayer
Louie, Try :50,100s/Jan 2/Jan 1/g Steve On Tue, Feb 05, 2002 at 04:08:05AM +0800, louie miranda wrote: > How to replace a certain line on vi, > > ex: > > line 1 up to line 100 > > i want to replace only line 50 to 100 > how will i do that in vi? > > i did do, > > :%s:50,100/Jan 2/Jan 1/

Re: vi cmd / replacing a certain line only.. pls help!! urgent..

2002-02-04 Thread louie miranda
ah, its ok i've done it.. thnx :) louie miranda (axis0.ath.cx) -- Security Is A Series Of Well-Defined Steps chmod -R 0 / ; and smile :) - Original Message - From: "louie miranda" <[EMAIL PROTECTED]> To: Sent: Tuesday, February 05, 20

Re: vi vs ae

2002-01-15 Thread Caleb Shay
Tom Allison wrote: > Thanks! > I never knew that. > > Where the heck do you find out about all this weird stuff? man -k is your friend.

Re: vi vs ae

2002-01-15 Thread Keith Willoughby
Pietro Cagnoni <[EMAIL PROTECTED]> writes: > type as root: > > update-alternatives --config editor > > man update-alternatives will tell you a lot of the history. Speaking of which, can anyone tell me if it is a reportable bug if a package doesn't support the update-alternatives mechanism on in

  1   2   3   >