From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44753@debbugs.gnu.org
Subject: bug#44753: 27.1; arc-mode does not extract marked files
Date: Tue, 24 Nov 2020 16:01:15 +0800 [thread overview]
Message-ID: <CA+A2iZaXF4OjpcTLuA+ZN9ueqcqWqGbzME=7JXM6ZC1ATMzffA@mail.gmail.com> (raw)
In-Reply-To: <87k0ub8aef.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Awesome, thanks. I expected... well, maybe, mistakenly, the buffer to
behave roughly like a dired buffer.
--
Yours sincerely, Vladimir Nikishkin
(Sent with Google mail mobile.)
Lars Ingebrigtsen <larsi@gnus.org> 于 2020年11月24日周二 15:46写道:
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
> > What I do is I visit an archive, mark entries with `m', which adds an
> > asterisk next to their name, and then type `e' or `f', expecting to be
> > asked for a directory name to extract these files to.
>
> I'm not quite sure why you'd expect that -- the doc string of these
> commands say "In archive mode, extract this entry of the archive into
> its own buffer."
>
> In any case, in Emacs 28, there's a new `C' command that'll extract
> archive members and write them to disk. I've now adjusted the command
> so that it'll respect the marked files.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 1576 bytes --]
prev parent reply other threads:[~2020-11-24 8:01 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
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 [this message]
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='CA+A2iZaXF4OjpcTLuA+ZN9ueqcqWqGbzME=7JXM6ZC1ATMzffA@mail.gmail.com' \
--to=lockywolf@gmail.com \
--cc=44753@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.