From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: avoid $status and $options in POSIX mode
Date: Sun, 19 Sep 2010 14:39:43 -0700 [thread overview]
Message-ID: <100919143945.ZM25629@torch.brasslantern.com> (raw)
In-Reply-To: <100918002530.ZM29893@torch.brasslantern.com>
On Sep 18, 12:25am, Bart Schaefer wrote:
}
} I'm not entirely sure there aren't side effects of [the proposed
} autoconf/posixshell module] making the global parameter scope deeper
The worst effect I've found is that loading the module from inside a
function makes it appear that function scope has never ended. This
means the module must refuse to load except at top level, or at least
behave differently in a function.
Misc. mostly harmless things ...
- An extra prompt is printed after "exit" when interactive
- The warn_create_global option reports all undeclared parameters
- Pushed history with "fc -a -p" is popped on module unload (feature!)
- Diagnostics print line numbers as if in a function body
} Oh, a fairly large omission at this point is that it doesn't disable
} autoloads from other modules, so this does not yet solve the problem
} of $options manifesting itself.
The most obvious solution to this seems to be to walk the parameter
table looking for PM_AUTOLOAD and mask any parameter that has it.
Anyone have better suggestions?
--
next prev parent reply other threads:[~2010-09-19 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 17:33 Eric Blake
2010-09-18 3:25 ` Bart Schaefer
2010-09-18 7:25 ` Bart Schaefer
2010-09-19 21:39 ` Bart Schaefer [this message]
2010-09-20 8:45 ` 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=100919143945.ZM25629@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).