From: Jambunathan K <kjambunathan@gmail.com>
To: "T.V. Raman" <tv.raman.tv@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Jeremiah Dodds <jeremiah.dodds@gmail.com>,
emacs-devel@gnu.org
Subject: Re: list-packages: Marking packages as "uninteresting"?
Date: Tue, 22 May 2012 18:26:33 +0530 [thread overview]
Message-ID: <81bolgxtku.fsf@gmail.com> (raw)
In-Reply-To: <CADkJX2iPhvxvdqocb3tn-oxyWdnCif4N5L=7nUdzx1zyFZ88jg@mail.gmail.com> (T. V. Raman's message of "Tue, 22 May 2012 01:00:32 -0700")
> Enabling users to add a tag would be the most flexible approach.
>
> I am not a huge fan of categorization as a solution to all evils,
> because it's basically a case of shoving things into drawers --
> and then later not knowing what drawer you stuck it into. Emacs
> with incremental seach makes such things unnecessary:-) So if we
> do categorize and collapse things based on catagorization, let's
> implement that using invisibility specs since that works with
> isearch --- so I wouldn't need to know if you stuck say
> "org-mode" in the authoring drawer or the "gtd" drawer or
> whatever, I'd just isearch for org and get it.
> --
The only package that interests me are packages that I have already
installed or packages that are new.
I often use
M-x customize-changed RET
or use NEWS to "explore" new stuff.
For example,
M-x list-changed-packages RET
could either prompt for a Emacs release or a timestamp and list packages
that were modified in the intervening period. A PACKAGE-NEWS file could
be introduced which is current archive-contents *together* with the
*-readme.txt.
Or
There could be a sort option based on create/modify time.
ps:
I only wish that timestamps that I see in the below listing
http://elpa.gnu.org/packages/?C=M;O=D
give an idea of when a *particular* package was created/modified as
opposed to when the package *tar* was published. Save for Org, all
packages have "05-May-2012" has modified date. This is not that helpful
for discovery. For example, I would have liked to know when 'csv-mode'
made it's debut.
--
next prev parent reply other threads:[~2012-05-22 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 17:42 list-packages: Marking packages as "uninteresting"? T.V. Raman
2012-05-17 14:23 ` Jeremiah Dodds
2012-05-17 15:38 ` Stefan Monnier
2012-05-21 2:37 ` Tim Cross
2012-05-22 8:00 ` T.V. Raman
2012-05-22 12:56 ` Jambunathan K [this message]
2012-05-22 16:24 ` list-packages: Marking packages as Isaac
2012-05-24 13:11 ` list-packages: Marking packages as "uninteresting"? T.V. Raman
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=81bolgxtku.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jeremiah.dodds@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=tv.raman.tv@gmail.com \
/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).