Re: Patch: gvimext.dll don't find MSVCR80.dll when built with VC8. No context menu entries.
Mathias Michaelis wrote: Patch 7.0.Make_GvimExt Problem:On Windows, when GvimExt is built with Microsoft Visual Studio 2005, the context menu item Edit with vim doesn't appear in Explorer. Reason: GvimExt.dll cannot be loaded, because it is not prepared to the Windows Side by Side Components subsystem and so cannot find the C Runtime library in MSVCR80.dll. Solution: A manifest file is created by the linker. Embed it into the resources of GvimExt.dll. Files: src/GvimExt/Makefile I'm glad you managed to find a fix for this. I don't have this compiler. Can someone with MSVC 2005 verify this works properly? Is this the whole solution or does something else need to be changed? -- FIRST HEAD: All right! All right! We'll kill him first and then have tea and biscuits. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Redraw bug on WinXP with non-GUI tab line.
Ilya Bobir wrote: I've found bug in vim version VIM - Vi IMproved 7.0 (2006 May 7, compiled May 25 2006 04:17:33) MS-Windows 32 bit GUI version with OLE support Included patches: 1-17 In case incremental search is on, tab line some times is not visible. Steps to reproduce: gvim -u NONE -U NONE :e 1.txt :set is :tab sp /s after hitting 's' text is scrolled to a line containing 'six1' and tabline is empty - cleared with background color. I see the problem. I'll put it in the todo list. -- GALAHAD turns back. We see from his POV the lovely ZOOT standing by him smiling enchantingly and a number of equally delectable GIRLIES draped around in the seductively poulticed room. They look at him smilingly and wave. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Patch: Make_mvc.mak creates an empty gvim.exe.mnf file
Mathias Michaelis wrote: Patch Problem:Make_mvc.mak creates an empty gvim.exe.mnf file (or stops with an error message). (Suresh Govindachar) Solution: Don't use 'echo' to create files. Use inline files instead. Files: src/Make_mvc.mak This has always worked just fine. When does it fail? -- Microsoft's definition of a boolean: TRUE, FALSE, MAYBE Embrace and extend...? /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Runtime error in explorer.exe when right clicking with vim70f gvimext.dll installed
Mathias Michaelis wrote: first of all: THANKS! This issue is explained in MSDN in section about SxS - Side by Side Components. I've attached patch against current GvimExt/gvimext.rc that would make resource compiler add manifest inside generated DLL - this is what is required to make it run on WinXP SP2 and Win2k3. I first tried your patch, but then the resource compiler complained he couldn't find a file named winres.h. I then restored the original files, applied the following patch to your patch, and then applied your patch again. This was a full success! The dll now worked! The patch that I had to apply to your patch was: Change the names winres.h -- winresrc.h: [...] I have seen a few messages on the subject. Can someone merge everything and send me a patch for the final solution? I don't have this compiler thus I can't try it out myself. -- ZOOT: I'm afraid our life must seem very dull and quiet compared to yours. We are but eightscore young blondes, all between sixteen and nineteen-and-a-half, cut off in this castle, with no one to protect us. Oooh. It is a lonely life ... bathing ... dressing ... undressing ... making exciting underwear Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: [patch] Mods needed to successfully compile on OS/2 with gcc 3.2.1
David - Thanks for the patches. I'll include them. - Bram -- Back up my hard drive? I can't find the reverse switch! /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
svn, cvs
Hello, Since svn sources haven't been updated, and since they differs from the cvs sources by CR/LF in some files, I tried cvs. However: The following: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim checkout vim7 resulted in: cvs [checkout aborted]: connect to cvs.sf.net(66.35.250.207):2401 failed: No route to host And the following: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:80/cvsroot/vim checkout vim7 resulted in: cvs [checkout aborted]: connect to cvs-pserver.sf.net(66.35.250.213):80 failed: Connection reset by peer Am I doing something wrong, or is cvs just down? Thanks, --Suresh
Re: svn, cvs
* Suresh Govindachar sgovindachar@ [060618 01:27]: Am I doing something wrong, or is cvs just down? CVS access has been changed some time ago. Use :pserver:[EMAIL PROTECTED]:/cvsroot/vim as cvsroot. -- Regards, Sir Raorn. signature.asc Description: Digital signature
RE: svn, cvs
Based on Sir Raorn's reply, I tried: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim checkout vim7 which did lots of stuff and ended with: U vim7/src/xxd/xxd.c cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected Repeating the command resulted in the same message: cvs checkout: Updating vim7/src/xxd cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected Doing only update as follows: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim update resulted in the same message: cvs update: Updating vim7/src/xxd cvs update: dying gasps from vim.cvs.sourceforge.net unexpected Is this normal? If not, what should I do? Thanks, --Suresh
RE: svn, cvs
A.J.Mechelynck wrote: Suresh Govindachar wrote: Based on Sir Raorn's reply, I tried: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim checkout vim7 which did lots of stuff and ended with: U vim7/src/xxd/xxd.c cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected Repeating the command resulted in the same message: cvs checkout: Updating vim7/src/xxd cvs checkout: dying gasps from vim.cvs.sourceforge.net unexpected Doing only update as follows: C:\home\suresh\develop\vim\cvsc:\opt\cvs\cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/vim update resulted in the same message: cvs update: Updating vim7/src/xxd cvs update: dying gasps from vim.cvs.sourceforge.net unexpected Is this normal? If not, what should I do? If CVS is sick, That's my question -- does that message mean cvs is sick or is that message a normal termination message from cvs? you can always fall back on good old FTP (or even HTTP): The reason for fetching from cvs is to avoid having to patch. (and the reason for not using svn is that svn is out-of-date, and svn differes from Bram's cvs by CR/LF in some files). --Suresh
Re: svn, cvs
Suresh Govindachar wrote: The reason for fetching from cvs is to avoid having to patch. (and the reason for not using svn is that svn is out-of-date, and svn differes from Bram's cvs by CR/LF in some files). There were concerns about switching over to Subversion when we first started using it a few months ago, just before Vim 7.0 released. Are those concerns still valid? -- /George V. Reilly [EMAIL PROTECTED] http://www.georgevreilly.com/blog
filename completion ignorecase for Vim 7
Hi all, For Vim 7, it seems that filename completion in the :cmdline ignores case when searching for matches. For example, :e FTab matches both foo.txt Foo.txt This is different from Vim 6 where it only matches Foo.txt Is there any way to revert back to the old behavior? -- Gerald
Re: filename completion ignorecase for Vim 7
try :noic On Sat, Jun 17, 2006 at 02:32:46AM -0700, Gerald Lai wrote: Hi all, For Vim 7, it seems that filename completion in the :cmdline ignores case when searching for matches. For example, :e FTab matches both foo.txt Foo.txt This is different from Vim 6 where it only matches Foo.txt Is there any way to revert back to the old behavior? -- Gerald
Re: filename completion ignorecase for Vim 7
Gerald Lai wrote: For Vim 7, it seems that filename completion in the :cmdline ignores case when searching for matches. For example, :e FTab matches both foo.txt Foo.txt This is different from Vim 6 where it only matches Foo.txt Is there any way to revert back to the old behavior? What system? On MS-Windows case of filenames is ignored, on Unix it matters, on Mac it depends. -- He was not in the least bit scared to be mashed into a pulp Or to have his eyes gouged out and his elbows broken; To have his kneecaps split and his body burned away And his limbs all hacked and mangled, brave Sir Robin. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: filename completion ignorecase for Vim 7
On Sat, 17 Jun 2006, Bram Moolenaar wrote: Gerald Lai wrote: For Vim 7, it seems that filename completion in the :cmdline ignores case when searching for matches. For example, :e FTab matches both foo.txt Foo.txt This is different from Vim 6 where it only matches Foo.txt Is there any way to revert back to the old behavior? What system? On MS-Windows case of filenames is ignored, on Unix it matters, on Mac it depends. I'm on Windows for Vim 7, Linux for Vim 6 :) That explains it. I guess this is a matter of discrepancy between what the user wants to match, and what the OS cares to read. IMHO, what the user wants to match should take priority over whether the OS cares about the case of its filenames. Perhaps for Windows, we could have a 'smartcase' setup for filename completion matching where it's ignorecase only when all the characters are lowercase. Thanks. -- Gerald
Re: Bug with gU and German sharp s?
Hi, Am Freitag, 16. Jun 2006, 18:47:32 +0200 schrieb Christian Ebert: * Bram Moolenaar on Friday, June 16, 2006 at 17:24:20 +0200: I'll leave it up to language specialists to decide whether making straße uppercase should result in STRAßE or STRASSE. I thought it was STRASSE. Historic: STRASZE Now: STRASSE See: http://de.wikipedia.org/wiki/Versal-Eszett The TeX EC fonts (Cork or T1 encoding) indeed have an upper case ligature SS that is ONE letter. I'm not very lucky about that for the reasons mentioned in the Wikipedia article. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
synchronize current working directory - problem with vim7
Hi All I'm using the CD.vim script from: http://vim.sourceforge.net/scripts/script.php?script_id=65 to synchronize the current working directory with the current buffer. au BufEnter * execute :lcd . expand(%:p:h) On Vim7, when I browse directories (e.g :e c:\Projects)... the current working directory does not get updated. How do I fix this? Thanks in Advance! Sreeram signature.asc Description: OpenPGP digital signature
Re: synchronize current working directory - problem with vim7
Chris Sutcliffe wrote:
if exists('+autochdir')
set autochdir
else
autocmd BufEnter * silent! lcd %:p:h:gs/ /\\ /
endif
In my _vimrc and it's worked beautifully in both vim 6 and vim 7.
I just tried 'autochdir', and when i'm browsing a directory, it seems to
set the current working directory to the *parent* of the directory.\
For instance, if i'm browsing 'c:\projects\mypetproject\', the current
directory is being set to 'c:\projects', how do i make it so that the
current directory is set to 'c:\projects\mypetproject\'?
Thanks in advance!
Sreeram
signature.asc
Description: OpenPGP digital signature
Re: Segfault using errorformat and errorfile
Marc Weber wrote: Hi. I don't know much about errorformats in vim yet, I didn't manage to match these errors but I get a crash ;) It doesn't crash when removing the none error marker lines. Can you help me with finding a errorformat string ? Or should I write another parser to remove the other lines (grep, ..) ? Execute this command set errorformat=%f\\[%l\\,%c\\]%m and :cfile === I can reproduce it. I'll look into it. -- GALAHAD hurries to the door and pushes through it. As he leaves the room we CUT TO the reverse to show that he is now in a room full of bathing and romping GIRLIES, all innocent, wide-eyed and beautiful. They smile enchantingly at him as he tries to keep walking without being diverted by the lovely sights assaulting his eyeballs. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Tab autocommand inconsistencies?
Hari Krishna Dara wrote: I am observing what might be inconsistency in the order in which vim fires autocommands. First, ovserving the order of buffer and window events, - Using :new: WinLeave WinEnter BufLeave BufEnter - Using :wincmd w BufLeave WinLeave WinEnter BufEnter When combined with tab operations, - Using, :tabe: WinLeave TabLeave TabEnter WinEnter BufLeave BufEnter - Using :tabnext: BufLeave WinLeave TabLeave WinEnter TabEnter BufEnter Extrapolating the first two, I was expecting these to be - For tabe: TabLeave TabEnter WinLeave WinEnter BufLeave BufEnter - For :tabnext: BufLeave WinLeave TabLeave TabEnter WinEnter BufEnter Is the existing behavior expected? Does anyone agree that it is inconsistent? I am even surprised that they should differ between switching between the existing windows/tabs and creating new ones. The problem with autocommands is that they must run in a valid environment to avoid trouble (as in a crashing Vim). This is quite tricky, especially in combination with error handling (e.g., not being able to abandon a buffer). The order of autocommands changed at a late moment in 7.0 development to work around problems (no valid window when TabEnter was triggered, if I remember correctly). I rather not change it again, it might introduce bugs. -- DINGO: And after the spanking ... the oral sex. GALAHAD: Oh, dear! Well, I... GIRLS: The oral sex ... The oral sex. GALAHAD: Well, I suppose I could stay a BIT longer. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: synchronize current working directory - problem with vim7
Quoting K.S.Sreeram [EMAIL PROTECTED]:
Chris Sutcliffe wrote:
if exists('+autochdir')
set autochdir
else
autocmd BufEnter * silent! lcd %:p:h:gs/ /\\ /
endif
In my _vimrc and it's worked beautifully in both vim 6 and vim 7.
I just tried 'autochdir', and when i'm browsing a directory, it seems to
set the current working directory to the *parent* of the directory.\
For instance, if i'm browsing 'c:\projects\mypetproject\', the current
directory is being set to 'c:\projects', how do i make it so that the
current directory is set to 'c:\projects\mypetproject\'?
Assuming you're using netrw to do your browsing; look at
:he netrw-problems
In particular, look at P6.
Regards,
Chip Campbell
Re: synchronize current working directory - problem with vim7
[EMAIL PROTECTED] wrote: :he netrw-problems In particular, look at P6. Thanks for the pointer, but unfortunately doing let g:netrw_keepdir = 0 in _vimrc file does not seem to have any effect at all! Here's what happens: 1) run gvim.exe 2) :pwd (output: c:\Vim\vim70) 3) :e c:\Projects\Test\ (shows directory listing) 4) :pwd (output: c:\Vim\vim70) If I have 'set autochdir', then : 3) :e c:\Projects\Test (shows directory listing) 4) :pwd (output: c:\Projects) (I'd like this to be c:\Projects\Test!) So in either case, g:netrw_keepdir=0 doesn't have any effect at all, I even tried with a fresh install of vim7 without any extra plugins and the result was the same! How do I solve this? Thanks in advance! Sreeram signature.asc Description: OpenPGP digital signature
Re: Vim7 - intellisense problem
Dan Clarke wrote:
In my workplace, our coding standard states that we have to declare our
variables on the next line from the variable type. The intellisense in
vim7 doesn't work when it's like this.
For example ...
typedef struct
{
int
i;
}my_structure;
void main (void)
{
my_structure
var1;
my_structure var2;
var1. this doesn't work
var2. this does work
}
I guess we're not the only place that declares variables over multiple
lines.
Any way I can get around this? Would be really nice to get intellisense
working for our projects.
This would require adjusting $VIMRUNTIME/autoload/ccomplete.vim to look
one line back for the type of a variable. The tricky part is that you
need to avoid going a line back when the type is in the current line
(and since any ID could be a type name that's quite tricky).
--
TALL KNIGHT OF NI: Ni!
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: filename completion ignorecase for Vim 7
On Sat, 17 Jun 2006, A.J.Mechelynck wrote: Gerald Lai wrote: On Sat, 17 Jun 2006, Bram Moolenaar wrote: Gerald Lai wrote: For Vim 7, it seems that filename completion in the :cmdline ignores case when searching for matches. For example, :e FTab matches both foo.txt Foo.txt This is different from Vim 6 where it only matches Foo.txt Is there any way to revert back to the old behavior? What system? On MS-Windows case of filenames is ignored, on Unix it matters, on Mac it depends. I'm on Windows for Vim 7, Linux for Vim 6 :) That explains it. I guess this is a matter of discrepancy between what the user wants to match, and what the OS cares to read. IMHO, what the user wants to match should take priority over whether the OS cares about the case of its filenames. Perhaps for Windows, we could have a 'smartcase' setup for filename completion matching where it's ignorecase only when all the characters are lowercase. Thanks. -- Gerald IIUC, under Windows it is not possible to have in the same directory two files whose names differ only in case. Let's say you have Makefile in some directory. Creating makefile or MAKEFILE in the same directory will overwrite it. Similarly foo.c, FOO.C and Foo.C are indistinguishable. If Vim tries to open one of them, and another one exists, the OS will deliver it. Thus a 'smartcase' or 'noignorecase' setting for Windows filenames makes no sense. True. But how about filenames that aren't the same? Let's say we have these files on a Windows system: franticallysearching_0_alongfilename.txt franticallysearching_1_alongfilename.txt .. franticallysearching_641237_alongfilename.txt Franticallysearching_641238_alongfilename.txt franticallysearching_641239_alongfilename.txt .. franticallysearching_99_alongfilename.txt and we know we want to edit the file that starts with the capital F. When we do :e FTab would we expect it to match :e franticallysearching_ where we have to follow up by typing in the unknown number for that capital F file? I'd rather have it match :e Franticallysearching_641238_alongfilename.txt where it does what it's told to do. I could care less that Windows treats these files the same: franticallysearching_641238_alongfilename.txt Franticallysearching_641238_alongfilename.txt fraNtIcallysearChiNg_641238_alongfilename.txt to let it affect what I'm searching for. In the end, it's a matter of preference :) -- Gerald
Re: synchronize current working directory - problem with vim7
On Sat, 17 Jun 2006, K.S.Sreeram wrote: [EMAIL PROTECTED] wrote: :he netrw-problems In particular, look at P6. Thanks for the pointer, but unfortunately doing let g:netrw_keepdir = 0 in _vimrc file does not seem to have any effect at all! Here's what happens: 1) run gvim.exe 2) :pwd (output: c:\Vim\vim70) 3) :e c:\Projects\Test\ (shows directory listing) 4) :pwd (output: c:\Vim\vim70) If I have 'set autochdir', then : 3) :e c:\Projects\Test (shows directory listing) 4) :pwd (output: c:\Projects) (I'd like this to be c:\Projects\Test!) So in either case, g:netrw_keepdir=0 doesn't have any effect at all, I even tried with a fresh install of vim7 without any extra plugins and the result was the same! How do I solve this? Chip, Like Sreeram, I was also trying to get g:netrw_keepdir to work but was unsuccessful with Netrw v102b. -- Gerald
svn, cvs
On 6/18/06, Suresh Govindachar [EMAIL PROTECTED] wrote: Hello, Since svn sources haven't been updated, The content in subversion repository is the same with the CVS repository, at most 1 day later. It doesn't update only because Bram had been out for holiday since last month. and since they differs from the cvs sources by CR/LF in some files Give me the list and I'll fix. [...]
