unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: 57779@debbugs.gnu.org
Subject: bug#57779: 29.0.50; Make thumbs.el obsolete
Date: Tue, 13 Sep 2022 13:30:39 -0400	[thread overview]
Message-ID: <CADwFkmmTE1hCLdn8SqP6ZTLzJKC0TMWTpFN-YBi24T5qSkfpwA@mail.gmail.com> (raw)

Severity: wishlist

In Bug#10758, I argued that:

> I guess we could rebase thumbs.el to also use the built-in image viewing
> support, but I took a look and this external conversion seems built into
> the foundation of how that library works.  So this looks to me like it
> would amount to a rewrite of thumbs.el.  I could be wrong of course, but
> that was my conclusion after poking at it for an hour or so.
>
> Furthermore, at this point, image-dired.el is by far the more powerful
> package, and it seems better implemented overall.  Although it borrows
> heavily from thumbs.el (or at least it used to), thumbs.el seems fully
> redundant these days. ...
>
> So rather than attempting a rewrite of thumbs.el, the better solution
> seems to me to add any important missing features from thumbs.el to
> image-dired.el, and then obsoleting the former (not necessarily in that
> order, but either way is fine to me).
Ref: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10758#26

Now that we have added the `image-dired-wallpaper-set' command to
image-dired, I have a hard time seeing what thumbs.el provides over
Image-Dired.  I don't think it's worthwhile to continue maintaining
both.  Also, thumbs.el has seen very limited development in the last
decade or more.

I therefore suggest that we make thumbs.el obsolete, to better focus our
efforts on image-dired.el.





             reply	other threads:[~2022-09-13 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 17:30 Stefan Kangas [this message]
2022-09-14 12:21 ` bug#57779: 29.0.50; Make thumbs.el obsolete Lars Ingebrigtsen
2022-09-24 12:25   ` Stefan Kangas

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=CADwFkmmTE1hCLdn8SqP6ZTLzJKC0TMWTpFN-YBi24T5qSkfpwA@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=57779@debbugs.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).