Ben Fritz wrote:
I just realize my patch doesn't handle the g:html_no_pre option. I'll
make another patch in the next day or two to also handle this option
(I notice I'll need to get the latest from FTP again).
Bram, once I fix the handling of g:html_no_pre, is there a reason not
to
Hi folks,
Maybe somebody has some use for this. I wrote a small ruby script that
allows the creation of vimballs (plain text or gzipped) from the
command line. It's still young and fresh and experimental. I ran it
over my own plugins and the generated vimballs are identical to those
created by
On Tue, Feb 10, 2009 at 12:53:15PM -0800, Tom Link wrote:
Maybe somebody has some use for this. I wrote a small ruby script that
allows the creation of vimballs (plain text or gzipped) from the
command line.
I'm still curious what purpose vimballs serve over a standard archive
format like zip
On Tue, Feb 10, 2009 at 4:35 PM, Charles Campbell wrote:
James Vega wrote:
I'm still curious what purpose vimballs serve over a standard archive
format like zip or tar.gz. From a distribution perspective, all they've
done is made my work harder when trying to include vim scripts in a
Hi and thanks for giving the git repo a try.
_sc_, 06.02.2009:
FIVE
line 139
git mergetool
showed nothing that needed to be fixed
This is only needed, if merge conflicts arise. You will notice it, if
it's the case.
lines 147-232 of the README detail a merge of runtime files that
_sc_, 07.02.2009:
On Friday 06 February 2009 4:09 pm, Matt Wozniski wrote:
and my .git/config contains:
Somehow, you're missing this:
[branch custom]
remote = origin
merge = refs/heads/vim-with-runtime
and adding that in should make things work just fine...
_sc_, 05.02.2009:
since the patch no longer works i'd recommend an update to
vim's patch page:
http://groups.google.com/group/vim_dev/web/vim-patches
which still contains a link to
http://groups.google.com/group/vim_dev/browse_thread/thread/a6dd45468531f4e#msg_10fa0944a8b643b4
Sure.
Christian MICHON, 06.02.2009:
On Thu, Feb 5, 2009 at 10:23 PM, Markus Heidelberg
markus.heidelb...@web.de wrote:
What do you think about the commit message format, is it ok? I searched
for a git-like message, without losing information. The duplicated first
line of the problem
James Vega, 06.02.2009:
On Thu, Feb 05, 2009 at 10:23:33PM +0100, Markus Heidelberg wrote:
What do you think about the commit message format, is it ok? I searched
for a git-like message, without losing information. The duplicated first
line of the problem description is unavoidable I
Matt Wozniski wrote:
But let's not forget that they have significant disadvantages, too...
Vimballs made with new versions of the plugin don't work on older
vims.
There's been one problem with that -- 7.0 vimball doesn't handle the later
vimball versions. 7.1 and has been compatible; newer
On 2/11/09, Tom Link micat...@gmail.com wrote:
Hi folks,
Maybe somebody has some use for this. I wrote a small ruby script that
allows the creation of vimballs (plain text or gzipped) from the
command line. It's still young and fresh and experimental. I ran it
over my own plugins and
You can specify the base path with the final arg to MkVimball.
If you wanted to create vimballs from cygwin bash by calling Windows
gvim (you could of course use cygwin's vim but ...), you'd have to
convert the path which works most of the time but can be cumbersome.
But thanks for reminding me
12 matches
Mail list logo
