From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-20582-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 12127 invoked by alias); 18 Sep 2015 05:52:28 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 20582
Received: (qmail 5742 invoked from network); 18 Sep 2015 05:52:27 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:mime-version:content-type;
        bh=1VYuq/sjl/2Bn7lqh7uMJt5lzIQsbSj6U2ikErVRJlA=;
        b=F2n0S72auMcOMU3cBa0mbpVA/2Vwp2GUYJ5XaDBgFmlOTaJhVqVS770BZISngFDXop
         ZgRnyXcNBv4QJ5j31KcvO3dhJ07joX0iEjOaXVHka6cVMGqbBkosMOkQ52WIY3eWwHD3
         5Gq0eelvh8Ml7i+8p3jixhbEBmQbHD6gg/MNnL5DNmzGGA7snu4kom0vvugibcdvjXhk
         KORFK+rsgV1e5x0QxRbcdtqA8F9tqhTu0RajnFEgObSbVkGMlr/uRQCy2pqyTHPuEX5W
         4o+u5DeeWd0TPALMhodLgBsIdlc/2aORyR6Jff9PhXTl+EDuMqtsGGuQEN4MKLdr3XaG
         I5WQ==
X-Gm-Message-State: ALoCoQnOxRdol0vqI4ULMBQH/+CG/nAozk+lsAII1iODr2Ck9Khk7lsDfYmwt3WNtlVLc1s0puzD
X-Received: by 10.60.63.44 with SMTP id d12mr2380815oes.17.1442555544168;
        Thu, 17 Sep 2015 22:52:24 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150917225221.ZM25880@torch.brasslantern.com>
Date: Thu, 17 Sep 2015 22:52:21 -0700
In-Reply-To: <55FB9A50.4060903@eastlink.ca>
Comments: In reply to Ray Andrews <rayandrews@eastlink.ca>
        "Re: autoload" (Sep 17, 10:00pm)
References: <55FAE223.2080502@eastlink.ca> 
	<150917103419.ZM10067@torch.brasslantern.com> 
	<55FB12FD.8000504@eastlink.ca> 
	<150917134047.ZM10250@torch.brasslantern.com> 
	<55FB476F.7080106@eastlink.ca> 
	<150917162009.ZM10431@torch.brasslantern.com> 
	<55FB66E8.5030503@eastlink.ca> 
	<150917210453.ZM12575@torch.brasslantern.com> 
	<55FB9A50.4060903@eastlink.ca>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-users@zsh.org
Subject: Re: autoload
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Sep 17, 10:00pm, Ray Andrews wrote:
}
} I guess the 'line 5 `)' error mystery is best
} forgotten.  Very strange tho.

It's not a mystery.  Try this:

    zsh -nf /usr/share/zsh/functions/Completion/Base.zwc

} $ fpath=( /aWorking/Zsh/Source "${fpath[@]}" )
} $ source miscfunctions
} $ autoload -w /aWorking/Zsh/Source/Source.zwc
} $ l
} [ nothing ]
} $ l
} [ now I get listing ]

The way autoload works is, the name of the file has to be the same as
the name of the function.  If you "source" the file, you execute the
file contents immediately, which in your case defines the functions.
If you "autoload" the function names, you NEITHER define NOR execute
them; you just mark them to be processed later.

Then when you try to execute, zsh looks for a file with the same name
as the function, parses it, and executes the result of the parse.
Except for handling of the positional parameters, this is *almost* the
same as

   functions[$filename:t]=$(<filename)
   eval "$functions[$filename:t]"

With "autoload -z" (the default when no option), zsh assumes the file
*was* the entire function body and does nothing further.

*If* the function was marked "autoload -k", then zsh assumes that the
eval-like step defined THAT function, and calls it by name a second time,
similar to:

   functions[$filename:t]=$(<filename)
   eval "$functions[$filename:t]"
   $filename:t

If we now throw zcompile into the mix, the -z / -k options to autoload
are ignored in favor of the -z / -k options to zcompile.  However, the
rule about the file name having to be the same as the function name
doesn't change.  Further "autoload -w" still doesn't define anything;
it just uses the index table in the zcompiled file to grab the list
of names to mark for later processing.

} Strangely there seems to be no trouble with multiple functions in one
} file except in the case of 'miscfunctions' so I have to source it
} separately. (The other multiple functions are all help functions only
} called by the main function in each file. I don't know why that makes
} a difference, but it does.)

Does what I just wrote, above, help?  In the "miscfunctions" case, the
name of the file matches NONE of the names of the functions inside it;
they can't be autoloaded.  The name of the file has to match the name
of AT LEAST ONE function inside the file, *OR* the entire file has to
be that single function (as if it were a script).

} Also, I wonder why $fpath needs to be modified since 'autoload -w' is
} given an explicit path to the .zwc file

The internal implementation of autoloaded functions is unrelated to
hashing and does not retain any file paths.  It keeps only the base
names.  Where that set of names came from does not change that.

This is important to the consistent operation of fpath searching.  If
you have

    fpath=(/tmp/testfunctions ...)

and you create a new file /tmp/testfunctions/tryme, and the function
is marked for autoloading, then that new file has to be found ahead
of anything else, even if you previously used "autoload -w" on a .zwc
file that contains a "tryme" file.  The contents of fpath at the
instant of execution ALWAYS takes precedence; there is no "never get
this function from anywhere except [here]" in the autoload scheme.