bug#15619: M-x list-packages should also show link to homepage / source

bug#15619: M-x list-packages should also show link to homepage / source

[Swaroop C H]

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

bug#15619: M-x list-packages should also show link to homepage / source

[Glenn Morris]

Swaroop C H wrote:

> 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.

This is absolutely the right forum, but a trivial check will show that
the same issue was already reported and recently implemented.

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13291

bug#15619: M-x list-packages should also show link to homepage / source

[Swaroop C H]

On 15-Oct-2013, at 12:01 PM, Glenn Morris <rgm@gnu.org> wrote:
> This is absolutely the right forum, but a trivial check will show that
> the same issue was already reported and recently implemented.
> 
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13291

Hi Glenn,

Apologies for the redundant request, apparently, my searching skills are not good, I did actually try searching the archives ( http://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3Apackage+URL;package=emacs shows nothing? )

Glad to hear that this has already been resolved for future versions of Emacs!

Regards,
Swaroop

bug#15619: M-x list-packages should also show link to homepage / source

[Glenn Morris]

Swaroop C H wrote:

> Apologies for the redundant request, apparently, my searching skills are not good, I did actually try searching the archives ( http://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3Apackage+URL;package=emacs shows nothing? )

That searches for the literal string "package+URL".

bug#15619: M-x list-packages should also show link to homepage / source

[Dmitry Gutov]

Swaroop C H <swaroop@swaroopch.com> writes:
> Glad to hear that this has already been resolved for future versions of Emacs!

Each package repository also has to implement support for it.

For MELPA, check out https://github.com/milkypostman/melpa/issues/424

bug#15619: M-x list-packages should also show link to homepage / source

[Glenn Morris]

Dmitry Gutov wrote:

> Swaroop C H <swaroop@swaroopch.com> writes:
>> Glad to hear that this has already been resolved for future versions of Emacs!
>
> Each package repository also has to implement support for it.

Where's the NEWS entry informing people of this, then?

bug#15619: M-x list-packages should also show link to homepage / source

[Dmitry Gutov]

On 15.10.2013 18:54, Glenn Morris wrote:
>> Each package repository also has to implement support for it.
>
> Where's the NEWS entry informing people of this, then?

Added in 114675, feel free to edit as you see fit.

If most people read NEWS after the release, though, which is my 
understanding, it will be rather late to work on the implementations.