🚀 go-pugleaf

hallam@zeus02.desy.de (Phill Hallam-Baker) writes:

>In article <9208261428.AA20587@cse.uta.edu>, hufnagel@cse.uta.edu (Stephen
>Hufnagel) writes:

>|>     We plan to construct a LaTex/Z development environment.  Attached
>|>     is  a  brief  set  of  requirements.  Your comments, suggestions,
>|>     and/or participation would be appreciated.  Also, If you know  of
>|>     existing similar components or capabilities, please let us know.

>|>     APPROACH: The LTD editor will be optimized  for  the  syntax  and
>|>     semantics  of  LaTex and LaTex style files --i.e., ZED.STY and/or
>|>     OZ.STY.  Its key function is to provide LaTex  sensitive  editing


An idea I have been toying with which is half-way to what you propose is
a more general purpose X "macro" tool.  This tool can store a database 
of fragments of whatever text you like, organised and accessed using 
GUI-navigation or keyword search.  Once a fragment is selected the tool 
will then type it into another xterm window on your screen.  
Context-sensitive help can be associated with each stored fragment.

For LaTeX the database would have a collection of commonly used forms
such as lists and tables.  It could have a complete menu of LaTeX and
TeX commands on-line.  You could then extend this with a ZED or OZ module.

Pros:  It is a separate tool that can be reused for other jobs.  It is 
simpler.

Cons: It is not the fully-integrated super-duper system that you are
contemplating.

PCs tend to large integrated (ie closed) systems because they have no
alternative tool infrastructure or culture.  I would prefer a cluster of
tools.
-- 
Anthony Shipman                 "You've got to be taught before it's too late,
CP Software Export Pty Ltd,      Before you are six or seven or eight,
19 Cato St., East Hawthorn,      To hate all the people your relatives hate,
Melbourne, Australia, 3121       You've got to be carefully taught."  R&H