zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: parser (was: Re: PATCH: Improved _mailboxes)
Date: Thu, 24 Feb 2000 18:08:52 +0000	[thread overview]
Message-ID: <1000224180852.ZM22044@candle.brasslantern.com> (raw)
In-Reply-To: <200002240907.KAA32439@beta.informatik.hu-berlin.de>

On Feb 24, 10:07am, Sven Wischnowsky wrote:
} Subject: RE: PATCH: parser (was: Re: PATCH: Improved _mailboxes)
}
} 
} Andrej Borsenkow wrote:
} 
} > zcodeload file

Let's not do that, shall we?  Let's stick with autoload and have a file
suffix convention, like emacs' .el and .elc, or something.  Heck, there
could even be separate fpath and compiled_fpath or ...

} All this also makes me think about a way to allow multiple zsh's to
} share other memory bits (like the command table and so on). How
} portable is anonymous shared mmap or shared mmap on /dev/null?

Do we really want to go down the road of having e.g. zmodload in one
zsh suddenly make new builtins available to another zsh?  I don't want
the behavior of a script that's running in the background to change
because of something I loaded into my foreground shell ...

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


  reply	other threads:[~2000-02-24 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-24  9:07 Sven Wischnowsky
2000-02-24 18:08 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-25  8:41 Sven Wischnowsky
2000-02-25  9:55 ` Andrej Borsenkow
2000-02-24 10:03 Sven Wischnowsky
2000-02-24  8:54 Sven Wischnowsky
2000-02-23 13:21 Sven Wischnowsky
2000-02-23 16:45 ` Bart Schaefer
2000-02-23 18:58 ` Peter Stephenson
2000-02-24  7:47 ` Andrej Borsenkow

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=1000224180852.ZM22044@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).