Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-27 Thread Andrey G. Grozin
On Fri, 26 Aug 2005, C Y wrote: > I think I know what Andrey is thinking about here. Let's say we have > the following expression: > > 2 >b + 2 a > + c > d >

RE: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread Bill Page
On August 26, 2005 4:00 PM Martin Rubey wrote: > > C Y writes: > > I think I know what Andrey is thinking about here. Let's > > say we have the following expression: > > > > 2 > > b + 2 a > > + c >

Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread Martin Rubey
C Y writes: > I think I know what Andrey is thinking about here. Let's say we have > the following expression: > >2 > b + 2 a > + c > d >

Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread root
> 1. What is the correct file to put the definition and initialisation of >$InterfaceStrings ? choose a new file. > 2. Is there some way in which this initialisation could be made dependent > on external conditions? For example, can I pass a command-line argument to > AXIOMsys, and check

Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread C Y
--- Martin Rubey <[EMAIL PROTECTED]> wrote: > Andrey G. Grozin writes: > > > ... if this C code is used, it is absolutely impossible (and never > > will be possible) to copy a (part of) output by the mouse and > > insert in into an input field (because it is not possible to > > reconstruct the m

Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread Andrey G. Grozin
I forgot to ask one more practical question. The prompt prefix and suffix will contain non-printable chars, \0x02 (ctrl-b) and \0x05 (ctrl-e). How can I include them in a boot string? Is literal embedding of these bytes inside a string enough? (in emacs, ctrl-q ctrl-something inserts the litera

Re: [Axiom-developer] steps towards better TeXmacs interface

2005-08-26 Thread Martin Rubey
Dear Andrey, just two comments: regarding the markers and in and output parsing you should short circuit yourself wiht Kai Kaminski, I suppose. Second: Andrey G. Grozin writes: > ... if this C code is used, it is absolutely impossible (and never will be > possible) to copy a (part of) output