zsh-workers
 help / color / mirror / code / Atom feed
From: DervishD <raul@pleyades.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Test E01 and Y01 fails in my zsh 4.0.9
Date: Fri, 9 Jan 2004 12:54:21 +0100	[thread overview]
Message-ID: <20040109115421.GC2777@DervishD> (raw)
In-Reply-To: <1040107223003.ZM11778@candle.brasslantern.com>

    Hi Bart :)

 * Bart Schaefer <schaefer@brasslantern.com> dixit:
> } file is run even when zsh is invoked with '-f', isn't it?
> Yep.  In fact, /etc/zshenv is run even when zsh is invoked with
> "-o no_global_rcs".

    There should be a flag for avoiding even /etc/zshenv, just in
case it is badly broken...

> } > }     Don't know why 'comptestinit' stops there :??
> }     Can it be caused by some option I set on my /etc/zshenv?
> It could be ... but I can't suggest anything specific.

    Well, I isolated the problem: the test doesn't like my PS1
(which, BTW, shouldn't be in /etc/zshevn... my fault). Since
'comptest' modifies PS1, that was probably the problem. If I unset my
PS1, I got the following as the output of 'make check TESTNUM=Y01'.
Haven't tried with Y02 and Y03 yet:

cd Test ; make check
make[1]: Entering directory `/root/Test/zsh-4.0.9/Test'
if test -n ""; then \
  cd .. && DESTDIR= \
  make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
for f in ./Y01*.ztst; do \
  ../Src/zsh +Z -f ./ztst.zsh $f; \
done
./Y01completion.ztst: starting.
*** /tmp/zsh.ztst.out.6474	Fri Jan  9 12:42:19 2004
--- /tmp/zsh.ztst.tout.6474	Fri Jan  9 12:42:19 2004
***************
*** 1,12 ****
  line: {: }{}
! DESCRIPTION:{file}
! DI:{dir1}
! DI:{dir2}
! FI:{file1}
! FI:{file2}
! line: {: dir1/}{}
! line: {: dir2/}{}
! line: {: file1}{}
! line: {: file2}{}
! line: {: dir1/}{}
! line: {: dir2/}{}
--- 1,7 ----
  line: {: }{}
! line: {: }{}
! line: {: }{}
! line: {: }{}
! line: {: }{}
! line: {: }{}
! line: {: }{}
Test ./Y01completion.ztst failed: output differs from expected as shown above for:
  comptest $': \t\t\t\t\t\t\t'
Was testing: directories and files
./Y01completion.ztst: test failed.
make[1]: [check] Error 1 (ignored)
rm -rf Modules .zcompdump
make[1]: Leaving directory `/root/Test/zsh-4.0.9/Test'

    I don't have the 'computil' module, could it be the problem?
Anyway, my zsh seems to work OK even if the test fails :?

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/


  parent reply	other threads:[~2004-01-09 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 12:11 DervishD
2004-01-07 16:02 ` Bart Schaefer
2004-01-07 18:56   ` DervishD
2004-01-07 21:09     ` Bart Schaefer
2004-01-07 21:26       ` DervishD
2004-01-07 22:30         ` Bart Schaefer
2004-01-07 23:46           ` DervishD
2004-01-09 11:54           ` DervishD [this message]
2004-01-31 22:06     ` zpty and sutff Alexey Tourbin
2004-01-31 23:49       ` DervishD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040109115421.GC2777@DervishD \
    --to=raul@pleyades.net \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).