GNU bug report logs - #38647
26.3; image-next-file does not consider archived images

Previous Next

Full log

Message #13 received at 38647 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 38647 <at> debbugs.gnu.org, ynyaaa <at> gmail.com
Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images
Date: Sun, 02 Aug 2020 11:49:11 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> When viewing archived images(zip or tar) with image-mode,
>> typing 'n' does not show the next image in the archive.
>> Similar for 'p'.
>
> Sounds like a missing feature which would be good to have, thanks.
>
> Any takers?

There's some difficulty knowing how to approach this -- the different
archive modes do so many different odd things.

For instance, if you open the file "guide.png" from a zip buffer,
buffer-file-name ends up being:

"/home/larsi/tmp/images.zip:guide.png"

In a tar file buffer, you end up with:

"/home/larsi/tmp/images.tgz!./guide.png"

So that has to be regularised first...  but will that break stuff?

Secondly, there doesn't seem to be any general "what's the next file in
this archive buffer" function?  Or am I missing something?

This seems like a trivial request, but I'm not sure we have the
infrastructure to make it happen...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.