Chronological Thread 

< Chronological >      < Thread >

---

What about adding a level of indirection in the communication between
"session" and the plug-in? What I mean is:

- When the user types a command for the plug-in in a session, instead
of sending what he typed, call a scheme procedure with arguments:

* the string the user typed
* the port used to talk to the child process

You can already do this without changing
anything in the standard components
of TeXmacs (but this remains somehow
a hack) ; write a new plugin (let's
call it "foo", to define things clearly),
and in the plugin "foo", do :
<<
(define (foo-plugin-eval name session t)
(display* "foo-plugin-eval=" name "; session=" session "; t=" t "\n")
(if (equal? name "foo")
(begin
... the stuff for the foo plugin ...
)
; Default case
(plugin-eval0 name session t))
)
(define plugin-eval0 plugin-eval)
(set! plugin-eval foo-plugin-eval)))
>>

This way, (foo-plugin-eval) behaves as a
stub for the real (plugin-eval0) that uses
the socket, and you can preprocess/postprocess
the input & the output exactly the way you
want.

Is that what you wanted, or are there some
missing things ?

Best, Henri

---

• extern-exec and "further customization", Lionel Elie Mamane, 02/01/2006
  • Re: [TeXmacs] extern-exec and "further customization", Henri Lesourd, 02/01/2006
    • Re: [TeXmacs] extern-exec and "further customization", Lionel Elie Mamane, 02/02/2006
      • Re: [TeXmacs] extern-exec and "further customization", Joris van der Hoeven, 02/02/2006
        • Re: [TeXmacs] extern-exec and "further customization", Lionel Elie Mamane, 02/03/2006
          • Re: [TeXmacs] extern-exec and "further customization", Joris van der Hoeven, 02/03/2006
            • Re: extern-exec and "further customization", Lionel Elie Mamane, 02/06/2006
              • Re: [TeXmacs] Re: extern-exec and "further customization", Henri Lesourd, 02/07/2006

---

Archive powered by MHonArc 2.6.19.