From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11967 invoked by alias); 27 Sep 2015 16:44:21 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36661 Received: (qmail 26695 invoked from network); 27 Sep 2015 16:44:21 -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=hUIrb0A24LIbFNLLwY9EXR1GalGfvzIcxaiDDCu1fIc=; b=g4TFPyT+jTyEnwdUpQio4tcSxqSYXlKtAAKUUGgVauDs7HzjokB6eNvQDLeoPto3+5 L7s+3MXBAKABdGpydQx7A8jIU5tdEfWWtxePoynisOJ/+yKT9Ult0kD/2g+ZZffZPwpN +lmCeT8jOJgH3ZD+MKKzO/JQWfkNXqgdRSc3js8E1FS4oluW6RHPuaDiuF9ESSQAU88O qGOX2+roqHbO/ZxkCXx25M342tkfRvcvyiiAMLM25GMK4tViVmYqNv3gZ2JiWprG3IMP bXvhlS4DPM7/Dhr69XSvgG88z3MdEtrCqFA4gCT/L9BgGmB6NDUCQ17Q7SFQda7shdtf ZcQA== X-Gm-Message-State: ALoCoQk9BQJLcD4E4ppGaUY8qKOrrBb1egv+S0L1jrbDOKDj30fiaChL698Y2/HecC1J5klZw8Op X-Received: by 10.202.48.210 with SMTP id w201mr8130441oiw.115.1443372258325; Sun, 27 Sep 2015 09:44:18 -0700 (PDT) From: Bart Schaefer Message-Id: <150927094415.ZM25752@torch.brasslantern.com> Date: Sun, 27 Sep 2015 09:44:15 -0700 In-Reply-To: <20150927162835.4297b94c@ntlworld.com> Comments: In reply to Peter Stephenson "Re: Static link of curses module" (Sep 27, 4:28pm) References: <20150927162835.4297b94c@ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Static link of curses module MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 27, 4:28pm, Peter Stephenson wrote: } } Typically, you'd do this by editing config.modules rather than the .mdd config.modules is generated from the .mdd and then is what gets used at build time, so yeah. } I'm not sure how this is supposed to work. I can see the module being } registered automatically, but I don't see any evidence that there } was ever a mechanism for running the request "load_module" based on } load=yes. Yeah, I don't think that was ever what it was intended to mean. I think the intent was that if the module has autoloads, then you don't have to declare them with "zmodload -a". It doesn't imply that load_module() is actually called. Look at the modules that have "load=yes" in the default .mdd file: rlimits sched parameter termcap terminfo zutil (plus several in Zle) Those all have autofeatures declared. Then look at curses.mdd -- it has "autobins" instead. No other .mdd file has "autobins". I think curses.mdd just got overlooked when we converted to the features mechanism. Try this? diff --git a/Src/Modules/curses.mdd b/Src/Modules/curses.mdd index 669c4f5..80c8f86 100644 --- a/Src/Modules/curses.mdd +++ b/Src/Modules/curses.mdd @@ -2,7 +2,7 @@ name=zsh/curses link='if test "x$ac_cv_func_initscr" = xyes && test "x$zsh_cv_path_curses_header" != x; then echo dynamic; else echo no; fi' load=no -autobins="zcurses" +autofeatures="b:zcurses" objects="curses.o"