unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alan@idiocy.org, 25076@debbugs.gnu.org
Subject: bug#25076: 24.5; Enhancement request: Make `archive-mode' more Dired like (sorting etc.)
Date: Fri, 2 Dec 2016 08:13:00 -0800 (PST)	[thread overview]
Message-ID: <e46970c9-fa6b-4558-b9eb-85bc5f380e83@default> (raw)
In-Reply-To: <83shq6ol7x.fsf@gnu.org>

> > > > Subject line says it all.  `archive-mode' still seems pretty
> > > > rudimentary.  It would be good to at least be able to sort the
> > > > lines by file name etc.
> > >
> > > I’m wondering if it wouldn’t be smarter to actually use dired to
> > > access archives, like how we can use dired to access remote
> > > directories through tramp.
> > >
> > > I expect this is probably a much bigger/harder job than I
> > > imagine, but what would be required? Just a function that
> > > could produce ls style output for archives?
> >
> > I can't speak to that question.  I suggest that you file a
> > separate enhancement request for it.  If it turns out that
> > it is trivial then the two bugs can be merged - I don't have
> > any objection to being able to use Dired (completely) for archives.
> >
> > But no, it is not just a question of producing an ls-style
> > listing. The various Dired operations available currently
> > expect a file as target.
> 
> Then one almost obvious solution is to unpack the archive under
> temporary-file-directory, and invoke Dired on that.

Yes.  And that is what I've done, manually.  I think wrapping
that up so that it happens transparently is probably the best
solution.

> In any case, IMO adding such a feature (which I agree should be
> nice) is out of scope of archive-mode, as it is designed.  Its
> basic design is to show you the archive as it is on disk, with
> no changes.  The file listing you are looking at in archive-mode
> is in most cases a specially-formatted TOC that is recorded in
> the archive.  Changing its order means changing the archive itself,
> which is not what the request wants, AFAIU.

I think you're right.

> So if Dired on a temporary copy is not a good solution for some
> reason, I guess we need a new mode, which will reuse some basic
> capabilities of archive-mode, but otherwise be designed similarly
> to Dired.

I think opening Dired on a temporary extraction is probably the
way to go.  Do you want to rename this enhancement request to that
effect, or do you want a new request for that?

Once that is available, a question will be whether, by default,
`dired-find-file' and `find-file' should open an archive file in
archive mode or should open Dired on (a temporary extraction of) it.





  reply	other threads:[~2016-12-02 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 18:36 bug#25076: 24.5; Enhancement request: Make `archive-mode' more Dired like (sorting etc.) Drew Adams
2016-12-01 19:57 ` Alan Third
2016-12-01 20:14   ` Drew Adams
2016-12-02  7:15     ` Eli Zaretskii
2016-12-02 16:13       ` Drew Adams [this message]
2016-12-02 16:19         ` Eli Zaretskii
2016-12-02  8:47   ` Michael Albinus
2022-02-03 20:38     ` Lars Ingebrigtsen
2022-02-03 23:14       ` Kévin Le Gouguec
2022-02-05  6:27         ` Lars Ingebrigtsen
2022-02-05 16:02           ` bug#25076: [External] : " Drew Adams
2016-12-04 18:43 ` bug#25076: One possible solution: dired-avfs Hong Xu
     [not found] <<f8857e59-0d22-4983-925f-b36783cea015@default>
     [not found] ` <<20161201195707.GA15995@breton.holly.idiocy.org>
     [not found]   ` <<411373d3-f941-492c-ac17-8d1786ed7c58@default>
     [not found]     ` <<83shq6ol7x.fsf@gnu.org>
     [not found]       ` <<e46970c9-fa6b-4558-b9eb-85bc5f380e83@default>
     [not found]         ` <<83bmwumhgc.fsf@gnu.org>
2016-12-02 16:24           ` bug#25076: 24.5; Enhancement request: Make `archive-mode' more Dired like (sorting etc.) Drew Adams

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=e46970c9-fa6b-4558-b9eb-85bc5f380e83@default \
    --to=drew.adams@oracle.com \
    --cc=25076@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.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 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).