🚀 go-pugleaf

In article <1js7odINNqgh@slab.mtholyoke.edu> jbotz@mtholyoke.edu (Jurgen Botz) writes:
>If I want to manipulate the active file (editing, sorting), is the
>following the safe and correct sequence of commands?
>
>   ctlinnd pause "edit active"
>   [do something to the active file]
>   ctlinnd reload active "edit active"
>   ctlinnd go "edit active"

I put a "ctlinnd flush all" after the pause (I do a throttle, actually), just
to make sure that the active file in memory is the same as the one on disk.
Might not be necessary, but it doesn't hurt. :-)

>If I want to manipulate the active from a program (Perl script), do
>I do the same thing, or is there a shortcut?

I would say yes; there's no shortcut as far as I know.

--Ken

In <1js7odINNqgh@slab.mtholyoke.edu> jbotz@mtholyoke.edu (Jurgen Botz) writes:
>If I want to manipulate the active file (editing, sorting), is the
>following the safe and correct sequence of commands?
>   ctlinnd pause "edit active"
>   [do something to the active file]
>   ctlinnd reload active "edit active"
>   ctlinnd go "edit active"
Yes, that is the minimal sequence of commands.  Someone else said they did
a 'flush' after step one.  That's not necessary, and would cause extra
work (e.g., channel programs to be stopped and restarted).

>If I want to manipulate the active from a program (Perl script), do
>I do the same thing, or is there a shortcut?
If you are writing C, look at doc/inndcomm.3 and include/inndcomm.h; they
include all you need to do any ctlinnd command (in fact, ctlinnd itself is
little more than a call to the library).

Hacking up a Perl subroutine that spoke to innd's Unix-domain control
socket should be fairly straightforward.
	/r$