[PATCH] documentation fixes

Hi Bram, Find attached a patch that corrects the following in the docs - - Tidy up the use of Tab, Tab, tab etc - Fix the highlighting for the title of getwinposx() in eval.txt. There is a missing '' at the start of the previous line to terminate the previous highlighting. - One or two

[SOLVED] RE: 7.1a.001 OSX colour scheme errors?

Hm... Maybe the console version checks the values of the guibg= guifg= settings even though it doesn't use them. Try dropping the attached file into your $VIMRUNTIME folder and see if it makes any difference. (See :help rgb.txt for an explanation of how Vim uses it. IIUC, on X11- and

RE: [SOLVED] RE: 7.1a.001 OSX colour scheme errors?

Michael Wookey wrote: Hm... Maybe the console version checks the values of the guibg= guifg= settings even though it doesn't use them. Try dropping the attached file into your $VIMRUNTIME folder and see if it makes any difference. (See :help rgb.txt for an explanation of how Vim uses

RE: 7.1a.001 OSX colour scheme errors?

Has anyone else noticed this? You apparently are missing the runtime/rgb.txt file. It's part of the extra archive. Perhaps you didn't unpack it correctly? You must have unpacked it, since it contains src/gui_mac.c. And you must not change the directory structure, otherwise Vim.app

7.1a.001 OSX colour scheme errors?

Hello vimmers, I am running 7.1a.001 on OSX and have just noticed the following from console vim (running in Terminal.app and also occurs in iTerm.app). If I change the colour scheme I receive a lot of error output. For example: :colorscheme desert Results in: Error detected while

RE: 7.1a.001 OSX colour scheme errors?

A.J.Mechelynck wrote: Michael Wookey wrote: Hello vimmers, I am running 7.1a.001 on OSX and have just noticed the following from console vim (running in Terminal.app and also occurs in iTerm.app). If I change the colour scheme I receive a lot of error output. For example

RE: problem with win32 vim 7.1a.001

Any ideas? Maybe you can rename all your directories named Vim70 to Vim71a. Yep - that was it. C:\Vim\vim70 was renamed to C:\Vim\vim71a and all is well. Thanks! (and also thanks to Tony for the troubleshooting hints)

[PATCH] minor doc patch

Hi Bram, Find attached a patch that properly brackets the use of Enter in the docs. cheers vimdoc-enter-brackets.patch Description: vimdoc-enter-brackets.patch

problem with win32 vim 7.1a.001

Hello vim list, I've just synced up to 7.1a.001 (svn #263) and built on Win32 (MSVC). Everything builds fine and I replace my previous gvim.exe and vim.exe with the newly built versions. I also sync my runtime from ftp.nluug.nl. My vim installation is in: C:\Vim\vim70 My config is in:

RE: completion menu colors

Is there a way to change the completion menu colors? See: :help hl-Pmenu :help hl-PmenuSel :help hl-Pmenu-Sbar :help hl-PmenuThumb For example: :highlight Pmenu guibg=DarkRed cheers

RE: autocmd bug?

I have the following in my .vimrc: filetype plugin indent on autocmd FileType c,h,cpp,hpp,cs setlocal cindent number cursorline If I have a new buffer and set the filetype as follows, everything works just fine: :set filetype=c However, if I have a new buffer

[PATCH] minor doc update

Attached is a small patch to update the information for 'listchars' in options.txt. There was no linkage to the highlight groups that listchars uses. cheers options_listchars.patch Description: options_listchars.patch

RE: [PATCH] minor doc update

Michael Wookey wrote: Attached is a small patch to update the information for 'listchars' in options.txt. There was no linkage to the highlight groups that listchars uses. cheers Are you sure you diffed against the latest version of the file? In the version I have

RE: [PATCH] minor doc update

OTOH, the svn repository is known to lag behind the other repositories, sometimes by a week or more: diffing against it runs the risk of forking the code. IIUC, the latest on nluug.nl is also the latest official version at any point in time. You can compare the first line of the version you

RE: command to indent file

In the path I often used command to indent my php file or C# file: gg ... G mean go to the top of file and indent code until the end of file. But Unfortunately I forgot. Could anyone tell me what I forgot? :help = For example: gg=G

RE: Using right ctags file depending where Vim is started from - how?

Hi all! I am trying to automate my Vim setup as much as possible. On my PC I have 2 directories for 2 different releases. C:\Code_Rel1 C:\Code_Rel2 At a very top level in each of these directories I have ctags files. How can I setup Vim so that it sources right ctags file depending

[PATCH] minor doc typos

Attached is a small patch that fixes some minor typos in the docs. Specifically to ensure that uses of 'mousemodel' and 'wildchar' were fully quoted so that they can be jumped from. cheers vimdoc.patch Description: vimdoc.patch

RE: Win64-related patches

Hi Bram, Michael Wookey wrote: One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim - register', and watch it crash while trying to display an error message. This seems to fix the bug... Index: src/message.c

RE: Win64-related patches

Hi Bram, Michael Wookey wrote: One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim - register', and watch it crash while trying to display an error message. This seems to fix the bug... Index: src/message.c

[PATCH] minor typo in tutor

Index: runtime/tutor/tutor === --- runtime/tutor/tutor (revision 218) +++ runtime/tutor/tutor (working copy) @@ -568,10 +568,10 @@ 4. To change every occurrence of a character string between two lines, type

RE: [PATCH] minor typo in tutor

Hmm.. apologies if my mail client messed that up. Find the patch attached. cheers tutor.patch Description: tutor.patch

RE: The Seven Habits Of Effective Text Editing 2

cRaig - On 2/19/07, Bram Moolenaar [EMAIL PROTECTED] wrote: ... I'll ask if I can get the video in a portable format and put it on the Vim ftp server. If you choose Download from a Linux workstation, you can save the video as an AVI file. The presentation is approx. 500 MB

RE: Win64-related patches

Michael Wookey wrote: One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim - register', and watch it crash while trying to display an error message. This seems to fix the bug... Index: src/message.c

RE: how to read the file created in PC in Linux correctly?

I have a lot of text files created in PC. When I open them in Linux using gvim, I get a lot of ^M and no line breaking. It is messy. How can I read the file correctly in Linux? There is a good discussion of this topic here: http://www.vim.org/tips/tip.php?tip_id=26 cheers

RE: Win64-related patches

One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim -register', and watch it crash while trying to display an error message. This seems to fix the bug... Index: src/message.c === --- src/message.c (revision 212)