Hi Thilo,
Thilo Six wrote:
Excerpt from Thomas Köhler:
-- snip --
And it would help people like me that used to maintain some
runtime files in the past and now are stuck maintaining something
they don't use any longer.
I think that is exactly the meaning of team maintenance.
I commit
On Tue, 15 May 2012, Thomas Köhler wrote:
Hi Thilo,
Thilo Six wrote:
Excerpt from Thomas Köhler:
-- snip --
And it would help people like me that used to maintain some runtime
files in the past and now are stuck maintaining something they don't
use any longer.
I think that is exactly the
Hello Benjamin,
Benjamin R. Haskell wrote:
On Tue, 15 May 2012, Thomas Köhler wrote:
Thilo Six wrote:
Excerpt from Thomas Köhler:
[...]
But of course, there once was a reason for the current model, which
is let people maintain the stuff who know what they are doing
That exactly will not be
On Monday, May 14, 2012 6:18:57 PM UTC-5, Jason A. Spiro wrote:
Thank you very much for your work on Vim.
In certain cases, Vim can quite-reliably guess the background color:
- On rxvt and its derivatives.
(See src/option.c:term_bg_default(), viewable online at
I like the idea of team maintenance of runtime files. I don't see why we
shouldn't just do it for all the runtime files. Just set up a Bitbucket or
Github clone (or another Google Code project, but I don't see a good way to
relate it back to the main Vim repository, and clones made on the
Hello Thomas and Benjamin,
Excerpt from Thomas Köhler:
-- snip --
I think you're misinterpreting what team maintenance would mean. It
wouldn't be a team per language, but rather a single team to handle
changes (maintenance) to all syntax files. (Which doesn't preclude
active maintainers
On 2012-05-15, Thilo Six wrote:
When i think of this team i count each current maintainer as a member already.
The idea is to use a mailinglist where anyone who likes can subscribe (think
of
vim-dev). All communication about runtimefiles happens openly. Not 99% via
private email where no
On Di, 15 Mai 2012, Gary Johnson wrote:
I like it.
Do you think there would be enough maintenance traffic to justify a
separate runtime-maintainers list or would vim-dev suffice?
+1
If the traffic isn't too big, I would prefer vim-dev list (since I am
already subscribed) so please add me
Hello Gary and Christian,
Excerpt from Christian Brabandt:
On Di, 15 Mai 2012, Gary Johnson wrote:
I like it.
Do you think there would be enough maintenance traffic to justify a
separate runtime-maintainers list or would vim-dev suffice?
+1
If the traffic isn't too big, I would
вторник, 15 мая 2012 г., 1:30:23 UTC+4 пользователь Bram Moolenaar написал:
ZyX wrote:
Any news on the status of the patch?
It's in the todo list at line 164:
Patch for Python: add pyeval()(zyx, 2012 Apr 15, update Apr 16)
Also changes for Lua. Update Apr 19. Update Apr 22.
That's
Nacitar Sevaht wrote:
This is subtle, but I noticed it toying around with some
metaprogramming things..
True is highlighted as if it's a keyword, though it is not. true
is indeed a keyword, however, and should be hilighted.. but it is
erroneous to highlight True. The same can be said of
Hi Ben!
On Di, 15 Mai 2012, Ben Fritz wrote:
Since the error only occurs if 'backup' and 'writebackup' are both
off, maybe we could only do the dry run conversion in this
situation? I.e., if either 'backup' or 'writebackup' are set, do what
Vim has always done; but if neither are set, do
Stephen Bovy wrote:
I have a final done-done set of changes that will fully support The
most-current version of z/OS with Motif 2.1 and feature-toolbar
support
Works great and looks beautiful !!
Bram,
Would you like me to re-submit a consolidated version ???
It would be nice to
Ok, thanks
It will take me a while to put this together :)
-Original Message-
From: b...@moolenaar.net [mailto:b...@moolenaar.net]
Sent: Tuesday, May 15, 2012 12:20 PM
To: Bovy, Stephen
Cc: vim_dev@googlegroups.com; vim-...@vim.org
Subject: Re: z/OS Make-File and Configure Script
On 5/15/2012 9:02 AM, Thilo Six wrote:
No one is anyone blocking to take care of their peeve pets.
I'd be hesitant to suggest that people take care of their pet peeves.
Yes for real bugs or infrastructure features (like spell). But since
there is hopefully a main guy for each file, shouldn't
On Mon, May 7, 2012 at 7:11 PM, Val Markovic v...@markovic.io wrote:
I can confirm that mattn's patch does appear to fix this problem; the dot
register works again.
Any chance of this patch landing in trunk soon? I've been using a
version of Vim patched with it every day since it was posted
16 matches
Mail list logo
