On Tue, Dec 23, 2008 at 3:39 AM, Markus Heidelberg
wrote:
>> quick feedback after a cloning of vim_mainline: tons of commits are
>> due to git-svn merged commits and syncing with CVS.
>> could this be avoided ? maybe some commits can be squashed.
>
> Why should I squash only to loose/cripple hist
On 22/12/08 20:26, Markus Heidelberg wrote:
> Richard Hartmann, 22.12.2008:
>> PS: There is a bug on http://repo.or.cz/w/vim_extended.git
>>
>> edit and build as usual
>> vim; make; make install
>> :s_vim_./configure_
>
> The 'vim' command belongs to 'edit' from above. I usually never call
> confi
Christian MICHON, 23.12.2008:
>
> On Mon, Dec 22, 2008 at 2:31 PM, Markus Heidelberg
> wrote:
> >http://repo.or.cz/w/vim_mainline.git
>
> nice to see another git repo for vim :)
> how often do you synchronize it ?
When I see a patch on the list, I look whether the svn repo is updated
and t
Hello,
I sent this email to b...@vim.org, but I am also sending it here so
more eyes have a chance to see it.
Vim's omni-completion fails for Python any time a file contains an
import statement which fails (i.e., any import statement that will
raise an ImportError). For example:
import notamodu
On Mon, Dec 22, 2008 at 2:31 PM, Markus Heidelberg
wrote:
>http://repo.or.cz/w/vim_mainline.git
nice to see another git repo for vim :)
how often do you synchronize it ?
quick feedback after a cloning of vim_mainline: tons of commits are
due to git-svn merged commits and syncing with CVS.
c
Richard Hartmann, 22.12.2008:
>
> On Mon, Dec 22, 2008 at 14:31, Markus Heidelberg
> wrote:
>
> > Richard, I hope you can understand that I haven't yet tackled the Readme
> > file. I haven't forgotten it.
>
> Sure, no worries, I know how it is ;)
> There are a few new & interesting patches lis
Richard Hartmann, 22.12.2008:
>
> PS: There is a bug on http://repo.or.cz/w/vim_extended.git
>
> edit and build as usual
> vim; make; make install
> :s_vim_./configure_
The 'vim' command belongs to 'edit' from above. I usually never call
configure directly, make calls it automatically. The 'mak
PS: There is a bug on http://repo.or.cz/w/vim_extended.git
edit and build as usual
vim; make; make install
:s_vim_./configure_
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
On Mon, Dec 22, 2008 at 14:31, Markus Heidelberg
wrote:
> Richard, I hope you can understand that I haven't yet tackled the Readme
> file. I haven't forgotten it.
Sure, no worries, I know how it is ;)
There are a few new & interesting patches listed on Josh's site, maybe
you could merge them, o
Hi,
I have created a branch that contains the latest runtime files fetched
with rsync. This branch can be merged into Vim's source tree (e.g. the
vim branch). That means you can now have a tree with the latest runtime
files COMBINED with your own changes to the runtime files or the changes
to the
10 matches
Mail list logo