unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Swaroop C H <swaroop@swaroopch.com>
To: 15619@debbugs.gnu.org
Subject: bug#15619: M-x list-packages should also show link to homepage / source
Date: Tue, 15 Oct 2013 09:48:52 +0530	[thread overview]
Message-ID: <85D01BD8-A634-4AAB-A475-B1D54AE8C1A4@swaroopch.com> (raw)

Hello,

I hope this is the right forum for this question, please direct me if otherwise.

When I run ~M-x list-packages~, and click on a package name, the description is usually vague on what it means, and it would be great if there was a link to the source / github link (just like the website http://melpa.milkbox.net/ displays the Source column)  so that I can understand what it actually does.

For example, ~pony-mode~ says "Minor mode for working with Django projects [github]" and that ~[github]~ doesn't actually link to anything and that description is not helpful to what it actually does.

Further examples (as pointed out by jlf on freenode.net#emacs IRC) are "lisp-editing" which says "lisp editing tools" in the description and "fuzzy-match" which says "fuzzy matching [wiki]" in the description.

This is definitely not nitpicking about those packages, but a request that there be a standard homepage / source (github, etc.) link in the description for each package, similar to how HomeBrew package manager on OS X works.

Thank you!

Regards,
Swaroop






             reply	other threads:[~2013-10-15  4:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15  4:18 Swaroop C H [this message]
2013-10-15  6:31 ` bug#15619: M-x list-packages should also show link to homepage / source Glenn Morris
2013-10-15  6:36   ` Swaroop C H
2013-10-15  6:41     ` Glenn Morris
2013-10-15 13:44     ` Dmitry Gutov
2013-10-15 14:54       ` Glenn Morris
2013-10-16  0:22         ` Dmitry Gutov

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=85D01BD8-A634-4AAB-A475-B1D54AE8C1A4@swaroopch.com \
    --to=swaroop@swaroopch.com \
    --cc=15619@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).