I know what tar is, but I had no idea that vim would happily
decompress for me.  That's pretty cool (always nice to learn something
unexpected).  As soon as I through cat at it I found out that you're
absolutely right (I suppose you already knew that).  I've been working
with Linux for a few years now - as an enthusiast, not a professional
- and I've never seen a file gzipped outside of a tarball so I wasn't
looking for it.

Anyway, after decompressing the file and piping it to a new file
called trac-post-commit-hook, guess what?  It worked.  Flawlessly.
Now, if you don't mind, I have a couple of other general questions:

1.  Is there any convention/best practice that indicates where a
post-commit hook script should be stored?  It will work anywhere, I
know, but is there a recommendation?

2.  Since the post-commit-hook file that gets executed lives in the
project's /hooks directory and must be named post-commit...I assume
you can have multiple post-commit scripts executed just by calling all
scripts from that same hook file.  Is there any problem with that or
is it done pretty regularly?

Thanks again for all of your help.  Without it, I would have probably
just decided it wasn't worth the hassle.  Now that I have it working,
though...I'm not sure I could live without it.

On 7/25/06, Emmanuel Blot <[EMAIL PROTECTED]> wrote:
> Hmmm.  Didn't try file.  I initially tried to list the contents
> through "tar -ztvf", but it told me it wasn't a compressed file.

tar is an archive tool, not a compression tool
tar tzvf is equivalent to
gunzip -c <file> | tar tvf -

> Then, just for kicks, I tried opening it in vi and there it was - nice
> and textual.  I'll run "file" on it as soon as I get to the office and
> let you know.

vim is clever enough to uncompress a gzipped file on-the-fly: it will
show you the gunzipped content of the file, this does not tell you
whether the file is gzipped or not.

use "cat" if you do not have "file"; cat does not gunzip, so if the
file is actually gzipped, you should get some garbage as output.
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac



--

Rob Wilkerson
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac

Reply via email to