Re: VIM questions
Steve Lamb hat gesagt: // Steve Lamb wrote:
On Sat, May 15, 1999 at 03:15:05PM +0100, Dave Swegen wrote:
1) For some reason vim inists on showing file stats at the bottom of the
screen whenever I edit a file. It isn't too bad normally, but when I
invoked from mutt it waits for me to press a key. Very annoying. How do I
get rid of that behaviour?
I'd love to know how to shut that thing off as well. Completely unneeded
and annoying as all hell.
One solution is hidden in the VIM-docs. See options.txt.
*'shortmess'* *'shm'*
'shortmess' 'shm' string (default )
global
{not in Vi}
This option helps to avoid all the |hit-return| prompts caused by file
messages, for example with CTRL-G, and to avoid some other messages.
It is a list of flags:
flag meaning when present~
f use (3 of 5) instead of (file 3 of 5)
[plus more flags...]
This gives you the opportunity to avoid that a change between buffers
requires you to hit return, but still gives as useful a message as
possible for the space available. To get the whole message that you
would have got with 'shm' empty, use :file!
Useful values:
shm=No abbreviation of message.
shm=a Abbreviation, but no loss of information.
shm=at Abbreviation, and truncate message when necessary.
Plus you will want to read message.txt's explanation of |hit-retrun|
messages:
*hit-return*
Press RETURN or enter command to continue
This message is given when there is something on the screen for you to read,
and the screen is about to be redrawn:
- After executing an external command (e.g., :!ls and =).
- Something is displayed on the status line that is longer than the width of
the window, or runs into the 'showcmd' or 'ruler' output.
To reduce the number of hit-return prompts:
- Set 'cmdheight' to 2 or higher.
- Add flags to 'shortmess'.
- Reset 'showcmd' and/or 'ruler'.
--
____
Frank Barknecht __ __ trip\ \ / /wire __
/ __// __ /__/ __// // __ \ \/ / __ \\ ___\
/ / / / / / / // // /\ \\ ___\\ \
/_/ /_/ /_/ /_//_// / \ \\_\\_\
/_/\_\
Re: VIM questions
On Sat, May 15, 1999 at 03:15:05PM +0100, Dave Swegen wrote: 1) For some reason vim inists on showing file stats at the bottom of the screen whenever I edit a file. It isn't too bad normally, but when I invoked from mutt it waits for me to press a key. Very annoying. How do I get rid of that behaviour? I'd love to know how to shut that thing off as well. Completely unneeded and annoying as all hell. 2) How do I make use the dark background syntax settings? Set them up in a local directory and have the local directory override the global syntax directory. 3) In the long running debian coding standards debate on devel, it was mentioned that tabs shouldn't be used to indent, but spaces instead. How do I set up vim to insert n amount of spaces when I press the TAB key? Or is there some other key that is used for that purpose? Here's from my .vimrc set tabstop=2 set expandtab expandtab is the one that will automatically set tabs to spaces. -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your ICQ: 5107343 | main connection to the switchboard of souls. ---+-
Re: VIM questions
On Sat, May 15, 1999 at 21:06 -0700, Steve Lamb wrote: On Sat, May 15, 1999 at 03:15:05PM +0100, Dave Swegen wrote: 1) For some reason vim inists on showing file stats at the bottom of the screen whenever I edit a file. It isn't too bad normally, but when I invoked from mutt it waits for me to press a key. Very annoying. How do I get rid of that behaviour? I'd love to know how to shut that thing off as well. Completely unneeded and annoying as all hell. Just figured it out: the culprit is the ruler option. Turn it off and the evil goes away...Bummer, really, as the ruler is slightly useful... 2) How do I make use the dark background syntax settings? Set them up in a local directory and have the local directory override the global syntax directory. OK, I feel a bit dumb, but how do I do that? 3) In the long running debian coding standards debate on devel, it was mentioned that tabs shouldn't be used to indent, but spaces instead. How do I set up vim to insert n amount of spaces when I press the TAB key? Or is there some other key that is used for that purpose? Here's from my .vimrc set tabstop=2 set expandtab expandtab is the one that will automatically set tabs to spaces. Great! Just what I was looking for... Cheers Dave -- Dave Swegen | Debian 2.1 on Linux i386 2.2.3 [EMAIL PROTECTED] | PGP key available on request [EMAIL PROTECTED] | Linux: The Choice of a GNU Generation --
Re: VIM questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 16 May 1999 14:29:08 +0100, Dave Swegen wrote: Just figured it out: the culprit is the ruler option. Turn it off and the evil goes away...Bummer, really, as the ruler is slightly useful... Bugger. 2) How do I make use the dark background syntax settings? Set them up in a local directory and have the local directory override the global syntax directory. OK, I feel a bit dumb, but how do I do that? Uhm, not sure. Go to the VIM home page and follow the links to the Windows version. I know, Windows, boo. But the guy has an example of how to do it on his web page. :) Great! Just what I was looking for... You're welcome. - -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your ICQ: 5107343 | main connection to the switchboard of souls. - ---+- -BEGIN PGP SIGNATURE- Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc iQA/AwUBNz7LQXpf7K2LbpnFEQJE6ACfSvGqpwicQLlsg9tJDSF95krmcPIAnj4d P9QhmtKq+/pHRZ+OgxY9yCwF =ZEra -END PGP SIGNATURE-
VIM questions
I have a few questions regarding VIM that have been nagging at me for a while, and I'm hoping someone can help me out... 1) For some reason vim inists on showing file stats at the bottom of the screen whenever I edit a file. It isn't too bad normally, but when I invoked from mutt it waits for me to press a key. Very annoying. How do I get rid of that behaviour? 2) How do I make use the dark background syntax settings? I've set background to dark, but it makes no difference - it still inists on using such groovy combinations as dark blue on black. In the past I have edited /usr/syntax/vim directly, commenting out the dark settings, and changing the colours in the light scheme more to my liking. However, it tends to get hosed every time I upgrade vim, which is a PITA. How do I set up vim to use my personal colour settings? (FWIW I think the doc system on vim is awful - the one thing I really don't like about it) 3) In the long running debian coding standards debate on devel, it was mentioned that tabs shouldn't be used to indent, but spaces instead. How do I set up vim to insert n amount of spaces when I press the TAB key? Or is there some other key that is used for that purpose? Any illumination will be much appreciated Cheers Dave -- Dave Swegen | Debian 2.1 on Linux i386 2.2.3 [EMAIL PROTECTED] | PGP key available on request [EMAIL PROTECTED] | Linux: The Choice of a GNU Generation --
Re: VIM questions
I have a few questions regarding VIM that have been nagging at me for a while, and I'm hoping someone can help me out... 1) For some reason vim inists on showing file stats at the bottom of the screen whenever I edit a file. It isn't too bad normally, but when I invoked from mutt it waits for me to press a key. Very annoying. How do I get rid of that behaviour? Never seen this behaviour. 2) How do I make use the dark background syntax settings? I've set background to dark, but it makes no difference - it still inists on using such groovy combinations as dark blue on black. In the past I have edited /usr/syntax/vim directly, commenting out the dark settings, and changing the colours in the light scheme more to my liking. However, it tends to get hosed every time I upgrade vim, which is a PITA. How do I set up vim to use my personal colour settings? (FWIW I think the doc system on vim is awful - the one thing I really don't like about it) Make a ~ entry for vim rather than using the global settings. 3) In the long running debian coding standards debate on devel, it was mentioned that tabs shouldn't be used to indent, but spaces instead. How do I set up vim to insert n amount of spaces when I press the TAB key? Or is there some other key that is used for that purpose? I disagree w/ using spaces, tabs are nice and allow each user to set their own tab space (i like 4, you like 3 so we each set our tabset appropriately and never have to edit the code)
Re: VIM questions
On Sat, May 15, 1999 at 10:45:48AM -0400, [EMAIL PROTECTED] wrote: 3) In the long running debian coding standards debate on devel, it was mentioned that tabs shouldn't be used to indent, but spaces instead. How do I set up vim to insert n amount of spaces when I press the TAB key? Or is there some other key that is used for that purpose? I disagree w/ using spaces, tabs are nice and allow each user to set their own tab space (i like 4, you like 3 so we each set our tabset appropriately and never have to edit the code) Or, if you disagree with that sentiment, you can execute expand --tabs x filetoexpand someotherfile ; mv someotherfile filetoexpand DON'T expand a file and redirect the output to itself...you will lose the file (learned this the hard way...makes perfect sense in retrospect :) - flip - [EMAIL PROTECTED]/[EMAIL PROTECTED] -- You can only be a child once, but you can be immature forever -- unknown
VIM questions
1) Will there ever be a debian version of Vim which supports -g under X, or will I have to compile my own? 2) How can I get my keys mapped properly? I want del to delete the character under the cursor, bs to delete the previous character, home to move to the beginning of the line, end to move to the end of the line, pg up to go up a page, pg dn to go down a page, etc... where do I start? I would like behavior both in console mode and in an xterm. Thanks, Chris. === Chris R. Martin email: [EMAIL PROTECTED] PGP key upon request www: http://http.tamu.edu:8000/~crm7479 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: VIM questions
Chris R. Martin [EMAIL PROTECTED] wrote: 1) Will there ever be a debian version of Vim which supports -g under X, or will I have to compile my own? 4.5-4, in bo. (This has been the cause of a couple of bug reports from people who believe there should be a separate version without X support. This ain't policy, folks. Sorry...) 2) How can I get my keys mapped properly? I want del to delete the character under the cursor, bs to delete the previous character, home to move to the beginning of the line, end to move to the end of the line, pg up to go up a page, pg dn to go down a page, etc... where do I start? I would like behavior both in console mode and in an xterm. I'm not too sure about this. I'm such a diehard vi user, I use the standard vi commands for these :-) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
