From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 264 invoked by alias); 24 May 2017 18:57:43 -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: 41147 Received: (qmail 21329 invoked from network); 24 May 2017 18:57:43 -0000 X-Qmail-Scanner-Diagnostics: from sub5.mail.dreamhost.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(208.113.200.129):SA:0(-2.8/5.0):. Processed in 3.082275 secs); 24 May 2017 18:57:43 -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=-2.8 required=5.0 tests=HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: tetsujin@scope-eye.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at scope-eye.net does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=scope-eye.net; h= message-id:from:to:subject:date:content-type:mime-version; s= scope-eye.net; bh=/Y8ISjCLiEQ+0h38uVnhGsSB6Nw=; b=1SH7YeXZpctkvU aNv0CqzKVLeCxBWJaqVee4THj0EMagOdMwK+VXa5CYLY3EkPrbsr9/oZN0JVA7fh e6fIxUWsp1XmGbzgbWiUhvf5NlIQykTkjkcew6Kgf1EAx5bmTcDYpizIhFcSn53s MawL1eQSK3UKXLdCCDJBYkrvzJ4CY= Message-Id: <45fd7d7b777636cd074be985ca63ccc644ee4b69@webmail.scope-eye.net> From: tetsujin@scope-eye.net To: zsh-workers@zsh.org X-Mailer: Atmail 7.8.0.1 X-Originating-IP: 50.78.252.161 Subject: Building a new ZSH module outside the ZSH source tree Date: Wed, 24 May 2017 14:57:32 -0400 Content-Type: multipart/alternative; boundary="=_fd8112ace653560055cec57e977dc66d" MIME-Version: 1.0 --=_fd8112ace653560055cec57e977dc66d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi there, I'm working on a library called "Shell-Pepper" - the idea is= =0Ato provide some added functionality to multiple different shells via= =0Aloadable modules (when it's necessary or at least beneficial to do so= )=0Aand shell scripts...=0A=0AAnyway, so far the library has just a few= commands (some of which are=0Aalready provided as part of zsh - I think= it's pretty cool that zsh=0Aalready provides a module for connecting to= Unix Domain Sockets) - and=0Aso far, only for Bash and Korn Shell. It s= eems like zsh has a fairly=0Anice programming interface for modules, but= I'm not really clear on=0Athe process for building a module without tyi= ng it into the zsh build=0Asystem.=0A=0AIn particular, the only examples= of zsh modules I have are part of the=0Azsh distribution, in Src/Module= s. Each one includes C source and=C2=A0 a=0Amodule description file (.md= d) - and sometime during the build,=0ASrc/Modules/Makefile and Makefile.= in are generated, and the contents=0Aof these (particularly the generati= on of module.mdh and module.epro)=0Aare a bit arcane. I can copy the exa= mple module and create another zsh=0Amodule in zsh/Src/Modules, and buil= d it. But because shell-pepper is=0Aaiming to support multiple shells, a= lot of its functionality is=0Afactored out into a "common" build direct= ory. I'm not sure it quite=0Afits into this build model, and I'd rather= stick to the model I've got=0Aanyway - feed the location of the build t= rees for the different shells=0Ainto my build system and build from my p= roject tree.=0A=0ASo I don't really know if there's been much call in th= e past for=0Abuilding ZSH modules outside the ZSH source tree, I don't k= now if=0Athere's a good solution for this at this point. But if somebody= on the=0Alist could help me out with this, I'd appreciate it.=0A=0A---G= EC=0A --=_fd8112ace653560055cec57e977dc66d--