Re: zsh-3.1.2-zefram3 - first experience

[Andrew Main <zefram@xxxxxxxxx>]

Andrej Borsenkow wrote:
>the_makefile=Makemod
>/home/bor/src/zsh-3.1.2-zefram3/Src/mkmakemod.sh: syntax error at line 239: `(' unexpected
>gmake[1]: *** [Makemod] Error 2
>gmake[1]: Leaving directory `/SAM/home/bor/build/zsh-3.1.2-zefram3/Src'
>gmake: *** [Src] Error 2

Well that localises it a little.

>+ sdir=/home/bor/src/zsh-3.1.2-zefram3 
>+ top_builddir=+ echo /home/bor/src/zsh-3.1.2-zefram3
>+ top_builddir=+ sed -e s,[^/][^/]*,..,g -e s,^/,,
>+ top_builddir=+ pwd
>+ top_builddir=../../../../SAM/home/bor/build/zsh-3.1.2-zefram3 
>+ CONFIG_FILES=Src/Makemod:../../../../SAM/home/bor/build/zsh-3.1.2-zefram3/Src/Makemod.in CONFIG_HEADERS= ./config.status
>creating Src/Makemod
>sed: Cannot open /home/bor/src/zsh-3.1.2-zefram3/../../../../SAM/home/bor/build/zsh-3.1.2-zefram3/Src/Makemod.in: No such file or directory

Ouch.  I hadn't thought about symbolic links in the pathname.  At least
this one's easily soluble.

>   At least my /bin/sh is not happy with [^xyz] pattern. Here is patch:

I don't think all sh's are happy with [!xyz].  I'll do this bit another
way -- all sed's can handle [^xyz].

>3. makepro.awk fails. I am using nawk. It fails because of unquoted `{' -
>it is metacaracter in extended regexp.

Sorted.

>4. Finally, after I managed to compile it, I lost ZLE!!! All seems to
>work, zle.so, comp1.so, compctl.so are loaded, bindkey shows all bindings,
>but when I try to use *any* bound character, I get no effects. '^P' gives
>fine message `'^P' not found" :-)

"'^P' not found" sounds like it's looking for a *function* called '^P'.
What bindkey instructions are you executing on startup?

-zefram