zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Will Day <willday@rom.oit.gatech.edu>, zsh-workers@sunsite.auc.dk
Subject: Re: two sets of modules under /usr/local/lib/zsh ?
Date: Sat, 9 Sep 2000 16:05:49 +0000	[thread overview]
Message-ID: <1000909160549.ZM139@candle.brasslantern.com> (raw)
In-Reply-To: <20000908234850.A16212@rom.oit.gatech.edu>

On Sep 8, 11:48pm, Will Day wrote:
}
} And I guess I'm wondering, if these are only for backwards compatibility,
} (a) do I need them, if I never used paths for modules anywhere

What do you mean by "I never used paths for modules anywhere" ?

If you mean "I used modules, but never by their paths" then if you don't
have the alias modules you'll have to change your startup files or any
other places where you used modules, to use the zsh/modulename form.
You'll eventually need to do that anyway, though, because as Zefram said
the alias module files went away in 3.1.9-dev-5, replaced by an internal
aliasing mechanism ("zmodload -A").

If you mean "I never used the zmodload command" then you don't need them.

} Also, I guess I'm a little curious about it all, since the new path:
}    /usr/local/zsh/3.1.9/zsh/cap.so
} 
} seems a little unnecessarily redundant, with two "zsh"'s in there.

It's an attempt to be forward-looking, so that other modules that are
not part of the zsh "package" can be distrubuted under separate module
hierarchies, but all live under /usr/<whatever>/zsh/<version>/.


-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      parent reply	other threads:[~2000-09-09 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-09  3:48 Will Day
2000-09-09  9:26 ` Zefram
2000-09-09 19:44   ` Will Day
2000-09-09 16:05 ` Bart Schaefer [this message]

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=1000909160549.ZM139@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=willday@rom.oit.gatech.edu \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).