Edward L. Fox wrote:
On 5/10/07, Gautam Iyer <[EMAIL PROTECTED]> wrote:
[...]
> I've a question, though: isn't bleeding-edge development done in
> https://svn.sourceforge.net/svnroot/vim/trunk ? That /would/ be the
> appropriate line for the latest sources, right?
I don't know. I'm still ask
Sam Halperin wrote:
I am trying to syntax highlight a file containing one very long line.
(A machine generated chunk of ascii that needs to be visually checked
when an error occurs.)
The highlighting works up to about a screens worth of text (~2400
char), but stops highlighting well before t
Rene de Zwart wrote:
I would like it if vim could integrate more into a graphical application
for instances an ide.
The integration would allow application builders to use vim as a component.
relief them of the burden of maintaining an editor
Give them access to 20+ years matured editor code ba
Gregory Seidman wrote:
I'm finding that smartindent is routinely wrong about how I want things to
be indented in JS, but I haven't been able to find an indent script. I'd be
interested in working on it myself, but I don't know the first thing about
how the function referred to when setting indent
David le Comte wrote:
This is my 2nd attempt, but with smaller sample vhdl file,
The mail handler rejected my last email due to
its being too large.
Problem Description:
When editing VHDL files, autoindent mode
does not behave as expected with comment lines.
I suggest that
John Beckett wrote:
[...]
Then, I could write an email to a friend saying
"Run gvim and do .
Then you can press F11 to do ".
For example, perhaps F11 = ":cn", Shift-F11 = ":cp".
[...]
This sounds very like file types. When you are opening a file
appropriate actions can be done automatically i
Ilia N Ternovich wrote:
Hi all!
I'm trying to make recent.vim plguin working with vim-7.0
There is some kind of problem with mapping keys inside plugin:
function! OptionFiles()
"let file = bufname("%")
if bufname("")=="recent_files"
map gf
set number
set noswapf
[EMAIL PROTECTED] wrote:
Hi All,
I couldn't open the file name start with "+" in vi editor. Since
"+" is the option in vi editor. Is there any other way to open the file?
Note: I tried with escape character "\" also.
You can use "--" to indicate that all the other arguments are file
n
Peter Hodge wrote:
--- Nick Gravgaard <[EMAIL PROTECTED]> wrote:
Hi Zdenek,
On 30/10/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
Hi, Nick,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick Gravgaard
Sent: 19 October 2006 13:42
To:
Edward L. Fox wrote:
In my opinion, this kind of work shouldn't be done by hacking the
source code of VIM. You can use a vim script to call the synax
highlighting engine to convert the text into HTML code, and copy the
converted code into the clipboard with a DLL add-on (as we know, GVim
supports
Yakov Lerner wrote:
[...]
I mean, I tried 'ls c:\windows' in cygwin and it does not work ..
strange is it issue of version of cygwin ? I saw even
weirder differences in cygwin behaviour ... fat32 vs ntfs differences...
Maybe this is because \ have a special meaning for bash or some othe
Peter Hodge wrote:
Thanks for your help, I had another look and found out you need another syntax
command to reproduce it properly. Here is the revised bug report
Start vim using
vim -u NONE
insert the following test code (note that the 4th line must be indented).
array($foo)
is_array
Peter Hodge wrote:
Hello,
I have discovered that it is possible for a syntax region to overlap a syntax
keyword, even though the region is not contained in the keyword. Take the
following code example and apply the syntax commands below:
TEST CODE:
(is_array($foo))
( is_array($foo)
Marc Weber wrote:
When doing something like
map(["a","b"],"matchstr(v:val, "\(.\)"))
will the regular expression "\(.\)" be compiled on every iteration?
How about this:
for l in lines
if l =~"regex"
...
?
How about :help profile ? ;)
[...]
Hello.
I've found bug in highlighting when matchparen is used. Not sure it is
because of a matchparen thought.
Test case
=
gvim
i{}hO
Now I can see first line with one character background been highlighted
and an insert cursor over it and '{}' on a second line, both highlighted.
N
tax.c that
was modified by my previous patch from "extend inside normal inside
keepend" e-mail.
Ilya Bobir
Index: syntax.c
===
RCS file: /cvsroot/vim/vim7/src/syntax.c,v
retrieving revision 1.62
diff -c -r1.62 syntax
ere is a patch for syntax.c that does this check. I'm getting correct
behavior with this patch for my test case.
--
Ilya Bobir
Index: syntax.c
===
RCS file: /cvsroot/vim/vim7/src/syntax.c,v
retrieving revision 1.62
diff -c -
17 matches
Mail list logo
