unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: lockywolf@gmail.com, 44753@debbugs.gnu.org
Subject: bug#44753: 27.1; arc-mode does not extract marked files
Date: Fri, 20 Nov 2020 13:50:33 +0200	[thread overview]
Message-ID: <83wnygz1py.fsf@gnu.org> (raw)
In-Reply-To: <87sg94ied8.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  20 Nov 2020 10:09:23 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Vladimir Nikishkin <lockywolf@gmail.com>,  44753@debbugs.gnu.org
> Date: Fri, 20 Nov 2020 10:09:23 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > We need first to add a capability to extract archive members to files.
> 
> This was added to the trunk in August.

You are right, I forgot about that, sorry.

However, the implementation of archive-copy-file doesn't seem to be
easily scalable to what Vladimir requested.  It is also sub-optimal
(to say the least) to extract files by going through a temporary
buffer, since every archive type has some way of extracting files
directly.  If nothing else, this will cause serious problems with
encoding, especially when several files are extracted at once that
happen to be encoded differently.  And the speed will also be much
slower than if we use the archiver program to do the extraction.





  reply	other threads:[~2020-11-20 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  3:23 bug#44753: 27.1; arc-mode does not extract marked files Vladimir Nikishkin
2020-11-20  8:07 ` Eli Zaretskii
2020-11-20  9:09   ` Lars Ingebrigtsen
2020-11-20 11:50     ` Eli Zaretskii [this message]
2020-11-24  6:06       ` Lars Ingebrigtsen
2020-11-24 15:33         ` Eli Zaretskii
2020-11-20  9:18   ` Vladimir Nikishkin
2020-11-24  7:46 ` Lars Ingebrigtsen
2020-11-24  8:01   ` Vladimir Nikishkin

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=83wnygz1py.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44753@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=lockywolf@gmail.com \
    /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).