From: Drew Adams <drew.adams@oracle.com>
To: "Juri Linkov" <juri@linkov.net>,
"Simen Heggestøyl" <simenheg@runbox.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
41741@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#41741: [PATCH] Save project list as lisp data
Date: Mon, 8 Jun 2020 16:48:43 -0700 (PDT) [thread overview]
Message-ID: <1f13ef89-b2d6-4d97-8597-a89228ecca36@default> (raw)
In-Reply-To: <87pna943cq.fsf@mail.linkov.net>
> > Another example from the top of my head: recording project visit
> > counts. That could be used for an option to show the most popular
> > projects first in the completion list, for instance.
>
> Or record project visit time, and then sort by time,
> so that the most recently used projects are first.
Haven't been following this thread; sorry.
But this is one of the things bookmarks are great for.
Whatever it is, bookmark it, and use the bookmark to
access it. Each time you do, the bookmark updates
the date+time visited and the number of visits.
Nothing else is needed, just the ability to bookmark
something. And you can do that for pretty much
anything you can visit. If no existing bookmark type
is relevant you can easily define a new bookmark type.
next prev parent reply other threads:[~2020-06-08 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877dwkno62.fsf@simenheg@gmail.com>
2020-06-06 22:59 ` bug#41741: [PATCH] Save project list as lisp data Dmitry Gutov
2020-06-07 19:55 ` Simen Heggestøyl
[not found] ` <87wo4ips6d.fsf@simenheg@gmail.com>
2020-06-07 20:18 ` Dmitry Gutov
2020-06-08 19:00 ` Simen Heggestøyl
[not found] ` <873675jsbv.fsf@simenheg@gmail.com>
2020-06-08 20:32 ` Dmitry Gutov
2020-06-09 18:48 ` Simen Heggestøyl
2020-06-08 23:09 ` Juri Linkov
2020-06-08 23:39 ` Dmitry Gutov
2020-06-08 23:48 ` Drew Adams [this message]
2020-06-06 16:40 Simen Heggestøyl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f13ef89-b2d6-4d97-8597-a89228ecca36@default \
--to=drew.adams@oracle.com \
--cc=41741@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
--cc=simenheg@runbox.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.