Re: vi as a text editor
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 doesn't have any color support on it. | | right, that's exactly my problem. so you too are saying it should be | dtterm? or xtermc? nothing i export my TERM to seems to make any | difference at all. You need to find out which terminal type is recorded as supporting color in the system's termcap/terminfo database. On the Solaris 8 systems at school I discovered that 'dtterm' fit that description. Apart from searching through the database to find one, or hoping you stumble across it by accident, the only other option is for the sys admin to add the proper entry to the termcap. The entry can be obtained from any other UNIX system (eg debian). -D -- The Consultant's Curse: When the customer has beaten upon you long enough, give him what he asks for, instead of what he needs. This is very strong medicine, and is normally only required once. http://dman.ddts.net/~dman/ msg14474/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 the Suns i work on ... exporting TERM=dtterm doesn't > | seem to do much, either. do i need to rewrite my syntax highlighting > | configuration files, or something? any tips on this would be greatly > | appreciated! > > If you use a dark (black) background in your terminal like I do, then > put > set bg=dark > syn on > in your .vimrc. Then vim will use lighter colors for the > highlighting. If you want gvim's gui to match, add > hi Normal guibg=black guifg=white > before the 'syn on' line. > > 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 doesn't have any color support on it. right, that's exactly my problem. so you too are saying it should be dtterm? or xtermc? nothing i export my TERM to seems to make any difference at all. -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ msg14277/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 curses library. unfortunately, i'm not a sysadmin on this system ... -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ msg14276/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 i need to rewrite my syntax highlighting | configuration files, or something? any tips on this would be greatly | appreciated! If you use a dark (black) background in your terminal like I do, then put set bg=dark syn on in your .vimrc. Then vim will use lighter colors for the highlighting. If you want gvim's gui to match, add hi Normal guibg=black guifg=white before the 'syn on' line. 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 doesn't have any color support on it. HTH, -D -- Come to me, all you who are weary and burdened, and I will give you rest. Take my yoke upon you and learn from me, for I am gentle and humble in heart, and you will find rest for your souls. For my yoke is easy and my burden is light. Matthew 11:28-30 http://dman.ddts.net/~dman/ msg14260/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 syntax highlighting. Does anyone know how to fix > > | that? :) > > > > export TERM=dtterm > > > > The termcap on Solaris is a bit braindead since xterm and friends > > entries lack color support. I did manage to discover, at one point, > > that the dtterm (their CDE terminal emulator) entry has color > > support and is compatible with xterm. > > 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 i need to rewrite my syntax highlighting > configuration files, or something? any tips on this would be greatly > appreciated! This works for me in .bashrc on solaris 8: if [ `uname` = "SunOS" ]; then export TERM=xtermc fi I compiled vim with ncurses5, not the sun curses library. > > > > -- > .~. nori @ sccs.swarthmore.edu > /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ >// \\ @ maenad.net > /( )\ www.maenad.net >^`~'^ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 TERM=dtterm > > The termcap on Solaris is a bit braindead since xterm and friends > entries lack color support. I did manage to discover, at one point, > that the dtterm (their CDE terminal emulator) entry has color > support and is compatible with xterm. 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 i need to rewrite my syntax highlighting configuration files, or something? any tips on this would be greatly appreciated! -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ msg13522/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 hefty for such a task unless you're a hardcore emacs > use that never leaves the editor. I know you can set up mutt to use it > in some sort of daemon(?) mode to reduce invocation time, but I also > have less time than I did back when I first learned vim (and a lot more > mail) :) If you tell mutt to use 'dtemacs' as your editor, then it'll start a new emacs window inside an existing process if there is one, or else start a new one. That said, I still prefer vim for my mail editing, since it loads instantly and I don't need to move away from my Eterm. -rob msg13437/pgp0.pgp Description: PGP signature
Re: vi as a text editor
* 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 at the moment. :%!ispell -a good times, Vineet -- http://www.doorstop.net/ -- http://www.eff.org/ msg13426/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 looking for [space][dash][dash] beginning in the first column, when it's supposed to be [dash][dash][space], though I've noticed many people are omitting the [space]. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 line. as i type, towards the end > of the line, it juts cuts the word. it neither hyphanates nor pushes > it to the next line. is there way i could make vi do this? See below. > moreover, can i have macros? doing the same repetitive thing? i will > also like to bind them to key strokes. You want the 'map' command. Be aware that it actually maps key codes from your .vimrc to commands, you'll need to actually enter the '^V' character to bind anything to it. > moreover, i have spell, ispell and aspell installed. is there a way i > can use them while in vi? Like a lot of people, I use mutt+vim. Here's some neat stuff I've collected from various places and now lives in my ~/.vimrc: set nocompatible" Use Vim defaults (much better!) set backspace=indent,eol,start augroup Mail au! " Wrap at 72 characters. au FileType mail set textwidth=72 au FileType mail set autoindent au FileType mail set formatoptions=tcrq2n au FileType mail set comments+=n:\| au FileType mail set nomodeline "remove .sig from messages I am replying to au BufRead /tmp/mutt* normal :g/^| -- $/,/^$/-1dgg augroup END nmap J gqap map :set pasteI " Use newsbody to spell check mail and such map ^T \1\2:e! % map \1 :w! map \2 :!newsbody -qs -n % -p aspell check \%f Using these settings, vim should automatically wrap at 72 columns (leaving room for a few levels of quoting). I got that line about removing the .sig from someone on here, but it doesn't actually seem to work... Hit 'J' in command mode to reformat the current paragraph; F11 to go to paste mode (useful for pasting things in X, so vim won't mess up the indentation) and ctrl-t to spell check your message. You'll need to install spellutils for that to work tho. Even if you don't use the rest, please, please, please set your editor to wrap your lines at some sane length. Long lines make your mail much, much harder to read. -rob msg13409/pgp0.pgp Description: PGP signature
Re: vi as a text editor
-- 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 towards end of line. as i type, towards the end > > of the line, it juts cuts the word. it neither hyphanates nor pushes > > it to the next line. is there way i could make vi do this? > > > > moreover, can i have macros? doing the same repetitive thing? i will > > also like to bind them to key strokes. > > > > moreover, i have spell, ispell and aspell installed. is there a way i > > can use them while in vi? > > > > Try `dpkg -L vim`. There are a ton of example macros, keymappings, etc > that come with the package. There is also a walktrhough to teach you > the basics of using vim. exec 'vimtutor' for a vim tutorial (it's part of the vim package). I've used both vi and vim, and find vim is fantastic for all my editing needs (from simple configuration file changes to coding in perl to mail to news to...). And it doesn't slow down my 366Mhz (primary machine), 166Mhz (laptop), or 1.7GHz machines one bit :-) . And if you're serious about learning vim, pick up a copy of Steve Oualline's "Vi IMproved -- VIM" book; worth it's weight in gold, if not more. -- Matthew Weier O'Phinney [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 use vim - you don't find it on every Unix box, > just like emacs. I agree that learning to use plain old vi is definitely a good thing. I started out using just vim. One of my later classes required work be done exclusively on Solaris, and using standard vi I felt more than a little crippled after becoming used to vim's niceties. 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 hefty for such a task unless you're a hardcore emacs use that never leaves the editor. I know you can set up mutt to use it in some sort of daemon(?) mode to reduce invocation time, but I also have less time than I did back when I first learned vim (and a lot more mail) :) Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 map like I have in vim that isn't true (FYI). " Make the up and down movements move by "display" lines: map j gj map k gk -D -- There are 10 types of people in the world: those who understand binary, and those who do not. http://dman.ddts.net/~dman/ msg13369/pgp0.pgp Description: PGP signature
Re: vi as a text editor
"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 >> hyphanates nor pushes it to the next line. is there way i >> could make vi do this? >> With (n)vi you can say ":set wrapmargin=8" to cause wrapping around 8 characters before the end of the line. lynx /usr/share/doc/nvi would be good reading for you. There are also two tutorial files there, unzip them and read them in vi. Osamu> Highlight with "V" and cursor move and "gq" does the trick. Osamu> Wrap around can be done by ":set tw=72". Osamu> Most people use VIM instead of VI to be sane. Try it. I can't resist giving another opinon: when I want vi, I use vi (or, more precisely, nvi on Debian systems). When I *need* vim, I simply use emacs :-) (followups to this should probably be to alt.religon.emacs or something like that). 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 use vim - you don't find it on every Unix box, just like emacs. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 to use vim instead. The reason for that is vim has many more (useful!) features than 'vi' (copyrighted by Bill Joy and found only on Solaris sytems) or the other free clones (elvis and nvi). | Ah, sorry - I use vim quite a bit I always use vim :-). | vim is a little over-featured, but some of those features are very nice. | :) The syntax highlighting (in mail as well as code) is something I'm | loath to do without. Indeed! | As an aside, I primarily use standard vi on Solaris, I feel your pain ;-). | since Solaris never seems to understand my remote terminal well | enough to allow syntax highlighting. Does anyone know how to fix | that? :) export TERM=dtterm The termcap on Solaris is a bit braindead since xterm and friends entries lack color support. I did manage to discover, at one point, that the dtterm (their CDE terminal emulator) entry has color support and is compatible with xterm. -D -- The way of a fool seems right to him, but a wise man listens to advice. Proverbs 12:15 http://dman.ddts.net/~dman/ msg13366/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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. it neither hyphanates nor pushes > it to the next line. is there way i could make vi do this? > > moreover, can i have macros? doing the same repetitive thing? i will > also like to bind them to key strokes. > > moreover, i have spell, ispell and aspell installed. is there a way i > can use them while in vi? > > thanx, > > sandip p deshmukh --*** > > statistics, n.: A system for expressing your political prejudices in > convincing scientific guise. Try `dpkg -L vim`. There are a ton of example macros, keymappings, etc that come with the package. There is also a walktrhough to teach you the basics of using vim. -- -- |Stephen Gran | In the long run, every program becomes| |[EMAIL PROTECTED] | rococco, and then rubble. -- Alan Perlis| |http://www.lobefin.net/~steve | | | | | -- msg13337/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 end > > > of the line, it juts cuts the word. it neither hyphanates nor pushes > > > it to the next line. is there way i could make vi do this? > > > > I believe this one's already been answered. > > no. someone asked me to use vim instead. i think that is what i am using > right now! you know, it takes up 12mb space. i would love to eliminate > it at the earliest! so tell me please. a few keystrokes and 12mb space!! > ;) Ah, sorry - I use vim quite a bit and fooled myself into thinking tw was a standard vi setting. Actually, standard vi word wrap is the reverse. Instead of textwidth, it's wrapmargin: :set wm=8 is equivalent to :set tw=72 in vim. vim is a little over-featured, but some of those features are very nice. :) The syntax highlighting (in mail as well as code) is something I'm loath to do without. As an aside, I primarily use standard vi on Solaris, since Solaris never seems to understand my remote terminal well enough to allow syntax highlighting. Does anyone know how to fix that? :) Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 > > it to the next line. is there way i could make vi do this? > > I believe this one's already been answered. no. someone asked me to use vim instead. i think that is what i am using right now! you know, it takes up 12mb space. i would love to eliminate it at the earliest! so tell me please. a few keystrokes and 12mb space!! ;) regards, sandip p deshmukh --*** Footnotes are for things you believe don't really belong in LDP manuals, but want to include anyway. -- Joel N. Weber II discussing the 'make' chapter of LPG msg13282/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 *does* go into command mode. That might be obvious, but I thought I would clarify. Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 cuts the word. it neither hyphanates nor pushes > it to the next line. is there way i could make vi do this? I believe this one's already been answered. > moreover, can i have macros? doing the same repetitive thing? i will > also like to bind them to key strokes. Yes. In command mode type: :map To type control characters, just hit Control-V before typing them. The above will create a macro to be used while in command mode. To make a macro that works in insert mode just use :map! instead :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 command mode. The only drawback to insert macros is a slight delay whenever you type the first character of the macro. To just type the word, just wait a second or two after typing the 'l'. > 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 at the moment. HTH, Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 > > the line, it juts cuts the word. it neither hyphanates nor pushes it to > > the next line. is there way i could make vi do this? > > I am not certain what your referring to, but it sounds like vi is just > making the line longer, it may *appear* it is going to the next line > but chances are good that its the same line. 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. you are right. it is one line. but on screen it appears to be several lines. anyway, any solution? thanx anyway sandip p deshmukh --*** Finagle's Eighth Law: If an experiment works, something has gone wrong. Finagle's Ninth Law: No matter what results are expected, someone is always willing to fake it. Finagle's Tenth Law: No matter what the result someone is always eager to misinterpret it. Finagle's Eleventh Law: No matter what occurs, someone believes it happened according to his pet theory. msg13274/pgp0.pgp Description: PGP signature
Re: vi as a text editor
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 it to > the next line. is there way i could make vi do this? I am not certain what your referring to, but it sounds like vi is just making the line longer, it may *appear* it is going to the next line but chances are good that its the same line. 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. > moreover, can i have macros? doing the same repetitive thing? i will also > like to bind them to key strokes. probably, even though i've been using vi since 1995 I still barely know more then the real basics(and I use it everyday). > moreover, i have spell, ispell and aspell installed. is there a way i can > use them while in vi? probably..no idea how :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi as a text editor
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 cuts the word. it neither hyphanates nor pushes > it to the next line. is there way i could make vi do this? > > moreover, can i have macros? doing the same repetitive thing? i will > also like to bind them to key strokes. > > moreover, i have spell, ispell and aspell installed. is there a way i > can use them while in vi? > > thanx, > > sandip p deshmukh > --*** Hey, did you see how I reformatted your posting! I use VIM. Highlight with "V" and cursor move and "gq" does the trick. Wrap around can be done by ":set tw=72". Most people use VIM instead of VI to be sane. Try it. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32 .''`. Debian Reference: post-installation user's guide for non-developers : :' : http://qref.sf.net and http://people.debian.org/~osamu `. `' "Our Priorities are Our Users and Free Software" --- Social Contract -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
vi as a text editor
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 it to the next line. is there way i could make vi do this? moreover, can i have macros? doing the same repetitive thing? i will also like to bind them to key strokes. moreover, i have spell, ispell and aspell installed. is there a way i can use them while in vi? thanx, sandip p deshmukh --*** statistics, n.: A system for expressing your political prejudices in convincing scientific guise. msg13268/pgp0.pgp Description: PGP signature
