From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 5475@debbugs.gnu.org, cyd@stupidchicken.com
Subject: bug#5475: Archives with filenames with square brackets
Date: Fri, 29 Jan 2010 00:00:11 +0200 [thread overview]
Message-ID: <83636lubys.fsf@gnu.org> (raw)
In-Reply-To: <e01d8a51001281324w343c5b96oa6d454c8389b1570@mail.gmail.com>
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Thu, 28 Jan 2010 22:24:50 +0100
> Cc: Chong Yidong <cyd@stupidchicken.com>, 5475@debbugs.gnu.org
>
> On Thu, Jan 28, 2010 at 10:05 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Chong Yidong <cyd@stupidchicken.com>
> >> Cc: juri@jurta.org, 5475@debbugs.gnu.org
> >> Date: Thu, 28 Jan 2010 15:07:09 -0500
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> >> Well, archive-zip-extract already branches for pkzip/unzip
> >> >
> >> > Yes, but it does that by a user option, not by some hidden knowledge.
> >> > I won't mind introducing a similar option that would tell arc-mode to
> >> > quote the file arguments.
> >>
> >> Right, but once the user tells arc-mode to use unzip, we can
> >> automagically shell-quote the filename; there seems to be no reason not
> >> to.
>
>
> Excuse me, I did not follow this thread at all, but I get curious.
> What does shell-quote have to do with the arc-mode library? Does it
> use a shell at all?
No, it doesn't use the shell. But "unzip" expands wildcards
internally, so wildcard characters need to be quoted if a file
includes them literally.
> Now that 7-zip is available on GNU/Linux too wouldn't it be very good
> to include support for it?
Patches are always welcome.
next prev parent reply other threads:[~2010-01-28 22:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 17:48 bug#5475: Archives with filenames with square brackets Juri Linkov
2010-01-26 21:05 ` Chong Yidong
2010-01-26 21:47 ` Eli Zaretskii
2010-01-27 16:57 ` Chong Yidong
2010-01-27 17:35 ` Eli Zaretskii
2010-01-28 20:07 ` Chong Yidong
2010-01-28 21:05 ` Eli Zaretskii
2010-01-28 21:24 ` Lennart Borgman
2010-01-28 22:00 ` Eli Zaretskii [this message]
2010-01-30 22:59 ` Juri Linkov
2010-01-31 4:18 ` Eli Zaretskii
2010-01-31 10:56 ` Juri Linkov
2010-01-31 18:04 ` Eli Zaretskii
2010-01-31 21:59 ` Juri Linkov
2010-02-01 4:15 ` Eli Zaretskii
2010-02-01 10:34 ` Juri Linkov
2010-02-01 11:48 ` Lennart Borgman
2010-02-01 15:43 ` Stefan Monnier
2010-02-01 21:55 ` Juri Linkov
2010-02-02 0:11 ` Lennart Borgman
2010-02-02 0:46 ` Juri Linkov
2010-02-02 4:03 ` Eli Zaretskii
2010-04-18 23:14 ` Juri Linkov
2010-02-01 19:49 ` Eli Zaretskii
2010-02-01 21:21 ` Drew Adams
2010-02-01 21:52 ` Eli Zaretskii
2010-02-01 22:04 ` Drew Adams
2010-02-01 22:39 ` Juri Linkov
2010-02-01 22:41 ` Lennart Borgman
2010-02-02 0:10 ` Lennart Borgman
2010-02-02 0:42 ` Juri Linkov
2010-02-02 1:30 ` Lennart Borgman
2010-02-02 10:03 ` Juri Linkov
2010-02-03 0:17 ` Lennart Borgman
2010-02-03 0:35 ` Juri Linkov
2010-02-03 23:54 ` Juri Linkov
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=83636lubys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5475@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=lennart.borgman@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).