From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: schwab@suse.de, emacs-pretest-bug@gnu.org
Subject: Re: 23.0.50; Possible bug with bzip2 compressed tar files?
Date: Sat, 12 Jan 2008 18:23:06 +0200 [thread overview]
Message-ID: <umyrbqahh.fsf@gnu.org> (raw)
In-Reply-To: <8F7B3701-FC80-4688-AE92-C9F5F42D3FA1@Freenet.DE> (message from Peter Dyballa on Sat, 12 Jan 2008 17:03:11 +0100)
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> Date: Sat, 12 Jan 2008 17:03:11 +0100
> Cc: schwab@suse.de, emacs-pretest-bug@gnu.org
>
>
> Am 12.01.2008 um 16:56 schrieb Eli Zaretskii:
>
> >> I do not see the archive's structure/elements, I get only a
> >> presentation of binary characters starting with BZh.
> >
> > Anything interesting in *Messages*?
>
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Mark set
> Mark saved where search started
> File OmniWeb-5.7-r97021-Alpha.tbz2 is large (14MB), really open? (y
> or n)
> View mode: type C-h for help, h for commands, q to quit.
>
> is all.
>
> >
> > Also, what happens if you set debug-on-error non-nil?
>
>
> Nothing more. There does not seem to be a real error from this file:
>
> -rw-r--r-- 1 pete pete 15234352 10 Jan 22:59 OmniWeb-5.7-
> r97021-Alpha.tbz2
.tbz2? I don't think Emacs automatically tries to un-bzip2 and untar
that, does it? Does it help to tweak jka-compr-compression-info-list?
next prev parent reply other threads:[~2008-01-12 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 14:12 23.0.50; Possible bug with bzip2 compressed tar files? Peter Dyballa
2008-01-12 14:25 ` Andreas Schwab
2008-01-12 15:14 ` Peter Dyballa
2008-01-12 15:56 ` Eli Zaretskii
2008-01-12 16:03 ` Peter Dyballa
2008-01-12 16:23 ` Eli Zaretskii [this message]
2008-01-12 19:41 ` Peter Dyballa
2008-01-14 22:22 ` Peter Dyballa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=umyrbqahh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Peter_Dyballa@Freenet.DE \
--cc=emacs-pretest-bug@gnu.org \
--cc=schwab@suse.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.