[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: more on anything.el inclusion

From: rubikitch
Subject: Re: more on anything.el inclusion
Date: Sat, 17 Jul 2010 22:37:35 +0900 (JST)

From: Ted Zlatanov <address@hidden>
Subject: Re: more on anything.el inclusion
Date: Thu, 01 Jul 2010 08:18:03 -0500


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 
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 
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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]