Re: [ jEdit-devel ] action namespaces

[Shlomy R. <sre...@gm...>]

>
> > My other comment about plugin normal actions vs macros is about the
> > naming conventions. If the core separates macros from normal actions,
> > maybe the same should be applied to plugins. But I don't know why the
> > core separates them, maybe the intention is user-written macros vs
> > built-in actions?
> Does it influence in any way the idea of origins and their
> implementation we're designing? I'm not that deep in the subject, but I
> believe a caller needn't specify whether he wants action or macro. He
> will provide an unique name and that's it.
>
>
You're right. It doesn't have to influence the idea of origins, but since
you've mentioned it, why does the core separate macros from other actions
in the action sets? If there's no good reason for that, we can drop this
separation. And if there is, it may just as well be relevant for plugins.