From: Eli Zaretskii <eliz@gnu.org>
To: LinSun <lin.sun@zoom.us>
Cc: sunlin7@yahoo.com, 47119@debbugs.gnu.org
Subject: bug#47119: 28.0.50; [patch][Dired] new user option for compressing dir suffix
Date: Mon, 22 Mar 2021 19:43:41 +0200 [thread overview]
Message-ID: <83pmzr9j8y.fsf@gnu.org> (raw)
In-Reply-To: <6ECADB20-F129-4024-982B-0236A5C3E719@hxcore.ol> (message from LinSun on Mon, 22 Mar 2021 20:28:48 +0800)
> Date: Mon, 22 Mar 2021 20:28:48 +0800
> From: LinSun <lin.sun@zoom.us>
> Cc: "47119@debbugs.gnu.org" <47119@debbugs.gnu.org>,
> "sunlin7@yahoo.com" <sunlin7@yahoo.com>
>
> >> - ("\000" ".tar.gz" "tar -cf - %i | gzip -c9 > %o"))
>
> >Why did you remove the "\000" entry? As the comment explains, it is
>
> >there to allow compressing a directory. To compress a directory, you
>
> >need to run 'tar' on it first, and the .tar.gz/.tar.xz entries run
>
> >'tar' on the _result_ of gzip/xz instead. So how will compression of
>
> >directories work after your changes? I feel that I'm missing
>
> >something here, but what?
>
> The “\000” entry is special for compress directory, if you go through back, other entries in the
> `dired-compress-file-suffixes` is decompress commands. After apply this patch, the “\000” entry is useless.
I'm still missing something, I think. Please describe step by step
how compressing a directory will work after your changes, and in
particular what shell command(s) will Dired run in that case.
Thanks.
next prev parent reply other threads:[~2021-03-22 17:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 3:55 bug#47119: 28.0.50; [patch][Dired] new user option for compressing dir suffix Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 7:37 ` Eli Zaretskii
2021-03-13 7:50 ` Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-18 15:41 ` bug#47119: " Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-20 10:37 ` Eli Zaretskii
2021-03-22 12:28 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 17:43 ` Eli Zaretskii [this message]
2021-03-23 3:00 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-18 15:41 ` bug#47119: " Lin Sun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-02 0:57 ` Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-17 16:04 ` Lars Ingebrigtsen
2021-05-18 1:21 ` Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-18 14:55 ` Glenn Morris
2021-05-18 15:49 ` Lars Ingebrigtsen
2021-05-19 0:12 ` Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-19 15:47 ` Glenn Morris
2021-05-20 10:20 ` LinSun via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-25 4:56 ` Lars Ingebrigtsen
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=83pmzr9j8y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47119@debbugs.gnu.org \
--cc=lin.sun@zoom.us \
--cc=sunlin7@yahoo.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).