Patch 7.2a.017
Problem::doautoall executes autocommands for all buffers instead of just
for loaded buffers.
Solution: Change curbuf to buf.
Files: src/fileio.c
*** ../vim-7.2a.016/src/fileio.cFri Jun 27 21:16:33 2008
--- src/fileio.cTue Jul 8 11:23:56
Patch 7.2a.018
Problem:Compiler warnings when compiling with Gnome. (Tony Mechelynck)
Solution: Add type casts.
Files: src/gui_gtk_x11.c
*** ../vim-7.2a.017/src/gui_gtk_x11.c Wed Jul 2 21:04:36 2008
--- src/gui_gtk_x11.c Fri Jul 4 12:46:24 2008
***
*** 22,27
On 08/07/08 12:45, Bram Moolenaar wrote:
Patch 7.2a.018
Problem:Compiler warnings when compiling with Gnome. (Tony Mechelynck)
Solution: Add type casts.
Files:src/gui_gtk_x11.c
This indeed removes most of the compiler warnings for that module. :-)
The only message I get is
On 08/07/08 13:47, Tony Mechelynck wrote:
On 08/07/08 12:45, Bram Moolenaar wrote:
Patch 7.2a.018
Problem:Compiler warnings when compiling with Gnome. (Tony Mechelynck)
Solution: Add type casts.
Files: src/gui_gtk_x11.c
This indeed removes most of the compiler warnings for
Hi Bram,
after a long time, another attempt to get vim able to search a different
location than /usr/local/include and /usr/local/lib for local headers
and libraries, hopefully with good enough commentary now. The first
attempt was http://www.mail-archive.com/[EMAIL PROTECTED]/msg02896.html
Consider the following mapping :
vmap expr Q visualmode()==#V ? ESC:echo 'line'CR :
ESC:echo 'not line'CR
I would expect the result to be that hitting Q in visual mode would
echo whether I were in linewise visual mode.
The actual result is that Q tells me whether I had used linewise
visual mode
By default leadero as mapped in ftplugin/changelog.vim opens the
file ChangeLog in the current directory. The following patch makes
this slightly more flexible.
#1
The name of the change log can be defined in b:changelog and can refer
to a file in a different directory.
#2
The variable
On 08/07/08 16:18, ThoML wrote:
By defaultleadero as mapped in ftplugin/changelog.vim opens the
file ChangeLog in the current directory. The following patch makes
this slightly more flexible.
[...]
Have you tried contacting Nikolai Weibull, the maintainer-of-record?
Best regards,
Tony.
--
Have you tried contacting Nikolai Weibull, the maintainer-of-record?
Yes, maintainer ... uhm ... not yet.
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
On Tue, Jul 8, 2008 at 16:57, ThoML [EMAIL PROTECTED] wrote:
Have you tried contacting Nikolai Weibull, the maintainer-of-record?
Yes, maintainer ... uhm ... not yet.
I read the mailing list. It's actually better to write to vim_dev, as
more eyes will see it there. I can't promise that
Consider the following:
perl EOF
some code that contains Vim keywords
EOF
If has(perl) is true, no problem! A syntax region is defined that
does not include any Vim groups, and the perl syntax is included
within the region.
If has(perl) is false, however, the code within perl EOF to EOF
will
Hi,
On Tue, Jul 8, 2008 at 05:05, Charles E. Campbell, Jr.
[EMAIL PROTECTED] wrote:
I'm just beginning a semi-automated test suite -- I expect that that
will help enormously sometime in the misty future. I'll be going
through the commands and trying to build the tests, checking netrw as I
Ben Schmidt wrote:
Is it possible to get what I want?
With a little jiggerypokery it should be! Perhaps something like
gvim --remote-send C-\C-N:cfile build.logCR:call foreground()CR
You'd obviously want to wrap that in a shell script or alias...
And there are other possibilities if
Alexei Alexandrov wrote:
Ben Schmidt wrote:
Is it possible to get what I want?
With a little jiggerypokery it should be! Perhaps something like
gvim --remote-send C-\C-N:cfile build.logCR:call foreground()CR
You'd obviously want to wrap that in a shell script or alias...
And there are
Ben Schmidt wrote:
Alexei Alexandrov wrote:
Err... I'll play with it, thanks! But I just realized that I don't like
--remote-send since it doesn't create a new Vim instance in case when no
server is running yet...
Keeping thinking and trying...
If not on Windows, perhaps an autocommand
Hello,
With 7.2a now out, I didn't see any mention of support for 64-bit
Windows. Vista (whatever you feel about it) really is the gateway to
64-bit on the Windows platform. This is my plea that 7.2 supports 64-
bit Windows out of the box.
All of the work is already done. There is a site
16 matches
Mail list logo
