I don't see where's the bug in official vim here - can you explain more? (I do not use vim at all)

Also it would be useful to see if its an issue with the vim package in testing as its very different from the one currently in extra.

Nono, you can't understand me, so i'd like to have a new feature in official vim package, in extra repo of course, i've written above.

The vimgdb from AUR has got so much BUGS to use it . . . It would just 2-3 plus line in the official vim pkgbuild according to this describtion:

http://clewn.sourceforge.net/install.html

Please take it, because for my development/work it's absolutely neccesary.

Your request doesnt make any sense, at least the way you expressed it.
Please write exactly what you would like to be added and where.

HHHHHH.....

Ok, you know vim. Vim has a debugging feature across VimGDB patch. I've linked the url above to see it . . .

So this patch allows to the user to use gdb inside vim. You can see a vimgdb pkgbuild in AUR, but it's not good! It crashes my vim absolutely.

My purpose is to add this lines to pkgbuild:
patch -d vim72 --backup -p0 < vimgdb/vim72.diff

And of course the tar.gz source to the source line in the PKGBUILD, i can't understand what you can't understand.

I can see that we include netbeans for the clewn interface, but not patching vim for vimgdb.

Yeah, but we'd like to develop in console-based environment without any gui, so clawn, netbeans, gvim is not okaz for me.

I really don't understand why can't you put this 2-3 line to the official vim package??!!

Is it so hard? It took me just about 5 minutes . . .

I don't wanna patch vim for the purpose of another package, which would be clearly against Archlinux packaging guide lines. Enabling the netbeans interface is fine.

> The vimgdb from AUR has got so much BUGS to use it
Cannot it be fixed?

Tobias Kieslich: You can't put 2-3 lines to the PKGBUILD. Can you attach the related lines of the Archlinux packaging guide lines ???

Roman Kyrylych: The fixed situation means the vim PKGBUILD + this 2-3 lines . . .

It's not about adding 3 lines, it's about maintaining packages that consist of source files that stem from different origins. Sooner or later things get out of sync and break.
"Arch provides non-patched, vanilla software; packages are offered from pure upstream sources, how the author originally intended it be distributed. Patching only occurs in extremely rare cases, to prevent severe breakage in the instance of version mismatches that may occur within a rolling release model. " from http://wiki.archlinux.org/index.php/Arch_Linux
Or more elaborate, her: http://wiki.archlinux.org/index.php/The_Arch_Way

Okay! In this case why does vim contains 166 patches ??? Yes, you heard well, 166, not one . . .
I can't understand your statement to this feature request, why the developer is an uncorrect to the users.

I'm close to closing this bug, read the PKGBUILD and understand the way it works!
The 166 patches actually are from vim.org itself and they represent the ongoing STABLE development of the software. Yes, that is a little odd compared to the way other projects release their sources and it creates a huge overhead for me maintaining the package, but it's the vim way of doing it. Those patches actuall affect the internal version number of vim, displayed by vim --version.
The patches you are refrerring to are third party, aka different origin.

This feature is available in every other distribution, however in archlinux not . . .

Use ABS to build vim with whatever non upstream patches you like. Other distributions may include that, not ALL as you say, Debian based do, but they dont offer you the convinience of building your own packages easily like Arch.

You claim "every other distribution", but I checked Debian: they don't include this patch. Checked fedora, no patch either.

@Laszlo: there are 2 choices:
1) take the current vim pkgbuild, add the required patch and host it on AUR
2) convice vim developers to include it in official vim