- From: Lionel Elie Mamane <address@hidden>
- To: Joris van der Hoeven <address@hidden>
- Cc: address@hidden
- Subject: Re: [TeXmacs] extern-exec and "further customization"
- Date: Fri, 3 Feb 2006 00:34:09 +0100
On Thu, Feb 02, 2006 at 11:13:37PM +0100, Joris van der Hoeven wrote:
>
On Thu, Feb 02, 2006 at 10:46:32AM +0100, Lionel Elie Mamane wrote:
>
> On Wed, Feb 01, 2006 at 09:26:52PM +0100, Henri Lesourd wrote:
>
>> As far as calling a plugin from Scheme code
>
>> is concerned, I would rather say :
>
>> <<
>
>> (plugin-eval [name] [sesssion] [command])
>
>> >>
>
> Yes, this seems to do it. Thanks. TeXmacs doesn't seem to like the
>
> second thing I tried, though... It doesn't appreciate plugin foo
>
> telling it
>
> DATA_BEGIN command:(plugin-eval "foo" "default" "bar") DATA_END
>
> it seems to go into an infinite loop of issuing bar to plugin foo.
>
That is not surprising, since your plug-in seems to ask TeXmacs to
>
ask the *same* plug-in for executing some command, all over the
>
*same* pipe.
Yes, exactly :) I'm not surprised it doesn't work, but I don't see why
it cannot work.
>
This is not reasonable: your plug-in might directly execute the command
>
instead of passing through TeXmacs.
This supposes that the command does not depend on the TeXmacs state. I
was hoping to get information about the TeXmacs state in this
way. Something like:
DATA_BEGIN command:(plugin-eval "foo" "default" (string-append "callback:
pos foo " (object->string (position-get foo)))) DATA_END
I'll have to cook up another system.
--
Lionel
Archive powered by MHonArc 2.6.19.