zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Bug with parameter module
Date: Sun, 05 Dec 1999 18:07:04 +0000	[thread overview]
Message-ID: <E11ug3E-0001cu-00.1999-12-05-18-06-24@mail6.svr.pol.co.uk> (raw)
In-Reply-To: "Zefram"'s message of "Sun, 05 Dec 1999 12:48:05 GMT." <E11ub5B-0003ke-00@crucigera.fysh.org>

Zefram wrote:
> Peter Stephenson wrote:
> >The shell hangs.  It seems that executing fn uses some wrapper associated
> >with the parameter module which then won't unload.
> 
> Just ignore errors; *attempt* to unload
> each module, but leave it if it doesn't unload.

That sounds reasonable.  I think the reason we need at least to attempt to
unload modules is that in general we don't know what code that can trigger;
it could in principle be something required for the shell to exit cleanly.
But I don't know if that's true (or ever will be true) in practice.  This
case is something of a counterexample to that attitude.

I found another problem while attempting to work around this.

zsh -c 'zmodload parameter; zmodload -u parameter
fn() { zmodload parameter; zmodload; }; fn'

Only the pseudo-module `zsh' shows up; parameter isn't there in the
function.  If you take away the code on the first line, it is.

This stuff makes scripts using the parameter module rather icky at the
moment, and as I'm planning on using $options to keep track of options in
the test system, it's a bit of a drag.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


  reply	other threads:[~1999-12-05 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-05  0:47 Peter Stephenson
1999-12-05  2:58 ` Bart Schaefer
1999-12-05 12:48 ` Zefram
1999-12-05 18:07   ` Peter Stephenson [this message]
1999-12-06 10:25 Sven Wischnowsky

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=E11ug3E-0001cu-00.1999-12-05-18-06-24@mail6.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).