On Sep 30, 11:48 am, "Yakov Lerner" <[EMAIL PROTECTED]> wrote:
> On 9/30/07, A.Politz <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > I am student of computer science.  In the next semester I'll
> > have to do some practical work supervised by a professor.
> > Now what I really would like to do in this project, is
> > giving vim the ability to start and manage subprocesses.
>
> > What I have in mind is :
>
> >   - Obviously writing the code, that handles the processes
> >     (sockets ? ,portability ? ).
> >     I would at least want to implement this for *nix.
> >   - vim functions to interface with this code.
>
> >   - associate process output with a buffer
> >   - add a buffer option, which automatically scrolls a
> >     buffer to the end
>
> >     or/and
>
> >   - make its output available via functions and autocommand.
>
> Are you going to use pseudo-tty  (between  parent and child) ?
>
> If no, then be aware you are going to have some problems.
>
> If yes, then how much %% of code overlap with /usr/bin/screen
> you are going to have ?
>
> Are you going to have detach/attach functionality a-la screen ?
>

The idea is to make running session aware programs
(lisp, dbms, ... ) possible and non session aware programs easier.
E.g :
 -start a lisp process in the background
 -send a expression to it
 -get the result and do something with it

Both (session and non-session ) is actually already possible,
 the first one with external scripts, but imply many problems
one has to overcome.

-ap


> Are you aware of the existing trick of redirecting output of the
> process to the log-file and having vim constantly reread and
> show the  bottom of the logile ?
>
> Yakov

No, I am not aware of a sane way to constantly reread a file in
a visible buffer let it display the end of it ,all while I am working
in another window or the cmdline. Maybe I missed something.

-ap


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui