Lech Lorens | 1 Oct 2011 01:45
Picon

Re: Improve errorformat strings

On 30-Sep-2011 Ben Boeckel <mathstuf <at> gmail.com> wrote:
> On Wed, Sep 14, 2011 at 19:08:16 -0400, Ben Boeckel wrote:
[…]
> > Patch attached.
> 
> Ping?

Check out 7.3.323

-- 
Cheers,
Lech

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Zvezdan Petkovic | 1 Oct 2011 06:03
Picon
Favicon

Re: awk indentation

On Sep 30, 2011, at 8:45 AM, erik wrote:

> I think I have this issue is fixed, as well as every other pending
> complaint.

Not all issues yet. :-)

> May I ask all involved in this thread to evaluate?

Gladly.

> You can find the indenter here: http://dl.dropbox.com/u/26176183/awk.vim

Thanks for providing this.

> Tested with vim 7.3 and 6.3, on several awk programs. It works fine on
> 7.3. It fails on vim 6.3 because imho cursor( v:lnum, 1) does not work
> (at least during indent).
> 
> Hope you like it.

First, the good news: It works much better than before.

The following doesn't work.

1. This may be a matter of preference but I think the continued lines
   are not aligned correctly.  For example, the code I aligned as this:

	vcard_tr_palm = "ADR;WORK ADR;HOME ADR " \
			"TEL;WORK TEL;FAX " \
(Continue reading)

Sergey Khorev | 1 Oct 2011 06:25
Picon

Re: racket (:mz) SEGV's vim

> This causes a SEGV.
>
> It seems to be in GC_add_roots -- but I don't know whose GC_add_roots
> that is (I think my racket is actually a 3m variant)

Looks like the folks changed something in Racket... again. I will take a look.

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Christ van Willegen | 1 Oct 2011 11:20
Picon

Question about DocComments in PHP (perhaps other languages as wel...)

Hi,

I ran into a problem yesterday when an annotation in a doc comment was
not picked up by a comment handler. Long story short: It turned out
that I had typed  /* where I should have typed /** to open the
comment.

For Vim, this is all comment, so it wasn't immediately noticeable.

I would like to add a request for the php.syntax (and perhaps others
as well?) to:

*) Include a 'DocComment' type (opened with /** or perhaps /*!) so
that it could be colored differently, and/or

*) check for annotations in comments (annotations usually start with
an  <at> , after a space, so '  <at> ' would start an annotation) and highlight
them as warnings

I can provide examples if they are wanted/needed.

Thanks in advance for any insights or help!

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
(Continue reading)

Dominique Pellé | 1 Oct 2011 12:52
Picon

[patch] window title not being updated when doing ":language fr_FR.UTF-8"

Hi

I see a minor bug in Vim-7.3.329 on Linux.
Command ":language fr_FR.UTF-8"  does not update the language
of the title in the terminal or title of gvim. Doing ":redraw!" does not
help either.  The language of the title gets updated after resizing the
terminal or gvim.

Steps to reproduce:

1) Start gvim with:
    $ (export LANG=en_US.UTF-8; gvim -u NONE -U NONE)

2) Observe that the window title is in English "[No Name] - GVIM1".

3) Enter Ex command    :language fr_FR.UTF-8

4) Observe that window title is still in English (bug!, I'd
   expect it to become in French).
   Doing ":redraw!"  does not work around.
   Observe that after resizing the window, title then
   becomes in French:  "[Aucun nom] - GVIM1"

Attached patch fixes it.

Regards
-- Dominique

--

-- 
You received this message from the "vim_dev" maillist.
(Continue reading)

Tim Brown | 1 Oct 2011 13:53
Gravatar

Re: racket (:mz) SEGV's vim

Sergey,

On 1 October 2011 05:25, Sergey Khorev <sergey.khorev <at> gmail.com> wrote:
> Looks like the folks changed something in Racket... again. I will take a look.

I'm subscribed to their twitter feed (including changes/patches etc.).
They never stop changing things... ever. Bless 'em.

Can you recommend a working pair of vim/racket versions (from source)
to get me going in the meantime?

Thanks,

Tim

-- 
| Tim Brown <tim.brown <at> timb.net> | M:+44(0)7771714159 | H:01372747875 |

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Sergey Khorev | 1 Oct 2011 14:36
Picon

Re: racket (:mz) SEGV's vim

> I'm subscribed to their twitter feed (including changes/patches etc.).
> They never stop changing things... ever. Bless 'em.

Yep, that's good for Racket but not so good for embedding
applications: API leaps unpredictably and I'm yet to see detailed
changelog for this kind of stuff.

> Can you recommend a working pair of vim/racket versions (from source)
> to get me going in the meantime?

MzScheme 4.x and Racket 5.0.1 should work for Vim 7.3.49+

--

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Xavier de Gaye | 1 Oct 2011 14:39
Picon

Re: building a test case with netbeans

On Fri, Sep 30, 2011 at 4:12 PM, Bram Moolenaar wrote:
> Xavier de Gaye wrote:
>> ...
>> When building an automated test case with netbeans, it is not obvious
>> how to have Vim made to call the idle loop. The attached patch adds a
>> call to netbeans_parse_messages() when the Vim ":sleep" command is
>> run. This allows for a more deterministic way of writing the test
>> cases (instead of inserting ":sleep" commands randomly until it works,
>> on this hardware).
>
> OK, this makes sense.  So you would run a Vim script that calls sleep in
> an endless loop?

Yes, this is right. It is a bit complicated due to the fact that there
are three processes running asynchronously (Vim, pyclewn and gdb), so
it is better to give an example. A typical pyclewn test case checks
that the content of a ${test_out} file contains the expected Vim signs
list:

    * the test starts by running the sequence of Vim and pyclewn
      commands that triggers gdb and sets breakpoint signs in Vim
      buffers
    * the test ends with the following commands:

            :call Wait_eop()
            :redir! > ${test_out}
            :sign place
            :qa

    * the definition of Wait_eop() follows:
(Continue reading)

Sergey Khorev | 1 Oct 2011 16:29
Picon

Re: racket (:mz) SEGV's vim

>> Can you recommend a working pair of vim/racket versions (from source)
>> to get me going in the meantime?
>
> MzScheme 4.x and Racket 5.0.1 should work for Vim 7.3.49+

Actually 5.1.3 has worked for me out of the box (I installed it from
Racket PPA on Ubuntu).
The only change needed is below (looks like PPA creator decided to use
/usr/share to store collects):
diff -r fb6b43d55773 src/auto/configure
--- a/src/auto/configure	Fri Sep 30 18:35:57 2011 +0200
+++ b/src/auto/configure	Sat Oct 01 17:25:02 2011 +0300
 <at>  <at>  -4935,6 +4935,10  <at>  <at> 
     else
       if test -d $vi_cv_path_mzscheme_pfx/lib/racket/collects; then
 	SCHEME_COLLECTS=lib/racket/
+      else
+        if test -d $vi_cv_path_mzscheme_pfx/share/racket/collects; then
+	  SCHEME_COLLECTS=share/racket/
+        fi
       fi
     fi
     if test -f
"${vi_cv_path_mzscheme_pfx}/${SCHEME_COLLECTS}collects/scheme/base.ss"
; then

--

-- 
Sergey Khorev
http://sites.google.com/site/khorser
Can anybody think of a good tagline I can steal?
(Continue reading)

Bram Moolenaar | 1 Oct 2011 20:02
Picon

Re: Bug in "it" and "at" text objects


Ben Fritz wrote:

> Using this XML snippet:
> 
> <?xml version="1.0"?>
> <root_tag>
>   <SomeTag>
>      <SomeTagPlusText>content</SomeTagPlusText>
>   </SomeTag>
>   <another_tag></another_tag>
> </root_tag>
> 
> I place my cursor on SomeTag and hit vit. It acts like I placed my
> cursor on root_tag. Same with vat. In other words, vat selects the
> entire <root_tag>...</root_tag> text, whereas I expect it to highlight
> only <SomeTag>...</SomeTag>
> 
> If I make a minor change to the XML:
> 
> <?xml version="1.0"?>
> <root_tag>
>   <SomeTag>
>      <SomeOtherTag>content</SomeOtherTag>
>   </SomeTag>
>   <another_tag></another_tag>
> </root_tag>
> 
> Then everything works as I expect. Pressing vat on SomeTag will
> highlight only from <SomeTag> to </SomeTag>.
(Continue reading)


Gmane