This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients brett.cannon, eric.araujo, orsenthil, pitrou
Date 2010-12-30.06:46:32
SpamBayes Score 5.8619953e-06
Marked as misclassified No
Message-id <20101230064620.GA3288@rubuntu>
In-reply-to <1293479986.26.0.682359680328.issue9893@psf.upfronthosting.co.za>
Content
On Mon, Dec 27, 2010 at 07:59:46PM +0000, Brett Cannon wrote:

> But if you have a local copy of the Vim files from the community
> what is preventing you from editing them for new keywords and
> sending a patch to the maintainer so that the rest of the community
> is brought up to speed that much faster?

You mean the Python Core Dev maintaining a set of Vim files as a fork
from the vim.org maintained files and adding new features when they
come up and be submitted the vim.org.

If that is the idea, it is indeed a good one.

But often it has happened that someone at the vim.org has noticed the
changes in Python and updated the files and the scripts at vim.org
remain updated.

> I suspect that not many people beyond core devs use the Misc/Vim
> file while more people in the community use the vim.org files.

Possibly and perhaps that is reason to discard our Misc/Vim in favor
of vim.org files.

But if you think there *should* be an official recommendation, some
pointers would definitely serve.
History
Date User Action Args
2010-12-30 06:46:35orsenthilsetrecipients: + orsenthil, brett.cannon, pitrou, eric.araujo
2010-12-30 06:46:32orsenthillinkissue9893 messages
2010-12-30 06:46:32orsenthilcreate