From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39497-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 27617 invoked by alias); 29 Sep 2016 10:06:33 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 39497
Received: (qmail 7657 invoked from network); 29 Sep 2016 10:06:33 -0000
X-Qmail-Scanner-Diagnostics: from mail-qt0-f175.google.com by f.primenet.com.au (envelope-from <sgniazdowski@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.216.175):SA:0(0.0/5.0):. 
 Processed in 0.123953 secs); 29 Sep 2016 10:06:33 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,
	T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: sgniazdowski@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.216.175 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=ix+V6d78MSl/O2Dfxpw613fFLCe48lEkamAL/VUXE90=;
        b=0LFGGOBWCkuIT5edDRqr214D3ji58PwFq/m6rQWxmCcvUUtigI2yFUz3aNdakClhhA
         726cMHRRN92gwbwXxbt7Sa00f0bKaausKmbLqUbRtG5O5m1opJ1885c8VYSZFIGCDdLZ
         qZ1lm3V15DaBoFLdtbJ+IUTpMub0fvR18d4kUw5KROPEBtgDrqMuJa7lSa0QISXZ8/iV
         4YTPISrlri+vTYOJsNG8P79IP4C6i9lL/DLJ4CytqhItRP2hMA4EFTyS/SvP1lIYZF5v
         Nk76EKP17UKOQvcdsqKyBpQDlZYS0GOnOExMXBRpIx7M6XoV1SfJyuVjVaffbndm23o8
         z5wQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=ix+V6d78MSl/O2Dfxpw613fFLCe48lEkamAL/VUXE90=;
        b=P4KnnD8ehEgn6ReYJtw7S8xq39HoFaDfD+NWca4w4aq6S19uHC6a/FAOxqhmjJl06A
         dYsBuYWuUeF+g1A/yBYKAaa7YUq07nZ0aUiodowBseCNbfHxut8ddS1RnxIX+TTJjAv8
         GLJHvENuhEj6cq8rNQaxekve3Z1gScTH0oYey2JRMmDIcDZoJ6zfj/yNNnTHS6xHWMQa
         u0VCBRcVY5Rm1RIAQczpADdg6DVskNVkq7VB7CU5NzsrL/1W4NPdGKNB+uv8x7ZI9e2Q
         bRTOBA6z5ryJuBgY01JG5RUpUJuzCDztTAyWQ4wZyjDRtVIod7ursUp5vZ/eobCIc85D
         VX4A==
X-Gm-Message-State: AA6/9RlqGEGDQ2gg9Mc8fPN7IUfgG0v+JymEYMF3pi8tqgq/PcGQzXLsYlwpL8jKiPqNeaaIDoPKnDUuX3NeGw==
X-Received: by 10.237.58.232 with SMTP id o95mr452401qte.33.1475142185407;
 Thu, 29 Sep 2016 02:43:05 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <160929001004.ZM27686@torch.brasslantern.com>
References: <CAKc7PVCXq6jQe2gF-Hb4UFBx7UXxRE=3_8Z2Oyq-H6d0LoNLAA@mail.gmail.com>
 <160929001004.ZM27686@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Thu, 29 Sep 2016 11:42:45 +0200
Message-ID: <CAKc7PVBO1dva04KosqD5h6NU6irtGHuWvGxE4pEAUCbw5YD_3Q@mail.gmail.com>
Subject: Re: Surprising effect of fun() { local FPATH=...; autoload -X }, and
 a bug
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I will go deep into what you wrote, I'm just overloaded with work
currently (while having no day time job hehe) and cannot much divide
focus, however I now encountered the FPATH problem (first time from
the initial email), having a debug print in place. Function uizcm is
loaded via:

                eval "function ${(q)func} {
                    local FPATH=3D${(qqq)PLUGIN_DIR}:${(qqq)FPATH}
                    builtin autoload -X ${(q-)opts[@]}
                }"

It has:

echo "FPATH: $FPATH" >> /tmp/reply-fp

The FPATH printed always contained required component for
further-autoloading to work, however now =E2=80=93 the case caught =E2=80=
=93 it just
didn't. And, I think this is maybe interesting =E2=80=93 doing:

FPATH=3D"the required fpath"

in shell, then again invoking Zle widget uizcm via Ctrl-O-Ctrl-U,
yielded working setup. So it's like if once uizcm took FPATH from the
local "FPATH" line in the emulated autoload stub, and once took it
from global scope.

Best regards,
Sebastian Gniazdowski