Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: (zsh-4.3.2) Y03 test failure under Slackware Linux 9.0.0


Eric De Mund wrote:
> I'm experiencing a "make check" failure in test Y03 when building
> zsh-4.3.2 under Slackware Linux 9.0.0 on a i686-pc-linux-gnu host, as I
> experienced back in March of this year (Message-ID:
> <17433.46602.590991.508063@xxxxxxxxxxx>).

Peter Stephenson wrote:
] The failure is this:
] *** /tmp/zsh.ztst.out.9272	Mon Nov 27 00:13:12 2006
] --- /tmp/zsh.ztst.tout.9272	Mon Nov 27 00:13:12 2006
] ***************
] *** 2,8 ****
]   line: {tst -o +o }{}
]   line: {tst -o +o }{}
]   MESSAGE:{no arguments}
] ! line: {tst +o }{}
] ! line: {tst +o -o }{}
] ! line: {tst +o -o }{}
]   MESSAGE:{no arguments}
] --- 2,10 ----
]   line: {tst -o +o }{}
]   line: {tst -o +o }{}
]   MESSAGE:{no arguments}
] ! line: {tst -+}{}
] ! MESSAGE:{no arguments}
] ! line: {tst -+}{}
] ! MESSAGE:{no arguments}
] ! line: {tst -+}{}
]   MESSAGE:{no arguments}
] Test ./Y03arguments.ztst failed: output differs from expected as shown above for:
]  tst_arguments -+o
]  comptest $'tst -\t\t\t\C-w\C-w+\t\t\t'
] Was testing: option beginning with + and -.
] ./Y03arguments.ztst: test failed.
] [...]
] My best guess is that the two \C-w's in the test aren't wiping the -
] from the previous line, "tst -o +o ". That suggests $WORDCHARS doesn't
] include "-" or it isn't having an effect for some reason. That would
] mean the test actually started the second set of completions with "tst
] -+" on the line, which then behaved the way you'd expect, so the
] failure isn't in the completion part at all. This seems more likely
] than the "-+" popping out of a failed completion.
] What happens if you start from "zsh -f" (and "bindkey -e" if neces-
] sary) and type:
] % tst -o +o\C-w\C-w
] does the - disappear (as it should)?  If not, what does "print -r
] $WORDCHARS" show?

On the Slackware 9.0.0 host in question:

    bear:~% cat /etc/slackware-version
    Slackware 9.0.0
    bear:~% ~/bin/config.guess

, the - (minus) does not disappear; I'm left with:

    bear:~% tst -

However, WORDCHARS consists solely of an _ (underscore):

    bear:~% print -r $WORDCHARS

When I set WORDCHARS to that which it's set to on another host, my
cygwin host:

    cowberry:~% uname -s
    cowberry:~% print -r $WORDCHARS

, then your requested test only leaves me with "tst ":

    bear:~% WORDCHARS='*?_-.[]~=/&;!#$%^(){}<>'
    bear:~% tst 
                ^---- cursor is here
    bear:~% print -r $WORDCHARS

So do I understand correctly that WORDCHARS should be set to more than _
(a lone underscore) in a "zsh -f" shell?

Let me know if you need me to perform any other tests.

[several minutes later]

Ok, I believe I've solved this. My build environment for zsh-4.3.2 was a
zsh-4.2.5 shell with my ~/.{zshenv,zshrc,zlogin} files invoked, which
includes this variable setting: WORDCHARS="_".

When I removed my WORDCHARS setting (and logged out and logged back in),
WORDCHARS reverted to what I presume is the default:

    bear:~% print -r $WORDCHARS

I then unpacked zsh-4.3.2.tar.bz into a brand new directory, configured
it, and performed a "make" and a "make check". All the tests in
zsh-4.3.2's "make check" passed.

It doesn't seem right that a "make" or "make check" of a new zsh, if
done from within the environment of an old zsh, should require a
"zsh -f" environment. However, that's your call. It seems to me that if
the Y03 test (or any other test) requires the environment to be set a
certain way, it should set it up itself. My sense here is that the
$WORDCHARS value is presumed set appropriately rather than being set

Thank you for helping me drill down on this problem; I appreciate it
very much.

Eric De Mund              |      Ixian Systems      | 
email: <ead@xxxxxxxxx>    | 650 Castro St, #120-210 | ICQ: 811788
http://www.ixian.com/ead/ | Mountain View, CA 94041 | Y!M: ead0002

Messages sorted by: Reverse Date, Date, Thread, Author