From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: Handling for ZLE modules
Date: Fri, 8 Nov 1996 08:45:37 -0800 [thread overview]
Message-ID: <961108084537.ZM12267@candle.brasslantern.com> (raw)
In-Reply-To: Peter Stephenson <pws@ifh.de> "Handling for ZLE modules" (Nov 8, 4:26pm)
On Nov 8, 4:26pm, Peter Stephenson wrote:
} Subject: Handling for ZLE modules
}
} I'm so impressed with the dynamic library code I couldn't resist
} implementing a way of allowing you to load new ZLE functions from
} modules.
Could I suggest that we immediately identify a subdirectory other than
Src/ where contributed modules can live and have their own Makefile?
I think this would be far preferable to cluttering Src/ with a bunch of
files with "mod_" prefixed to their names.
It might also be useful to have a standard (but by default not present)
directory where the build process looks for locally-supplied modules to
compile.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
next prev parent reply other threads:[~1996-11-08 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-08 15:26 Peter Stephenson
[not found] ` <pws@ifh.de>
1996-11-08 16:45 ` Bart Schaefer [this message]
1996-11-11 16:02 ` Bart Schaefer
1996-11-13 18:53 ` zle_refresh trial patch (and unrelated bug) Bart Schaefer
1996-11-14 9:03 ` Peter Stephenson
1996-11-14 14:57 ` Zefram
1996-11-08 17:16 ` Handling for ZLE modules Zefram
1996-11-08 17:26 ` Bruce Stephens
1996-11-10 23:55 ` Zoltan Hidvegi
1996-11-11 13:07 ` Peter Stephenson
1996-11-09 10:22 zle_refresh trial patch Geoff Wing
[not found] ` <gwing@primenet.com.au>
1996-11-09 17:09 ` zle_refresh trial patch (and unrelated bug) Bart Schaefer
1996-11-12 12:40 ` 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=961108084537.ZM12267@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).