From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 61639@debbugs.gnu.org
Subject: bug#61639: 30.0.50; [PATCH] Do not error out on non image file in image-dired
Date: Mon, 20 Feb 2023 16:45:04 +0200 [thread overview]
Message-ID: <83a618v1jj.fsf@gnu.org> (raw)
In-Reply-To: <87k00ctofi.fsf@ledu-giraud.fr> (message from Manuel Giraud on Mon, 20 Feb 2023 15:13:37 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: 61639@debbugs.gnu.org
> Date: Mon, 20 Feb 2023 15:13:37 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So maybe "C-t d" should filter the selected "images" before it calls
> > the function which errors out?
>
> That is what `image-dired-show-all-from-dir' is doing: it selects files
> from the given directory with the correct "image files" regexp and so no
> non image will be present.
>
> So your idea is to keep `image-dired--get-create-thumbnail-file' as is
> and filter its input in `image-dired-display-thumbs'? But then we won't
> get any message or error that something was not an image (this could go
> unnoticed as well ;-)
I don't necessarily see a reason to alert the user in this case, but
if you think we had better done that, we could show a message when we
find a non-image file in the list of the selected ones.
> > IOW, if the application doesn't want an API to fail for reasons
> > specific to the application, the onus of avoiding the error is on the
> > application, no?
>
> Yes, but maybe `image-dired--get-create-thumbnail-file' is not really an
> established API. It is called twice in Emacs (and the other place it is
> called non images are already filtered out).
>
> Do you think it could have been used in third-party package?
That's not what bothers me. What bothers me is that we burden a
low-level API with considerations whose source is the application.
next prev parent reply other threads:[~2023-02-20 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 20:09 bug#61639: 30.0.50; [PATCH] Do not error out on non image file in image-dired Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 12:49 ` Eli Zaretskii
2023-02-20 13:35 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 13:46 ` Eli Zaretskii
2023-02-20 14:13 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 14:45 ` Eli Zaretskii [this message]
2023-02-20 16:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-21 12:01 ` Eli Zaretskii
2023-02-21 12:16 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-21 13:03 ` Eli Zaretskii
2023-02-21 14:23 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 13:22 ` Eli Zaretskii
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=83a618v1jj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61639@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).