zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Compinstall, zcompile, and my .zshrc
Date: Mon, 10 Apr 2000 11:05:38 +0200 (MET DST)	[thread overview]
Message-ID: <200004100905.LAA32597@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 10 Apr 2000 08:54:15 +0000


Bart Schaefer wrote:

> On Apr 10, 10:37am, Sven Wischnowsky wrote:
> } 
> } Bart Schaefer wrote:
> } 
> } > Second, it'd be nice if I could do something like
> } > 
> } > 	zcompile .zshrc.zwc .zshrc .zsh/*
> } 
> } As for loading functions from a zwc files it checks if the (basename
> } of the) name of the sourced file is in the zwc file. And the loads it.
> } In other words, you can use symbolic links:
> } 
> }   zcompile .zshrc.zwc .zshrc .zsh/*
> }   for i in .zsh/*; do ln -s .zshrc.zwc ${i}.zwc; done
> 
> But how clever is that?  I mean, the file's still going to be read and/or
> mapped multiple times; is it really any better than compiling them all as
> separate .zwc files?

No, currently not. Hm, we could make the functions that looks if a zwc 
file is already mapped check if the file is the same as one of the
files already mapped usin stat, not only comparing filenames.

When they are read using one digest file doesn't have any advantages,
though.


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-04-10  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-10  9:05 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-10  8:37 Sven Wischnowsky
2000-04-10  8:54 ` Bart Schaefer
2000-04-10  3:48 Bart Schaefer

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=200004100905.LAA32597@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).