[vim/vim] ftplugin/python.vim: improve matching for ]] [[ ]m [m (#842)

86 views
Skip to first unread message

James Sully

unread,
Jun 1, 2016, 5:43:33 AM6/1/16
to vim/vim

This should stop ]], [[, ]m, and [m from jumping to identifiers beginning with either "def" or "class".

For instance, as it is currently, if your cursor is on apply, below:

def apply(f, x):
    return f(x)

default = "foo"
classy_identifier="bar"

def show_default():
    print(default)

Then you'll have to do ]m 3 times in order to land on def show_default(), instead of once.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/842

Commit Summary

  • ftplugin/python.vim: improve matching for ]] [[ ]m [m

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Coveralls

unread,
Jun 1, 2016, 5:50:07 AM6/1/16
to vim/vim

Coverage Status

Coverage decreased (-0.02%) to 62.28% when pulling fcae53e on sullyj3:master into 18dfb44 on vim:master.

Christian Brabandt

unread,
Jun 1, 2016, 6:29:42 AM6/1/16
to vim/vim

please contact the runtime script maintainer and discuss the issue with him.

James Sully

unread,
Jun 8, 2016, 10:50:50 AM6/8/16
to vim_dev, v...@noreply.github.com, reply+00b1d198ec7a926252541f53c390ac1d4f13d8c...@reply.github.com, vim-dev...@256bit.org
I contacted the maintainer and he hasn't responded, so I thought I'd go ahead and bump this, in accordance with CONTRIBUTING.md.
Bump.

Bram Moolenaar

unread,
Jun 8, 2016, 4:32:19 PM6/8/16
to James Sully, vim_dev, v...@noreply.github.com, reply+00b1d198ec7a926252541f53c390ac1d4f13d8c...@reply.github.com, vim-dev...@256bit.org
It looks like Johannes isn't responding.

Would you perhaps be willing to take over maintenance?

--
hundred-and-one symptoms of being an internet addict:
74. Your most erotic dreams are about cybersex

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

James Sully

unread,
Jun 9, 2016, 3:14:20 AM6/9/16
to vim/vim, vim-dev ML, Comment
I'd absolutely be willing, the main issue is whether I'm able. I don't
actually know vimscript (this patch is super trivial).

I'd love to learn and give it a shot though. Is there a document somewhere
that outlines the responsibilities and process?

On Thu., 9 Jun. 2016, 6:32 am vim-dev ML, <notifi...@github.com> wrote:

>
> James Sully wrote:
>
> > On Wednesday, 1 June 2016 20:29:42 UTC+10, Christian Brabandt wrote:
> > > please contact the runtime script maintainer and discuss the issue
> with him.
> > >
> > >
> > > —

Bram Moolenaar

unread,
Jun 9, 2016, 8:16:19 AM6/9/16
to vim/vim, vim-dev ML, Comment

James Sully wrote:

> I'd absolutely be willing, the main issue is whether I'm able. I don't
> actually know vimscript (this patch is super trivial).
>
> I'd love to learn and give it a shot though. Is there a document somewhere
> that outlines the responsibilities and process?

Just update the file header with your name and email. Send me the file
whenever you make improvements.

If you need help with writing the file the Vim maillist is a good place
to ask questions.


--
hundred-and-one symptoms of being an internet addict:
79. All of your most erotic dreams have a scrollbar at the right side.


/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///


You are receiving this because you commented.

Christian Brabandt

unread,
Jun 9, 2016, 10:45:51 AM6/9/16
to reply+00b1d1985e25b20587f87dcf7de0f8496f212b7...@reply.github.com, vim/vim, vim-dev ML, Comment, vim...@googlegroups.com
Am 2016-06-09 09:14, schrieb James Sully:
> I'd absolutely be willing, the main issue is whether I'm able. I don't
> actually know vimscript (this patch is super trivial).
>
> I'd love to learn and give it a shot though. Is there a document
> somewhere
> that outlines the responsibilities and process?

There is no documentation as far as I know. But I think ftplugins
are generally relatively easy to maintain and don't need to be updated
very often. One advise might be to maintain this file as a separate
github repository so others can contribute easily.

Best,
Christian

James Sully

unread,
Jun 9, 2016, 3:05:39 PM6/9/16
to vim...@googlegroups.com
--
--
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

---
You received this message because you are subscribed to a topic in the Google Groups "vim_dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_dev/VPVdKcsb3SY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
python.vim

Bram Moolenaar

unread,
Jun 9, 2016, 4:53:05 PM6/9/16
to James Sully, vim...@googlegroups.com

James Sully wrote:

> Attached :)
>
> And, created https://github.com/sullyj3/vim-ftplugin-python

Thanks.

Let's add the previous maintainer to the header:

" Previous Maintainer: Johannes Zellner <joha...@zellner.org>


--
If your nose runs, and your feet smell, you might be upside down.

James Sully

unread,
Jun 10, 2016, 4:30:41 AM6/10/16
to Bram Moolenaar, vim...@googlegroups.com
Done!
python.vim

vim-dev ML

unread,
Jul 8, 2016, 3:20:13 AM7/8/16
to vim/vim, vim-dev ML, Your activity

I think this can be closed. Reopen, if this issue isn't fixed yet please.


You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, .

vim-dev ML

unread,
Jul 8, 2016, 3:20:14 AM7/8/16
to vim/vim, vim-dev ML, Your activity

Closed #842.


You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, .

Reply all
Reply to author
Forward
0 new messages