help / color / mirror / code / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Test ./E03posix.ztst was expected to fail, but passed.
Date: Tue, 29 Mar 2022 18:00:52 +0900	[thread overview]
Message-ID: <0862E76F-68CE-419E-867D-A2BB898259E0@kba.biglobe.ne.jp> (raw)
In-Reply-To: <082447B3-C6A4-44A1-A3D3-7FD89D707480@kba.biglobe.ne.jp>

> 2022/03/17 0:30, I wrote:
> Please try the following patch.
> The patch for E03posix.ztst may not be necessary for fixing the
> current problem, but I think it is always safer to use 'zsh -f'.

The patch for E03posix.ztst (adding -f) is not necessary; if ARGV0=sh
and the shell is not interactive no initialization file will be sourced.

I will push the following patch for ztst.zsh.

Exporting MODULE_PATH has no effect since zsh will not import it
for security reason. If a child zsh (started during tests) needs
MODULE_PATH, then it must be set in the child explicitly.

I think the 'expected to fail' test must be run in UTF-8 locale;
I will send a patch in a separate post.

diff --git a/Test/ztst.zsh b/Test/ztst.zsh
index a59c06dcf..89fe69b5b 100755
--- a/Test/ztst.zsh
+++ b/Test/ztst.zsh
@@ -25,6 +25,7 @@ emulate -R zsh
 # Ensure the locale does not screw up sorting.  Don't supply a locale
 # unless there's one set, to minimise problems.
 [[ -n $LC_ALL ]] && LC_ALL=C
+[[ -n $LC_CTYPE ]] && LC_CTYPE=C
@@ -36,8 +37,6 @@ typeset +x WORDCHARS
 # Set the module load path to correspond to this build of zsh.
 # This Modules directory should have been created by "make check".
 [[ -d Modules/zsh ]] && module_path=( $PWD/Modules )
-# Allow this to be passed down.
 # We need to be able to save and restore the options used in the test.
 # We use the $options variable of the parameter module for this.

      parent reply	other threads:[~2022-03-29  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 16:33 Vincent Lefevre
2022-03-15 16:53 ` Mikael Magnusson
2022-03-16 15:30   ` Jun. T
2022-03-22  3:32     ` Jun T
2022-03-22 13:03       ` Vincent Lefevre
2022-03-22 21:04       ` Bart Schaefer
2022-03-23  2:26         ` Vincent Lefevre
2022-03-23 10:38           ` Stephane Chazelas
2022-03-23 16:17             ` Vincent Lefevre
2022-03-23  7:14         ` Jun T
2022-03-29  9:10           ` Jun T
2022-03-29  9:00     ` Jun T [this message]

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:

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

  git send-email \
    --in-reply-to=0862E76F-68CE-419E-867D-A2BB898259E0@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \


* 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


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).