Re: more on anything.el inclusion

[Thierry Volpiatto <thierry.volpiatto@gmail.com>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 01 Jul 2010 09:50:30 +0200 Thierry Volpiatto <thierry.volpiatto@gmail.com> wrote: 
>
> 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?

Maybe a function that autoload all as suggested by Dan?
Would not need major work, but need to discuss it with Rubikitch.

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

In which menu should we add anything commands?
I mean this kind of menu:

(easy-menu-define nil global-map
  "`anything' menu"
  `("Anything commands"
    ["Find files" anything-find-files t]
    ["Show xfonts" anything-xfonts t]))

Here it is in global menu, but maybe that should go in tools or don't
know where.(i never used menus in emacs, toolbar is disabled here).


> TV> For the developper who want to write his own anything source the best
> TV> actually is to look at the sources wrote in anything-config.el.
>
> I don't think you need to explain too much about developer support in
> this thread; I would assume anyone interested in extending it is capable
> of reading the docs.

Ok

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/