zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: "David Gómez" <david@pleyades.net>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Using zsh in gcc compilation
Date: Thu, 19 Sep 2002 16:18:52 +0100	[thread overview]
Message-ID: <16798.1032448732@csr.com> (raw)
In-Reply-To: ""David Gómez""'s message of "Thu, 19 Sep 2002 17:07:20 +0200." <20020919150720.GA14948@fargo>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

"David Gómez" wrote:
> Yes, you're right. And i think i now why. The output of genmultilib is
> different when executed by zsh or bash. It seems genmultilib use the
> $options variable to store the first positional parameter to
> genmultilib, and i'm sure you've guessed it, $options is already
> defined by zsh. I'm going to test multilib now with a different name
> instead of options, but i'm pretty sure this it's what is causing
> the problem.

That's extremely plausible --- `on' occurs very frequently in $options.

But that implies the zsh/parameter module is loaded.  It shouldn't be
doing this by default in sh emulation.  You might want to check what
startup scripts are being executed for sh mode (running with the option
-x should show this).

I'm not sure if there's a general way round this.  We would look to move
towards separate namespaces, but that needs someone to do the work.
It's a shame we didn't initially use names like zsh_options instead.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


       reply	other threads:[~2002-09-19 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020919150720.GA14948@fargo>
2002-09-19 15:18 ` Peter Stephenson [this message]
2002-09-19 15:37   ` David Gómez
2002-09-19 16:03     ` Bart Schaefer
2002-09-19 16:08       ` David Gómez
2002-09-19 16:15   ` DervishD
2002-09-19 15:12 David Gómez
2002-09-19 15:54 ` Bart Schaefer
2002-09-19 16:04   ` David Gómez
  -- strict thread matches above, loose matches on Subject: below --
2002-09-19 11:16 David Gómez
2002-09-19  9:52 David Gómez
2002-09-19 10:07 ` Peter Stephenson
2002-09-19 11:19   ` Peter Stephenson
2002-09-19 11:30     ` David Gómez
2002-09-19 12:15       ` Peter Stephenson
2002-09-19 12:43         ` David Gómez
2002-09-19 13:19           ` 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=16798.1032448732@csr.com \
    --to=pws@csr.com \
    --cc=david@pleyades.net \
    --cc=zsh-workers@sunsite.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).