Gary Johnson wrote:
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard).
Gary Johnson schrieb:
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard).
WinZip (for instance) can uncompress .gz files as an easy preliminary step.
7zip[1], which is GPL licensed, handles all formats well.
The point was though that vimballs cannot readily include binary data
which isn't all wrong I think.
[1] http://www.7-zip.org
Charles E. Campbell, Jr. schrieb:
Gary Johnson wrote:
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft
On 12/02/09 21:52, Andy Wokula wrote:
Charles E. Campbell, Jr. schrieb:
Gary Johnson wrote:
On 2009-02-12, Tony Mechelynckantoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix
On Tue, Feb 10, 2009 at 9:48 PM, Charles E. Campbell, Jr. wrote:
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
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
installing zip-based plugins basically is a matter of
exec '!unzip '. shellescape(expand('%')) .' -d ~/vimfiles'
On Wed, Feb 11, 2009 at 11:06 AM, Tom Link micat...@gmail.com wrote:
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
IMHO reliance on compiled-in +python support
On 11/02/09 03:48, Charles E. Campbell, Jr. wrote:
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
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim handle it specially.
The change would be transparent to
On 11/02/09 06:42, Tom Link wrote:
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
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard). And note that if
the
On Wed, Feb 11, 2009 at 7:29 PM, Tony Mechelynck wrote:
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim
Gary Johnson wrote:
On 2009-02-12, Tony Mechelynck antoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough standard).
On 12/02/09 02:07, Gary Johnson wrote:
On 2009-02-12, Tony Mechelynckantoine.mechely...@gmail.com wrote:
And then there are people like me who can un- .zip files if they have
to, but prefer to gunzip them (un- .gz), which is the Unix standard (as
opposed to the Microsoft Megabucks LoseDough
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
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
20 matches
Mail list logo
