I have run across a rather strange error in the syntax highlighting for
either vb.vim or html.vim. I'm unsure which is causing the problem.
Here are the circumstances under which this error occurs:
I am developing an HTA program. An HTA program (for those who do not
use Windows) is an HTML
Ok, please find attached my corrections to the c.vim file. (Diff
instructions.) Many thanks go to Tony for his invaluable help.
Especially with the diff command.
Synopsis:
Because hex values have the suffixes and the underscores it took a while
to come up with something which would handle
Yakov Lerner wrote:
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
>
>> It is fairly easy to check for inconsistencies in Binary, Octal,
and Hex
>
>
> I'm afraid C does n
Bram Moolenaar wrote:
Mark Manning 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
Yakov Lerner wrote:
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
It is fairly easy to check for inconsistencies in Binary, Octal, and Hex
I'm afraid C does not notion of binary numbers.
Yakov
On some systems that answer is correct. On others it is not. :-)
David Brown wrote:
Mark Manning wrote:
Thanks for the info! :-)
(Hit the reply button rather than "Compose Mail To".)
Would you mind configuring your email client to not insert a
Disposition-Notification-To: header when sending to the vim list.
Although most clients do i
Georg Dahn wrote:
Nikolai Weibull wrote:
This "stream of thought" mode you're using is more suited for IRC, see
http://www.vim.org/community.php.
Yes.
BTW, this is the list for development of Vim. Many of these Emails
don't belong to the development list. General questions about Vim
should
Nikolai Weibull wrote:
On 9/11/06, Mark Manning <[EMAIL PROTECTED]> wrote:
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+/-#) whi
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
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
Thanks for the info! :-)
(Hit the reply button rather than "Compose Mail To".)
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
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
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
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
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.
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
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
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
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=+
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
I believe I may have found an obscure bug. It is not a harmful bug. It
does not make VIM crash or do weird things. (Well, sort-of.) :-)
Here is how to reproduce it:
First you have to have a lot of open and close braces (}). They
do not have to be on the same line and in fact, this
22 matches
Mail list logo
