From: Dmitry Gutov <dgutov@yandex.ru>
To: jeremiah.dodds@gmail.com
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: GNU ELPA visibility
Date: Fri, 26 Oct 2012 20:10:58 +0400 [thread overview]
Message-ID: <508AB612.3010000@yandex.ru> (raw)
Tassilo Horn <tsdh@gnu.org> writes:
> Jeremiah Dodds <jeremiah.dodds@gmail.com> writes:
>
>>> When looking for an Elisp package or feature, most people reach for
>>> their browser before reaching for M-x list-packages. But packages
>>> distributed via GNU ELPA won't show up because they're not visible to
>>> search engines.
>>
>> I think it's very likely that M-x list-packages will get much more
>> common as time progresses. It's certainly the first thing that I go to
>> nowadays.
>
> Ditto, but the package explanations given there are far from informative
> enough to find the package you need for your task at hand. I look there
> first, but then google up the packages that sound relevant, and in the
> end that almost always leads to emacswiki.
>
> It would be good if every package would at least complement Version and
> Summary with a longer description, a link to its homepage (or emacswiki
> page if it has no homepage), and the date when it was updated the last
> time.
You may find that, for single-file packages, even if they provide an
extended "Commentary" section, it will not show up in the
"list-packages" interface. At least when distributed over MELPA or
Marmalade.
I think it's fixed in Daniel Haxney's package.el fork, though.
Showing a link to the homepage (taken from the "URL" header) would be a
welcome addition to the interface, too.
--Dmitry
next reply other threads:[~2012-10-26 16:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 16:10 Dmitry Gutov [this message]
2012-10-26 18:31 ` GNU ELPA visibility Stefan Monnier
2012-10-26 18:53 ` chad
2012-10-26 19:11 ` Stefan Monnier
2012-10-27 5:18 ` Chong Yidong
2012-10-27 11:26 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2012-11-02 18:47 Dmitry Gutov
2012-10-28 20:26 Dmitry Gutov
2012-10-28 16:29 Daniel Hackney
2012-10-28 16:47 ` Eli Zaretskii
2012-10-28 18:23 ` Andreas Schwab
2012-10-25 22:14 Dmitry Gutov
2012-10-25 22:47 ` Jorgen Schaefer
2012-10-25 21:23 Dmitry Gutov
2012-10-25 21:34 ` Drew Adams
2012-10-25 21:47 ` Dmitry Gutov
2012-10-25 21:52 ` Drew Adams
2012-10-26 1:37 ` Stefan Monnier
2012-10-25 21:48 ` Jorgen Schaefer
2012-10-25 19:58 Dmitry Gutov
2012-10-25 21:10 ` Stefan Monnier
2012-10-25 19:30 Stefan Monnier
2012-10-25 20:04 ` Jeremiah Dodds
2012-10-25 20:18 ` Drew Adams
2012-10-26 7:29 ` Tassilo Horn
2012-10-27 6:33 ` Bastien
2012-10-26 4:22 ` Jambunathan K
2012-10-27 6:39 ` Bastien
2012-11-01 4:33 ` Stefan Monnier
2012-11-01 5:10 ` Jambunathan K
2012-11-01 5:13 ` chad
2012-11-01 5:18 ` Jambunathan K
2012-11-01 12:42 ` Stefan Monnier
2012-11-02 7:12 ` Daniel Hackney
2012-11-02 7:48 ` Jorgen Schaefer
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=508AB612.3010000@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jeremiah.dodds@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
/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).