zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
Date: Mon, 8 Oct 2018 17:58:25 +0100	[thread overview]
Message-ID: <20181008165826eucas1p1d92a1c3f2c35ea914dfc7065cede6ddc~bsKHce1eU0484904849eucas1p1W@eucas1p1.samsung.com> (raw)
In-Reply-To: <CAH+w=7boCKyiNyLFrqkqVphv+ZHkDS1Q-XO5Rqx0WLghN1rNAA@mail.gmail.com>

On Mon, 2018-10-08 at 09:52 -0700, Bart Schaefer wrote:
> On Mon, Oct 8, 2018 at 9:06 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Bart Schaefer wrote on Mon, 08 Oct 2018 08:57 -0700:
> > > [PWS] means that the param_private module isn't included in a default
> > > build, so you have done something (edited config.modules, probably) to
> > > enable it.
> > On my machine, configure generates a link=dynamic auto=yes load=yes line
> > for zsh/param/private.  I do change that link to link=static auto=no, but
> > you seem to imply it should've generated that line with link=no?
> Well, that's what Peter was implying, I was just clarifying.  However,
> I think you're right that zsh/param/private normally is available as a
> dynamic module.

Yes, all I was saying is that you'd changed the configuration in a way
you hadn't mentioned, which you've now confirmed.  No reason to suppose
this is actually related.

> I think all this stuff about V10 is actually a goose chase, and it's
> B02 that is the real point of failure.

If that's failing on it's own, that's certainly the one to focus on
first, and highly likely the other will go away.

pws


  reply	other threads:[~2018-10-08 16:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 21:05 [PATCH] typeset -p doesn't report -U (unique) attribute Stephane Chazelas
2018-09-25 16:41 ` Daniel Shahaf
2018-10-07 13:35 ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Stephane Chazelas
2018-10-08  9:05   ` Peter Stephenson
     [not found]     ` <CACeGjnUhNqca7jLAR0KKSxobzDd+xXdAe4BeUeRpxu2CTp_zkA@mail.gmail.com>
2018-10-08 14:10       ` Peter Stephenson
2018-10-08 14:28         ` Daniel Shahaf
2018-10-08 15:24           ` Peter Stephenson
2018-10-08 15:49             ` Daniel Shahaf
2018-10-08 15:57               ` Bart Schaefer
2018-10-08 16:06                 ` Daniel Shahaf
2018-10-08 16:52                   ` Bart Schaefer
2018-10-08 16:58                     ` Peter Stephenson [this message]
2018-10-08 16:02               ` Daniel Shahaf
2018-10-08 16:19                 ` Peter Stephenson
2018-10-08 16:43               ` Peter Stephenson
2018-10-08 16:58                 ` Daniel Shahaf
2018-10-08 17:14                   ` Bart Schaefer
2018-10-08 19:39                     ` Stephane Chazelas
2018-10-09  9:02                   ` Peter Stephenson
     [not found]                   ` <1539075745.1499.2.camel@samsung.com>
2018-10-09  9:44                     ` Peter Stephenson
2018-10-09 16:52                       ` Bart Schaefer
2018-10-09 23:40                         ` Vin Shelton
2018-10-08 15:54             ` Bart Schaefer
2018-10-08 16:40               ` Bart Schaefer
2018-10-09 10:59   ` local read-only variables (Was:[PATCH] [long] typeset doesn't report tied parameters (and related issues)) Stephane Chazelas
2018-10-11  9:45   ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Oliver Kiddle
2018-10-11 12:46     ` Peter Stephenson

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='20181008165826eucas1p1d92a1c3f2c35ea914dfc7065cede6ddc~bsKHce1eU0484904849eucas1p1W@eucas1p1.samsung.com' \
    --to=p.stephenson@samsung.com \
    --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).