runscript not being invoked by minicom?

[Jeffrey Haemer]

Adam,

Thanks.  It's in /usr/bin, which, yes, is in my path. :-).

When I invoke runscript, from the shell, on scripts like the one you
suggest, they do run, so "runscript" isn't broken.

"ls -ulrt", which is a good tool for showing the last time an executable has
been run, shows minicom isn't invoking runscript.
I haven't tried to pull from the CVS tree, but I did grab a tarball, and
"make configure" fails on my Ubuntu Feisty Fawn box.  Sigh.

On 5/3/07, Adam Lackorzynski <adam at os.inf.tu-dresden.de> wrote:
>
> Hi,
>
> On Tue May 01, 2007 at 13:22:41 -0600, Jeffrey Haemer wrote:
> > I can't get my mincom to run scripts.
> >
> > When I try to run a script (^AG or through "minicom -S scriptname")
> nothing
> > happens.  Careful, detailed investigation [ "ls -ult" :-) ] reveals that
> the
> > script isn't being read
> > and runscript isn't even being invoked.
> >
> > This is probably just pilot error, but can anyone tell me what I'm doing
> > wrong and how to fix it?  I thought about getting the source, building
> from
> > scratch, and debugging it, but it seems like it's easier to ask first.
> >
> > Minicom itself works -- it's only scripts that are hosed.
> >
> >  OS: Ubuntu Feisty Fawn (7.04)
> >  minicom: 2.2-4build1 (installed with apt-get)
>
> Running a script works for me, using CVS head but there's no big
> difference between CVS head and 2.2. Does a really simple script like
>
> print "hello"
>
> work or not? I hope runscript is in your $PATH?! It should, as it's in
> /usr/bin.
>
>
>
>
> Adam
> --
> Adam                 adam at os.inf.tu-dresden.de
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>



-- 
Jeffrey Haemer <jeffrey.haemer at gmail.com>
720-837-8908 [cell]
http://goyishekop.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/minicom-devel/attachments/20070503/67c1932f/attachment.htm