vim-perl needs tech help, and/or a new maintainer
155 views
Skip to first unread message
Andy Lester
Oct 29, 2012, 10:26:58 AM10/29/12
to vim-...@googlegroups.com
(I just posted this to http://perlbuzz.com/2012/10/vim-perl-needs-your-help.html)
The vim-perl projects collects all the Perl-related vim support files in one place, and now it needs more TLC that I can provide it, which probably means someone other than me needs to maintain it.
A few years ago, I created vim-perl because there were about a half dozen different Perl-related files out there, all with different maintainers. There were two different perl6.vim files floating around on the web, and even the Perl 5-related files weren't maintained in a single place. Worst of all, there was no process for getting changes and improvements in these files back to Bram Moolenaar for inclusion in the main vim distribution.
Now, with vim-perl, there's a single source for all Perl-related files (syntax, indent, ftplugin, etc) and they get fed back to the vim core whenever there's an impending vim release. Anyone wanting to update their local ~/.vim directories can download and install the latest.
The problem with this solution is that I'm not a vim scripting whiz. I know enough of the vim language to get little things done, but that's not enough to maintain the package. The tech issues that have come up are beyond my knowledge. The issues queue has 51 issues that I don't have the skills to fix and don't have the time to attack. I have a bunch of pull requests pending, but I don't feel like I'm qualified to address whether they're correct or not.
There is also a lot of interest in making vim-perl an installable package using Pathogen or other related vim package managers, and I know zero about that.
Can you help? Are you interested in maintaining the project, or can you help me provide some technical direction? If so, please post to the vim-perl mailing list and let me know.
A few years ago, I created vim-perl because there were about a half dozen different Perl-related files out there, all with different maintainers. There were two different perl6.vim files floating around on the web, and even the Perl 5-related files weren't maintained in a single place. Worst of all, there was no process for getting changes and improvements in these files back to Bram Moolenaar for inclusion in the main vim distribution.
Now, with vim-perl, there's a single source for all Perl-related files (syntax, indent, ftplugin, etc) and they get fed back to the vim core whenever there's an impending vim release. Anyone wanting to update their local ~/.vim directories can download and install the latest.
The problem with this solution is that I'm not a vim scripting whiz. I know enough of the vim language to get little things done, but that's not enough to maintain the package. The tech issues that have come up are beyond my knowledge. The issues queue has 51 issues that I don't have the skills to fix and don't have the time to attack. I have a bunch of pull requests pending, but I don't feel like I'm qualified to address whether they're correct or not.
There is also a lot of interest in making vim-perl an installable package using Pathogen or other related vim package managers, and I know zero about that.
Can you help? Are you interested in maintaining the project, or can you help me provide some technical direction? If so, please post to the vim-perl mailing list and let me know.
xoxo,
Andy
Marc Chantreux
Oct 29, 2012, 10:47:23 AM10/29/12
to vim-...@googlegroups.com
On Mon, Oct 29, 2012 at 09:26:58AM -0500, Andy Lester wrote:
> (I just posted this to http://perlbuzz.com/2012/10/vim-perl-needs-your-help.html)
> (I just posted this to http://perlbuzz.com/2012/10/vim-perl-needs-your-help.html)
> The problem with this solution is that I'm not a vim scripting whiz. I
> know enough of the vim language to get little things done, but that's
> not enough to maintain the package. The tech issues that have come up
> are beyond my knowledge. The issues queue has 51 issues that I don't
> have the skills to fix and don't have the time to attack. I have a
> bunch of pull requests pending, but I don't feel like I'm qualified to
> address whether they're correct or not.
please add me as contributor or give me the project: i'll merge my pull
> know enough of the vim language to get little things done, but that's
> not enough to maintain the package. The tech issues that have come up
> are beyond my knowledge. The issues queue has 51 issues that I don't
> have the skills to fix and don't have the time to attack. I have a
> bunch of pull requests pending, but I don't feel like I'm qualified to
> address whether they're correct or not.
request and see the other issues.
> There is also a lot of interest in making vim-perl an installable
> package using Pathogen or other related vim package managers, and I
> know zero about that.
as submodule. you can also use Vundle.
My choice would be to remove the makefile.
regards
marc
Andy Lester
Oct 30, 2012, 11:57:11 AM10/30/12
to vim-...@googlegroups.com
On Oct 30, 2012, at 10:50 AM, Rob Hoelz <rdh...@gmail.com> wrote:
Count me in. I have a personal fork I'm using for adding Perl6 syntax folding, but I'd be happy to handle the occasional pull request/issue.
If you wouldn't mind granting me contributor access, I would like to label and categorize the existing open issues. (I'm a stickler for labels ;) )
My concern isn't getting stuff fixed today. My concern is ongoing fixes and direction. I can organize things, but when it comes down to "Is this the right technical answer for vim-perl?" then there are times I'm a little lost.
xoa
Britton Kerin
Oct 30, 2012, 3:21:10 PM10/30/12
to vim-...@googlegroups.com
Does this project also contain the embedded perl interpreter? I use
that for lots of
my own itches plus a released module or two.
At least count me amoung the people who strongly hopes it doesn't die.
If someone was
capable of partitioning off a well-defined task related to the
embedded interpreter I could
at least take a crack at it.
IIRC the last few times I've tried to build the latest vim it has
failed to compile right due
to problems with the embedded interpreter.
Britton
On Tue, Oct 30, 2012 at 7:50 AM, Rob Hoelz <rdh...@gmail.com> wrote:
> Count me in. I have a personal fork I'm using for adding Perl6 syntax
> folding, but I'd be happy to handle the occasional pull request/issue.
>
> If you wouldn't mind granting me contributor access, I would like to label
> and categorize the existing open issues. (I'm a stickler for labels ;) )
>
> -Rob
> --
> You received this message because you are subscribed to the Google Groups
> "vim-perl" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/vim-perl/-/lJHhFnEEkswJ.
> To post to this group, send email to vim-...@googlegroups.com.
> To unsubscribe from this group, send email to
> vim-perl+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/vim-perl?hl=en.
that for lots of
my own itches plus a released module or two.
At least count me amoung the people who strongly hopes it doesn't die.
If someone was
capable of partitioning off a well-defined task related to the
embedded interpreter I could
at least take a crack at it.
IIRC the last few times I've tried to build the latest vim it has
failed to compile right due
to problems with the embedded interpreter.
Britton
On Tue, Oct 30, 2012 at 7:50 AM, Rob Hoelz <rdh...@gmail.com> wrote:
> Count me in. I have a personal fork I'm using for adding Perl6 syntax
> folding, but I'd be happy to handle the occasional pull request/issue.
>
> If you wouldn't mind granting me contributor access, I would like to label
> and categorize the existing open issues. (I'm a stickler for labels ;) )
>
> You received this message because you are subscribed to the Google Groups
> "vim-perl" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/vim-perl/-/lJHhFnEEkswJ.
> To post to this group, send email to vim-...@googlegroups.com.
> To unsubscribe from this group, send email to
> vim-perl+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/vim-perl?hl=en.
Andy Lester
Oct 30, 2012, 3:26:58 PM10/30/12
to vim-...@googlegroups.com
On Oct 30, 2012, at 2:21 PM, Britton Kerin <britto...@gmail.com> wrote:
Does this project also contain the embedded perl interpreter? I use
that for lots of
my own itches plus a released module or two.
No, this is something else entirely. vim-perl is all the syntax highlighting and helper files that ship, such as the code that makes it so that if your cursor is on a module and you hit "gf" it opens that module.
The embedded Perl interpreter is part of vim that I know nothing about.
xoa
Rob Hoelz
Oct 31, 2012, 5:45:38 AM10/31/12
to vim-...@googlegroups.com
+1
Reply all
Reply to author
Forward
0 new messages