zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [Bug] $jobstates does not work in $()
Date: Fri, 4 Mar 2022 13:04:38 +0000	[thread overview]
Message-ID: <20220304130438.GA7687@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <59C35A96-D41D-4EF7-A02B-94B70AE1122D@kba.biglobe.ne.jp>

Jun T wrote on Fri, Mar 04, 2022 at 11:14:07 +0900:
> 
> > 2022/03/04 8:07, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > 
> > On Thu, Mar 3, 2022 at 2:05 PM Vin Shelton <acs@alumni.princeton.edu> wrote:
> >> 
> >> I don't see how you could have provoked this, Peter, but in the latest sources, I'm seeing a test failure under i3 in Arch:
> > 
> > Try this:
> > 
> > diff --git a/Test/W03jobparameters.ztst b/Test/W03jobparameters.ztst
> (snip)
> > +  zpty_input 'zmodload zsh/parameter'
> 
> This doesn't work for me.
> 
> I think the problem is that MODULE_PATH is not imported by the zsh started
> by zpty (for security).
> 
> 
> diff --git a/Test/W03jobparameters.ztst b/Test/W03jobparameters.ztst
> index 474adfaec..de3420038 100644
> --- a/Test/W03jobparameters.ztst
> +++ b/Test/W03jobparameters.ztst
> @@ -37,6 +37,7 @@
>  %test
>  
>    zpty_start
> +  zpty_input "MODULE_PATH=$MODULE_PATH"

Add ${(q)}?

Cheers,

Daniel


>    zpty_input 'sleep 3 &'
>    zpty_input 'print $jobstates'
>    zpty_input '(print $jobstates)'
> 
> 


  reply	other threads:[~2022-03-04 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  0:46 Carl Agrell
2022-03-01 10:40 ` Peter Stephenson
2022-03-02  9:44   ` Daniel Shahaf
2022-03-02 20:18     ` Peter Stephenson
2022-03-03 22:04       ` Vin Shelton
2022-03-03 23:07         ` Bart Schaefer
2022-03-04  2:14           ` Jun T
2022-03-04 13:04             ` Daniel Shahaf [this message]
2022-03-04 13:13               ` Vin Shelton
2022-03-06  4:18               ` Jun T
2022-03-07 14:22                 ` Daniel Shahaf

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=20220304130438.GA7687@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /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).