unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "David Glasser" <glasser@davidglasser.net>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] support filename prefixes and 100-character filenames in tar-mode.el
Date: Wed, 16 Apr 2008 01:35:44 +0300	[thread overview]
Message-ID: <87y77e28ux.fsf@jurta.org> (raw)
In-Reply-To: <1ea387f60804131848g1becbb24o2cb62fd428ae0f5f@mail.gmail.com> (David Glasser's message of "Sun, 13 Apr 2008 18:48:34 -0700")

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

>> > With all of the patch except for the change in the initial
>>  > initialization of name-end, the results look correct, except the
>>  > penultimate line ends in "foo2" instead of "foo20"; that is because
>>  > the name field here fill the entire field with no nulls, but the code
>>  > previously assumed there would be at least one null.  (It's possible
>>  > that similar adjustments are required for the initial values of
>>  > link-end, gname-end, and uname-end.)
>>
>>  Does your patch also handle @LongLink currently unsupported by tar-mode.el?
>
> Is it actually unsupported?  When I tried to make a tarball to test
> this issue with GNU tar, I saw stuff about "@LongLink" when I opened
> it in tar-mode.  (Try making a tarball from the one I sent using GNU
> tar; you'll see what I mean; I made my test tarball with pax, since
> that was what was used to make the one I opened when I first noticed
> this issue.)  I don't know if it was correct or not, though.

Please see a test tarball attached below.  It is correctly created with
GNU tar, but opening it in Emacs displays the following message:

    Warning: premature EOF parsing tar file

Also its file listing is incomplete, file names are truncated, and content
of some files is inserted into the file listing in the tar-mode buffer.

I thought your patch will fix these problems.


[-- Attachment #2: test.tgz --]
[-- Type: application/x-gtar, Size: 108633 bytes --]

[-- Attachment #3: Type: text/plain, Size: 45 bytes --]


-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2008-04-15 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 17:51 [PATCH] support filename prefixes and 100-character filenames in tar-mode.el David Glasser
2008-04-13 22:23 ` Juri Linkov
2008-04-14  1:48   ` David Glasser
2008-04-15 22:35     ` Juri Linkov [this message]
2008-04-15 23:17       ` David Glasser
2008-04-16 23:17         ` Juri Linkov
2008-04-16 23:32           ` David Glasser
2008-04-17  9:21             ` Juri Linkov
2008-04-17 13:34               ` Chong Yidong
2008-04-22 20:51                 ` Juri Linkov
2008-04-22 21:20                   ` David Glasser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y77e28ux.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=glasser@davidglasser.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).