On Jun 26, 11:28 am, Nick Alexander <ncalexan...@gmail.com> wrote:
> > Trying to add ; at various points didn't help.  Is this just me
> > (4.1.alpha1 fresh build on G4 X.4)?  Is GAP running in the
> > background?  But when I quit, there is no message about that, and in
> > any case presumably GAP doesn't do the codebase search.
>
> Why do you think GAP is relevant? The relevant command seems to be

Only because of the ;

>
>      cmd = 'sage -grepdoc "%s" | grep "%s"'%(s,extra)
>
> (The default is extra='').  So can you try 'sage -grepdoc' on your  
> architecture?
>

Similarly to sage -grep, works like a charm.  This is the first Sage
installation where this problem has come up, so the problem must have
come in since 4.0.2.  Where is the code for these sage -foo commands?
I found them once but have forgotten where they are.

The following from man find might be relevant, since that is the error
message which I am getting:

     -exec utility [argument ...];
             True if the program named utility returns a zero value as
its
             exit status.  Optional arguments may be passed to the
utility.
             The expression must be terminated by a semicolon
(``;'').  If the
             string ``{}'' appears anywhere in the utility name or the
argu-
             ments it is replaced by the pathname of the current file.
             Utility will be executed from the directory from which
find was
             executed.  Utility and arguments are not subject to the
further
             expansion of shell patterns and constructs.

but I don't know where find is used here.  Does grep call find?  (That
is obviously a shell newbie question, apologies.)

- kcrisman

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to