From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: rubikitch@ruby-lang.org Newsgroups: gmane.emacs.devel Subject: Re: more on anything.el inclusion Date: Sat, 17 Jul 2010 22:37:35 +0900 (JST) Message-ID: <20100717.223735.49025397.rubikitch@ruby-lang.org> References: <87hbkjhc8p.fsf@tux.homenetwork> <87iq4z5oj8.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1279373873 26393 80.91.229.12 (17 Jul 2010 13:37:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 17 Jul 2010 13:37:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 17 15:37:52 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Oa7aP-000214-MS for ged-emacs-devel@m.gmane.org; Sat, 17 Jul 2010 15:37:50 +0200 Original-Received: from localhost ([127.0.0.1]:59735 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oa7aO-0006iA-UW for ged-emacs-devel@m.gmane.org; Sat, 17 Jul 2010 09:37:48 -0400 Original-Received: from [140.186.70.92] (port=46224 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oa7aJ-0006hl-N7 for emacs-devel@gnu.org; Sat, 17 Jul 2010 09:37:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oa7aH-0004YU-Iy for emacs-devel@gnu.org; Sat, 17 Jul 2010 09:37:43 -0400 Original-Received: from smtp12.m3.home.ne.jp ([220.152.44.18]:39075) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oa7aH-0004Y9-2K for emacs-devel@gnu.org; Sat, 17 Jul 2010 09:37:41 -0400 Original-Received: from localhost ([124.144.92.34]) by smtp12.m3.home.ne.jp with ESMTP id <20100717133735.PNYL3655.smtp12.m3.home.ne.jp@localhost> for ; Sat, 17 Jul 2010 22:37:35 +0900 X-Mailer: Mew version 6.0.51 on Emacs 23.1.50 / Mule 6.0 (HANACHIRUSATO) In-Reply-To: <87iq4z5oj8.fsf@lifelogs.com> X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:127514 Archived-At: From: Ted Zlatanov Subject: Re: more on anything.el inclusion Date: Thu, 01 Jul 2010 08:18:03 -0500 Hi, I'm the developer of anything.el. > TV> On the user side, if you use anything-config.el, there is already build > TV> in sources ready for use, so you can use provided functions like any > TV> other emacs one (e.g M-x anything-xfonts). > > OK. Thanks for explaining. So from the user's viewpoint, it should be > enough to autoload all the front-end anything-* functions (from > anything.el ideally, so users don't have to know about > anything-config.el as you had it in your autoload example). Can you > make the necessary changes? Or will that require major work? We'll add autoload cookies to them. > Is there a list of the standard front-end functions (a subset of the > autoloads below) that should always be exposed (through keyboard > mappings, possibly in a menu) to Emacs users? The xfonts and file > selection ones should be in that list for sure. The preconfigured anything commands are too many to include into menus and some commands overlap other commands. For example, M-x anything-for-files handles buffers (M-x anything-buffers+), recentf (M-x anything-recentf), bookmarks (M-x anything-bookmarks) and locate (M-x anything-locate). We offer single source (anything-c-source-*) and multiple sources commands so that users can select preferred commands. Instead of binding all anything commands to menu and keymap, I created a navigator command for anything-* commands. M-x anything-execute-anything-command lists all anything commands in anything-config.el. Users can search and select appropriate command. Then users can bind it to keys. I think small amount of commands should be bound to menu and keymap. Cheers, -- rubikitch