unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "Elijah G." <eg642616@gmail.com>, 71180@debbugs.gnu.org
Cc: Philip Kaludercic <philipk@posteo.net>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#71180: [ELPA Feature Request] Package thumbnail
Date: Sun, 26 May 2024 02:23:36 -0700	[thread overview]
Message-ID: <CADwFkmmeoSr_N9=t2rFF_Hc7hCwB9-Di-STH+VBDysqGrc5NcQ@mail.gmail.com> (raw)
In-Reply-To: <86a5ken8py.fsf@gmail.com>

tags 71180 - notabug
severity 71180 wishlist
thanks

"Elijah G." <eg642616@gmail.com> writes:

> Tags: notabug
>
> Hi, i'm wondering if would be a good idea add support for thumbnail for
> elpa packages (for elpa website and package-menu *Help* buffers).
> I think this is a missing feature that most other editors and non-editors
> does (such as synaptic and vscodium).
>
> My idea is to only support 1 image (jpg or png, adding more than 1
> thumbnail would be hard to read the package *Help* buffer) and resize it
> (if possible) for not take all the buffer size.
>
> For packages developers i think would be fine define new header comment
> line for let them to choose which image they want to use, something like:
> ;;; Thumbnail: ./image.png
>
> Thanks.

I think this could be a good idea, but it would also depend on how the
idea is executed.  We would obviously need knobs to turn it off, the
feature would need to be tested on text displays, etc.

Instead of a header comment, we could just say that the thumbnail should
always be called "thumb.png" and be in the root directory of the
package, or something along those lines.





  reply	other threads:[~2024-05-26  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 22:30 bug#71180: [ELPA Feature Request] Package thumbnail Elijah G.
2024-05-26  9:23 ` Stefan Kangas [this message]
2024-05-26 11:01   ` Philip Kaludercic
2024-05-27 18:08     ` Elijah G.
2024-05-28  6:21       ` Philip Kaludercic
2024-05-30  3:10         ` Elijah G.
2024-06-02 19:41           ` Philip Kaludercic
2024-05-27  2:15   ` Elijah G.

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='CADwFkmmeoSr_N9=t2rFF_Hc7hCwB9-Di-STH+VBDysqGrc5NcQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=71180@debbugs.gnu.org \
    --cc=eg642616@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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).