From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: thierry.volpiatto@gmail.com
Subject: Re: anything.el inclusion
Date: Mon, 29 Mar 2010 13:32:58 -0500 [thread overview]
Message-ID: <87k4svhtb9.fsf@lifelogs.com> (raw)
In-Reply-To: jwvfx3malb6.fsf-monnier+emacs@gnu.org
On Fri, 26 Mar 2010 16:19:37 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>>> I mean these completions would be useful for standard existing
>>> commands as well.
>> Yes, i agree, but they need anything system to be dynamic, standard
>> emacs commands use static completion (one shot completion, no timer).
SM> I don't really know what you guys are talking about. Can someone give
SM> an example of what behavior is under discussion here?
Ditto, I don't know the anything.el internals well enough. As a user I
find it very valuable but I haven't even written a anything-* source,
only configured existing ones.
SM> PS: No objection to including anything.el from me.
It lives at http://www.emacswiki.org/emacs/Anything
According to that page, Tassilo Horn, Jason McBrayer, rubikitch and
Thierry Volpiatto maintain the anything-config repository. They would
probably be the best group to put together a version of anything.el
suitable for inclusion and to propose a list of anything-config sources
that the Emacs maintainers can pick from.
rubikitch or Thierry, are you interested in doing this?
Ted
next prev parent reply other threads:[~2010-03-29 18:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 6:18 kill-ring visualization joakim
2010-03-18 14:06 ` Stefan Monnier
2010-03-18 18:39 ` Leo
2010-03-18 19:37 ` joakim
2010-03-24 9:34 ` Juri Linkov
2010-03-24 13:54 ` Stefan Monnier
2010-03-25 7:04 ` Juri Linkov
2010-03-25 9:47 ` Thierry Volpiatto
2010-03-25 10:13 ` joakim
2010-03-25 10:20 ` Thierry Volpiatto
2010-03-25 13:56 ` anything.el inclusion (was: kill-ring visualization) Ted Zlatanov
2010-03-25 17:28 ` anything.el inclusion Juri Linkov
2010-03-26 6:37 ` Thierry Volpiatto
2010-03-26 7:01 ` Juri Linkov
2010-03-26 7:22 ` Thierry Volpiatto
2010-03-26 20:19 ` Stefan Monnier
2010-03-29 18:32 ` Ted Zlatanov [this message]
2010-03-29 19:34 ` Thierry Volpiatto
2010-04-03 5:44 ` Thierry Volpiatto
2010-04-03 13:53 ` Stefan Monnier
2010-04-03 14:17 ` Thierry Volpiatto
2010-04-03 19:08 ` Stefan Monnier
2010-03-26 17:09 ` Ted Zlatanov
2010-03-27 19:38 ` Juri Linkov
2010-03-27 21:35 ` Johan Busk Eriksson
2010-03-28 7:58 ` Yoni Rabkin
2010-03-28 17:39 ` joakim
2010-03-29 18:25 ` Ted Zlatanov
2010-03-26 2:00 ` regexp completion (was: kill-ring visualization) Stefan Monnier
2010-03-25 17:29 ` kill-ring visualization Juri Linkov
2010-03-26 2:53 ` Stefan Monnier
2010-03-26 7:09 ` Juri Linkov
2010-03-26 20:17 ` Stefan Monnier
2010-03-27 19:42 ` Juri Linkov
2010-03-27 20:37 ` Stefan Monnier
2010-03-30 16:07 ` Juri Linkov
2010-03-30 20:35 ` Stefan Monnier
2010-03-31 15:04 ` Juri Linkov
2010-03-25 16:49 ` Drew Adams
2010-03-18 15:16 ` Drew Adams
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=87k4svhtb9.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@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 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.