On Friday, August 21, 2015 at 5:31:12 PM UTC-5, James Kolb wrote:
On Friday, August 21, 2015 at 1:39:10 PM UTC-4, Bram Moolenaar wrote:
James Kolb wrote:
The current regex code may call mch_breakcheck which can process X events.
One of these events could be a remote_expr that makes its
On Monday, August 24, 2015 at 10:18:15 AM UTC-5, Ben Fritz wrote:
On Tuesday, August 18, 2015 at 3:52:23 PM UTC-5, Quan Chau wrote:
I'm really happy with this change. But are you guys moving to git to
replace mercurial?
I'm really sad with this change. Yes.
I'm too glib. Christian is
On Tuesday, August 18, 2015 at 3:52:23 PM UTC-5, Quan Chau wrote:
I'm really happy with this change. But are you guys moving to git to replace
mercurial?
I'm really sad with this change. Yes.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
Josh Wainwright wrote:
Hi Christian,
Well, would you volunteer to maintain this syntax file?
I haven't exactly volunteered, but am more than happy to do so. Is it
back to this list that I send the updated file?
No, send your patches directly to Bram Moolenaar. Tell him the
situation of
Hello Vim users,
The announced move is done!
The cleaned up git repository is available on GitHub.
You can start using it, see http://www.vim.org/git.php
If you previously had synced from the Mercurial repository on Google
Code, you can either just drop it and start using GitHub, or switch to
Bram Moolenaar wrote:
Hello Vim users,
The announced move is done!
The cleaned up git repository is available on GitHub.
You can start using it, see http://www.vim.org/git.php
If you previously had synced from the Mercurial repository on Google
Code, you can either just drop it and start
Dominique wrote:
Bram Moolenaar wrote:
[...]
the Mercurial mirror. More info here: http://www.vim.org/movetogithub.php
Sorry, the section about moving to github and taking over your local
changes isn't filled in yet. Hopefully you can figure it out yourself,
or wait until someone
On Mo, 24 Aug 2015, Marvin Renich wrote:
(I have set up an forwarding of all notifications from the vim
repository to the vim-dev ml).
I have started getting mail from Vim Github Repository; apparently
they are pull-requests forwarded to vim-dev. I have two problems with
this mail. First,
I have started getting mail from Vim Github Repository; apparently
they are pull-requests forwarded to vim-dev. I have two problems with
this mail. First, the person who sent the PR isn't identified. (This
was also a problem with the Vim problem tracker.)
Second, the List-ID headers are
No, send your patches directly to Bram Moolenaar. Tell him the
situation of non-contact with gnuplot's old mintainer, too.
(bram AT moolenaar DOT net)
Thank you for the clarification. I'm about to do that now.
For the future, I've spent a while maintaining a few of my own syntax
files and
* Christian Brabandt cbli...@256bit.org [150824 16:28]:
On Mo, 24 Aug 2015, Marvin Renich wrote:
(I have set up an forwarding of all notifications from the vim
repository to the vim-dev ml).
I have started getting mail from Vim Github Repository; apparently
they are pull-requests
El Monday 24 August 2015, Christian Brabandt escribió:
I am not going to start rewriting mails, that are sent from github. It's
just a simple forwarding, since the original github notification mail is
rejected by the google groups page.
Note that the sender name is lost as well. It's
12 matches
Mail list logo
