On Jun 28, 4:55 pm, Mathias Dahl <[EMAIL PROTECTED]> wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>
> > The only problem is I couldn't think of any practical example where
> > it would be useful to choose from several actions to execute. For
> > example, what else would one want to do with buffers besides
> > switching to them? Killing them? One usually kills the current
> > buffer, so it doesn't seem very useful. The same with files. What
> > else would one want to do with them than opening them?
>
> Maybe buffers isn't the best example, a better one could be friends,
> or colleagues. Say I want to send a chat message to my friend. Using
> `anything' I type in his name and get a match, then I get to choose
> whether I want to start to chat with him or send him an e-mail.

Yep, I know the theory. :) I only wanted an example which is closer to
the typical use of emacs, that's why I mentioned files and buffers.

Anyway, it's not hard to do, so I'll implement it when I have the
time. Probably using buffers as an example even if it's not very
useful.

> Of course, I could always define two sources, one for chat and one for
> e-mail... Anyway, maybe that can give you an idea. BTW, I am trying
> out `anything' as a replacement for iswitchb right now :)

I'm an iswitchb fan myself and I actually prefer the iswitchb
interface for switching buffers, since buffer switching is very
frequent and iswitchb is not so disruptive (doesn't pop up a window).

I plan to implement an anything-iswitchb integration. Iswitchb will
work as usual, but if you're idle for a while then the iswitchb input
will be used as anything input and a buffer will popup with the
completions anything can offer.

Like with timid completion.

_______________________________________________
gnu-emacs-sources mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources

Reply via email to