From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38647@debbugs.gnu.org, ynyaaa@gmail.com
Subject: bug#38647: 26.3; image-next-file does not consider archived images
Date: Wed, 05 Aug 2020 02:47:44 +0300 [thread overview]
Message-ID: <87lfiuq6w7.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zh7au97q.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 04 Aug 2020 10:05:45 +0200")
>> All this indicates that instead of using 'directory-files',
>> 'image-next-file' should rely on 'archive-next-line' if the file
>> is opened from an archive, and on 'dired-next-line' otherwise.
>
> `archive-next-line' isn't used in tar mode buffers -- that's the
> problem: There's no unified interface across the different archive
> modes. (Although perhaps there's just two? arc-mode and tar-mode?
Yep, there's just two - these twins are going hand in hand,
for example, in image-mode.el in image-toggle-display-image:
(not (and (boundp 'archive-superior-buffer)
archive-superior-buffer))
(not (and (boundp 'tar-superior-buffer)
tar-superior-buffer))
>> Also this means that if there is no corresponding dired buffer
>> already visited, then 'image-next-file' should create an internal
>> dired buffer just for the sake of file image navigation.
>
> Hm. I think that makes sense... but it would perhaps be a bit
> surprising?
Maybe when not requested, such Dired buffer should be killed afterwards,
or its name should start with a space.
next prev parent reply other threads:[~2020-08-04 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 7:15 bug#38647: 26.3; image-next-file does not consider archived images ynyaaa
2019-12-17 16:20 ` Eli Zaretskii
2020-08-02 9:49 ` Lars Ingebrigtsen
2020-08-03 23:50 ` Juri Linkov
2020-08-04 8:05 ` Lars Ingebrigtsen
2020-08-04 23:47 ` Juri Linkov [this message]
2020-08-05 9:09 ` Lars Ingebrigtsen
2020-08-05 23:50 ` Juri Linkov
2020-08-06 9:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfiuq6w7.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=38647@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=ynyaaa@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 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.