Patch 7.0.095
Problem:The Greek tutor is not available in utf-8. "el" is used for the
language, only "gr" for the country is recognized.
Solution: Add the utf-8 Greek tutor. Use it for conversion to iso-8859-7
and cp737. (Lefteris Dimitroulakis)
Files: runtime
Patch 7.0.096
Problem:taglist() returns the filename relative to the tags file, while
the directory of the tags file is unknown. (Hari Krishna Dara)
Solution: Expand the file name. (Yegappan Lakshmanan)
Files: src/tag.c
*** ../vim-7.0.095/src/tag.cThu Apr 27 23:40:34 2
This patch adds 'extrahuge' build size, which is
huge+interpreters (spelled as --with-features=extrahuge
or --with-features=allinterp).
Yakov
P.S. Maybe --with-features=max is better name.
patch-extrahuge
Description: Binary data
How can a script test for specific patchlevel ?
For example, I have vim 7.0.86 and I need to check in the script that
patchlevel is >= 7.0.86. But v:version is 700. How ? It would be
nice if to have patchlist available through some v: variable.
Yakov
Patch 7.0.097
Problem:":tabclose N" that closes another tab page does not remove the tab
pages line. Same problem when using the mouse.
Solution: Adjust the tab pages line when needed in tabpage_close_other().
Files: src/ex_docmd.c
*** ../vim-7.0.096/src/ex_docmd.c
Bug? With
gvim -o3 file1.txt file2.txt file3.txt
only the first two are displayed in a window. (All 3 files exist.)
The arguments list is OK, since
:bot new
:last
opens the 3rd file in a 3rd window.
If the line
set noea wmh=0 wh=9 hh=9
(in my vimrc)
Tony Mechelynck wrote:
> Bug? With
>
> gvim -o3 file1.txt file2.txt file3.txt
>
> only the first two are displayed in a window. (All 3 files exist.)
>
> The arguments list is OK, since
>
> :bot new
> :last
>
> opens the 3rd file in a 3rd window.
>
> If the line
>
>
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Bug? With
gvim -o3 file1.txt file2.txt file3.txt
only the first two are displayed in a window. (All 3 files exist.)
The arguments list is OK, since
:bot new
:last
opens the 3rd file in a 3rd window.
If the line
I started using FreeBasic which uses the "*.bas" ending and was
wondering if:
1. Anyone is interested in me sending in the updated basic.vim file.
2. If this is the right mailing group to send it to.
Thanks!
Mark
Mark Manning wrote:
I started using FreeBasic which uses the "*.bas" ending and was
wondering if:
1. Anyone is interested in me sending in the updated basic.vim file.
2. If this is the right mailing group to send it to.
Thanks!
Mark
Normal procedure would be to first try contacting the ma
In the syntax stuff, the c.vim file should be changed to have the following:
Old:
syn regioncStringstart=+"+ skip=+\|\\"+ end=+"+
contains=cSpecial
New
syn regioncStringstart=+"+ skip=+\|\\\"\|'+ end=+"+
contains=cSpecial
syn regioncStringstart=+
On 9/10/06, Mark Manning <[EMAIL PROTECTED]> wrote:
In the syntax stuff, the c.vim file should be changed to have the following:
Old:
syn regioncStringstart=+"+ skip=+\|\\"+ end=+"+
contains=cSpecial
New
syn regioncStringstart=+"+ skip=+\|\\\"\|'+ end=+"+
cont
I get:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mail server after RCPT TO:<[EMAIL PROTECTED]>:
host uk2mxarray3.uk2.net [83.170.64.215]: 550 addres
Mark Manning wrote:
> In the syntax stuff, the c.vim file should be changed to have the following:
>
> Old:
>
> syn regioncStringstart=+"+ skip=+\|\\"+ end=+"+
> contains=cSpecial
>
>
> New
>
> syn regioncStringstart=+"+ skip=+\|\\\"\|'+ end=+"+
> contains=c
Let me see if I can get an example program put together to show the
highlighting problem I've seen. Give me a few minutes here.
Mark
Patch 7.0.098
Problem:Redirecting command output in a cmdline completion function
doesn't work. (Hari Krishna Dara)
Solution: Enable redirection when redirection is started.
Files: src/ex_docmd.c, src/ex_getln.c
*** ../vim-7.0.097/src/ex_docmd.c Sun Sep 10 15:50:32 2
I'm working in FreeBasic and some C and some Perl. This is one of the
fixes in the basic.vim thing I'm doing and I saw the same thing in the
c.vim file and thought they would give the same incorrect highlighting.
I ran into this (for C) while working at NASA and thought I'd fix it,
but as you
Patch 7.0.099
Problem:GUI: When the popup menu is visible using the scrollbar messes up
the display.
Solution: Disallow scrolling the current window. Redraw the popup menu
after scrolling another window.
Files: src/gui.c
*** ../vim-7.0.098/src/gui.cTue Aug
Mark Manning wrote:
I'm working in FreeBasic and some C and some Perl. This is one of the
fixes in the basic.vim thing I'm doing and I saw the same thing in the
c.vim file and thought they would give the same incorrect
highlighting. I ran into this (for C) while working at NASA and
thought I
That is very strange. In 7.0.17 the "exit" command is still highlighted
as a string. If I put in an additional single quote then it
re-highlights as a function.
test.pl
print "This's a test'";
exit( 0 );
Look correct but the
test.pl
print "This's a test";
exit( 0 );
Does not.
Ok, with so many people going "What do you mean?" I'm going to do the
right thing and download the latest and greatest version. Obviously
there is something wrong going on here with me and my system. Otherwise
so many people wouldn't be saying their stuff is working properly. Give
me a few
Mark Manning wrote:
That is very strange. In 7.0.17 the "exit" command is still highlighted
as a string. If I put in an additional single quote then it
re-highlights as a function.
test.pl
print "This's a test'";
exit( 0 );
Look correct but the
test.pl
print "This's a test";
ex
Mark Manning wrote:
Ok, with so many people going "What do you mean?" I'm going to do the
right thing and download the latest and greatest version. Obviously
there is something wrong going on here with me and my system. Otherwise
so many people wouldn't be saying their stuff is working prope
Ok, after downloading the current items on the web page at vim.org both
C and Perl are working ok (in both Windows and Cygwin/Linux). Basic
still has the problems from before. Thanks to everyone for speaking
up. :-)
To Tony: Thanks for the diff command. I'll see about posting it but
not
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
(If I
put in "echo version" it comes back as 700. Even the 7.0.17 version
comes back as 700
Output of ':echo version' does not reflect patchlevel. (the .17 in
7.0.17 is patchlevel).
You can see the patchlevel on the initial splashscreen, or
Hey, I hate to keep barging in here asking questions and such but here
is a new one. :-)
In the new basic.vim file I am having a problem. In FreeBasic you can
use both single as well as double quotes to enclose a string.
Unfortunately, you can also have comments which start with a single
q
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
Hey, I hate to keep barging in here asking questions and such but here
is a new one. :-)
In the new basic.vim file I am having a problem. In FreeBasic you can
use both single as well as double quotes to enclose a string.
Unfortunately, you ca
-- Forwarded message --
From: Mark Manning <[EMAIL PROTECTED]>
Date: Sep 11, 2006 1:43 AM
Subject: Re: New question
To: Yakov Lerner <[EMAIL PROTECTED]>
Ok, tried it and it works! :-)
Thanks! :-)
Mark
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart="0x\x*[g-zG-Z]" end="\W"
The highlight command:
hi link c
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
I saw in the c.vim that there was an error statement for octal numbers.
There isn't one for hex numbers so I made one really quickly. If you
want, just put it into the c.vim file. :-)
The test:
syn regioncHexErrorstart="0x\x*[g-zG-Z]
Thanks for the info! :-)
(Hit the reply button rather than "Compose Mail To".)
Mark
It is fairly easy to check for inconsistencies in Binary, Octal, and Hex
because they have a fixed format. Decimal is not as easy due to there
being integers, reals, and general format numbers (ie: #e+/-#) which are
all grouped into the "Decimal" category. I'll think about it though.
Maybe I
Hi.
I tried ftp access with "netrw.vim".
ex: :e ftp://machine/path/
I get "--No lines in buffer--".
and I get following message in vim buffer in japanese.
ftp: is not internal command.
I guess that the first problem cause by ":file " command.
and the second cause by following code.
--
Mark Manning wrote:
Ok, after downloading the current items on the web page at vim.org both
C and Perl are working ok (in both Windows and Cygwin/Linux). Basic
still has the problems from before. Thanks to everyone for speaking
up. :-)
To Tony: Thanks for the diff command. I'll see about
On Sun, 10 Sep 2006 at 1:56pm, Bram Moolenaar wrote:
>
> Patch 7.0.096
> Problem:taglist() returns the filename relative to the tags file, while
> the directory of the tags file is unknown. (Hari Krishna Dara)
> Solution: Expand the file name. (Yegappan Lakshmanan)
> Files:
On Sun, 10 Sep 2006 at 9:07pm, Bram Moolenaar wrote:
>
> Patch 7.0.098
> Problem:Redirecting command output in a cmdline completion function
> doesn't work. (Hari Krishna Dara)
> Solution: Enable redirection when redirection is started.
> Files:src/ex_docmd.c, src/ex_g
A.J.Mechelynck wrote:
Mark Manning wrote:
Ok, after downloading the current items on the web page at vim.org
both C and Perl are working ok (in both Windows and Cygwin/Linux).
Basic still has the problems from before. Thanks to everyone for
speaking up. :-)
To Tony: Thanks for the diff
On Fri 8-Sep-06 4:11pm -0600, Bram Moolenaar wrote:
> Bill McCarthy wrote:
>
>> To better understand what vimdiff is doing (and why it is so
>> slow), I had my shell (4NT under WinXP) keep a log showing
>> me just what was requested. [Note: I use '>!' instead of '>'
>> for redirection because my 4
38 matches
Mail list logo