On Thu, Nov 13, 2008 at 1:03 PM, Jason Foreman [EMAIL PROTECTED] wrote:
This weekend I can do a trial run of rebasing MacVim onto
vim_extended. If I get it working, I will make the result available
Well, I didn't get around to it as early as I'd hoped, but I did do a
trial run of the rebase.
2008/11/19 Jason Foreman [EMAIL PROTECTED]:
On Thu, Nov 13, 2008 at 1:03 PM, Jason Foreman [EMAIL PROTECTED] wrote:
This weekend I can do a trial run of rebasing MacVim onto
vim_extended. If I get it working, I will make the result available
I've pushed the resulting branch into a fork of
Jason Foreman, 19.11.2008:
On Thu, Nov 13, 2008 at 1:03 PM, Jason Foreman [EMAIL PROTECTED] wrote:
This weekend I can do a trial run of rebasing MacVim onto
vim_extended. If I get it working, I will make the result available
Well, I didn't get around to it as early as I'd hoped, but
björn, 19.11.2008:
2008/11/19 Jason Foreman [EMAIL PROTECTED]:
On Thu, Nov 13, 2008 at 1:03 PM, Jason Foreman [EMAIL PROTECTED] wrote:
This weekend I can do a trial run of rebasing MacVim onto
vim_extended. If I get it working, I will make the result available
I've pushed the
Richard Hartmann, 18.11.2008:
On Mon, Nov 17, 2008 at 08:38, Markus Heidelberg
[EMAIL PROTECTED] wrote:
Ben Schmidt, 17.11.2008:
I gave up on SVN ages ago--I would have loved to use it, but it's just
too messy. Now I apply patches. Below is the script I use to do it with
John Beckett wrote:
Ben Schmidt wrote:
I gave up on SVN ages ago--I would have loved to use it, but
it's just too messy. Now I apply patches. Below is the script
Eventually I'd like to have a tip (http://vim.wikia.com/) on building Vim,
with
probably one overview article, and separate
On Mon, Nov 17, 2008 at 02:44, John Beckett [EMAIL PROTECTED] wrote:
Any thoughts? Should I put your script and my script on a page as a starting
point?
Can't hurt, all for it. Do you want to include the git howto I sent to
the user's
list, as well? I can do it myself, just need to know :)
On Mon, Nov 17, 2008 at 08:38, Markus Heidelberg
[EMAIL PROTECTED] wrote:
Ben Schmidt, 17.11.2008:
I gave up on SVN ages ago--I would have loved to use it, but it's just
too messy. Now I apply patches. Below is the script I use to do it with
Mercurial, which may serve as a starting point
Richard Hartmann wrote:
Can't hurt, all for it. Do you want to include the git howto
I sent to the user's list, as well? I can do it myself, just
need to know :)
Despite the fact that this thread is about the unofficial patches, I was
responding
to Ben's script that relates to the official
On Tue, Nov 18, 2008 at 04:06, John Beckett [EMAIL PROTECTED] wrote:
Despite the fact that this thread is about the unofficial patches, I was
responding
to Ben's script that relates to the official patches.
Oh, sorry!
In conclusion, please wait. I'll announce the stubs in a week or two.
björn, 15.11.2008:
2008/11/15 Markus Heidelberg [EMAIL PROTECTED]:
björn, 15.11.2008:
Anyway, I still haven't seen any reasons to switch to vim_extended yet
(so far, nothing makes _my_ life simpler).
If you don't want to use any of the features included in vim_extended, then
On Sun, Nov 16, 2008 at 17:56, Markus Heidelberg
[EMAIL PROTECTED] wrote:
björn, 15.11.2008:
[...]
Avoiding these conflicts is more important than having nice commit logs. But
there should be a way to get both. Edward, do you know why the trunk branch
doesn't have nice commit logs and is
2008/11/16 Edward L. Fox [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
You fetch from the trunk branch, right? What kind of conflicts did arise? I
suspect mostly from the runtime files!?
Any conflicts are possible. I'm not feeling surprised to that.
Because there's no much relationship in
Edward L. Fox, 16.11.2008:
On Sun, Nov 16, 2008 at 17:56, Markus Heidelberg
[EMAIL PROTECTED] wrote:
björn, 15.11.2008:
[...]
Avoiding these conflicts is more important than having nice commit logs. But
there should be a way to get both. Edward, do you know why the trunk branch
björn, 16.11.2008:
2008/11/16 Edward L. Fox [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
You fetch from the trunk branch, right? What kind of conflicts did arise? I
suspect mostly from the runtime files!?
Any conflicts are possible. I'm not feeling surprised to that.
Because
Anyway, all this makes me wonder if we really should be basing the Git
repo on the SVN repo since not even Edward is satisfied with it. I've
been thinking if it wouldn't be simpler to just apply the patches Bram
posts myself. Did you consider this option Markus?
Not really until now,
Ben Schmidt wrote:
Anyway, all this makes me wonder if we really should be basing the Git
repo on the SVN repo since not even Edward is satisfied with it. I've
been thinking if it wouldn't be simpler to just apply the patches Bram
posts myself. Did you consider this option Markus?
Not
Ben Schmidt wrote:
I gave up on SVN ages ago--I would have loved to use it, but
it's just too messy. Now I apply patches. Below is the script
Eventually I'd like to have a tip (http://vim.wikia.com/) on building Vim, with
probably one overview article, and separate articles for downloading,
Ben Schmidt, 17.11.2008:
Anyway, all this makes me wonder if we really should be basing the Git
repo on the SVN repo since not even Edward is satisfied with it. I've
been thinking if it wouldn't be simpler to just apply the patches Bram
posts myself. Did you consider this option
2008/11/15 Markus Heidelberg [EMAIL PROTECTED]:
As far as I know, macvim/vim contains the official runtime patches,
and macvim/master also gets MacVim-specific runtime patches)
What are the official runtime patches? For runtime files there don't exist
patches. MacVim specific runtime
björn, 15.11.2008:
2008/11/15 Markus Heidelberg [EMAIL PROTECTED]:
As far as I know, macvim/vim contains the official runtime patches,
and macvim/master also gets MacVim-specific runtime patches)
What are the official runtime patches? For runtime files there don't exist
patches.
2008/11/15 Markus Heidelberg [EMAIL PROTECTED]:
björn, 15.11.2008:
The entire point of the vim branch is that I need to separate the
MacVim stuff from Vim _and_ official runtime file updates.
OK, then I understand.
How do you update the runtime files? Do you just overwrite them on your
Hi Björn,
Jason already explained several things, so just some comments from me.
björn, 13.11.2008:
2008/11/13 Markus Heidelberg [EMAIL PROTECTED]:
Jason Foreman, 10.11.2008:
Sorry I had not responded before, but I wanted to let you know that I
find your vim_extended repository
Jason Foreman, 13.11.2008:
On Thu, Nov 13, 2008 at 12:29 PM, björn [EMAIL PROTECTED] wrote:
2008/11/13 Markus Heidelberg [EMAIL PROTECTED]:
Yes, they don't have a common base, that makes merging even more difficult
than it should be, I think. Having a common base would be a good idea,
The problem with all the $Id$ conflicts come from the runtime files
updates
Brörn does. He has committed the runtime updates into his vim branch
and merges
it into the master branch. I would suggest to use separate branches
for macvim
and the runtime updates.
Wouldn't that make
Nico Weber, 14.11.2008:
The problem with all the $Id$ conflicts come from the runtime files
updates
Brörn does. He has committed the runtime updates into his vim branch
and merges
it into the master branch. I would suggest to use separate branches
for macvim
and the runtime
Richard Hartmann, 08.11.2008:
On Fri, Nov 7, 2008 at 00:07, Markus Heidelberg
[EMAIL PROTECTED] wrote:
But because there was not a single response to my mail from 13.10.2008, I
came
to the conclusion that nobody was interested in this. That was quite
disappointing, especially
Jason Foreman, 10.11.2008:
Sorry I had not responded before, but I wanted to let you know that I
find your vim_extended repository invaluable. I use it to build my
own Vim for Linux. I would like to also use it to build MacVim, but
the MacVim repo has its own git branch imported from
2008/11/13 Markus Heidelberg [EMAIL PROTECTED]:
Jason Foreman, 10.11.2008:
Sorry I had not responded before, but I wanted to let you know that I
find your vim_extended repository invaluable. I use it to build my
own Vim for Linux. I would like to also use it to build MacVim, but
the
On Fri, Nov 7, 2008 at 00:07, Markus Heidelberg
[EMAIL PROTECTED] wrote:
Yes, I could, if the repo would be used by some people. I think I have even
tried to apply each extension that could be downloaded as a patch file.
Thanks to Jason, I am running a version of Vim with relativenumber
Hi Markus,
On Nov 6, 2008, at 5:07 PM, Markus Heidelberg wrote:
Richard Hartmann, 06.11.2008:
Also, I saw that Markus' git repo [3] does not incorporate all
patches
listed on said site. Perhaps he could add those, as well?
Yes, I could, if the repo would be used by some people. I think
On Sat, Nov 8, 2008 at 14:24, Bram Moolenaar [EMAIL PROTECTED] wrote:
These patches are made by anyone who is interested in making a patch. I
don't have time to look through them, especially if a patch gets changed
a few times. So don't expect a good or bad comment from me. Unless
it's
On Fri, Nov 7, 2008 at 00:07, Markus Heidelberg
[EMAIL PROTECTED] wrote:
But because there was not a single response to my mail from 13.10.2008, I came
to the conclusion that nobody was interested in this. That was quite
disappointing, especially because several threads on this list let me
Richard Hartmann wrote:
Can you add the patch to the list, please? :)
Sure but I don't have time to work out what text to put.
We need something like the following from
http://groups.google.com/group/vim_dev/web/vim-patches
10. Variable tabstops
Author: Matthew Winn
Status: alpha
On Thu, Nov 6, 2008 at 11:38, John Beckett [EMAIL PROTECTED] wrote:
On October 11 we had a discussion regarding a spammer who changed all the
links on
the 'Vim patches' page to a porn site (according to Google Groups forum
messages,
such links are probably to a site that tries to exploit
Hi all,
while searching for something unrelated, I stumbled over Matt's color
patch [1], again. It's the patch he wrote for better color support on
the CLI.
I tried adding it to the vim google groups site [2], but failed to locate
any edit button. Can we still edit on this site? I am logged into
On Thu, Nov 6, 2008 at 11:55, John Beckett [EMAIL PROTECTED] wrote:
Richard Hartmann wrote:
Can you add the patch to the list, please? :)
Sure but I don't have time to work out what text to put.
We need something like the following from
John Beckett wrote:
Richard Hartmann wrote:
I tried adding it to the vim google groups site [2], but
failed to locate any edit button. Can we still edit on this
site?
On October 11 we had a discussion regarding a spammer who changed all
the links on the 'Vim patches' page to a porn
Following Richard's suggestion, I added a (shortened) description of Matt
Wozniski's
patch to:
http://groups.google.com/group/vim_dev/web/vim-patches
Matt: Please reply (to me or the list) if any wording needs to be changed.
John
--~--~-~--~~~---~--~~
You
Richard Hartmann, 06.11.2008:
Also, I saw that Markus' git repo [3] does not incorporate all patches
listed on said site. Perhaps he could add those, as well?
Yes, I could, if the repo would be used by some people. I think I have even
tried to apply each extension that could be downloaded as a
40 matches
Mail list logo
