On 2018-09-07, Gary Johnson wrote:
> On 2018-09-07, Christ van Willegen wrote:
> > Hi,
> >
> > Perhaps you were bitten by https://github.com/vim/vim/commit/
> > fc65cabb15d0236bce001ad78e12a40511caf941#commitcomment-30321957
> >
> > I don't know if and when Bram has updated this.
>
> That could be the problem. Thank you. However, Bram wrote in the
> comments:
>
> It does work though, and I noticed some people using .tgz when uxing
> bzip2.
> But bzip2 should only be used when it exists.
>
> bzip2 _does_ exist on the systems where this failure occurs.
> I think Bram is incorrect when he says that bzip2 will work for .tgz
> files.
>
> Also, while the autoload/tar.vim file on the systems running Vim
> 8.1.332 looks like the one in the commit, the one on the system
> running 8.1.347 looks significantly different. For example, it
> defines a gzip_command at line 294. I suspect that this is Bram's
> fix, but as I have shown, it doesn't work.
>
> I'm surprised that Bram seems to be the one who updated this file.
> The maintainer is Charles Campbell and Bram usually defers to the
> maintainer for fixes. Further, whoever made these latest changes
> didn't even update the file header with a new date or version
> number, making it difficult to recognize that the file even changed.
It occurred to me that handling gzipped files may be a feature of
only newer versions of bzip2.
On the Red Hat Enterprise Linux Server 7.2 system (I mistakenly
wrote "Fedora" earlier) running Vim 8.1.347, bzip2 is:
bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010.
On the Ubuntu system running Vim 8.1.332, bzip2 is:
bzip2, a block-sorting file compressor. Version 1.0.5, 10-Dec-2007.
Regards,
Gary
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
