zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: autoload +X[zk]
Date: Tue, 28 Mar 2000 18:27:38 +0000	[thread overview]
Message-ID: <1000328182738.ZM23045@candle.brasslantern.com> (raw)
In-Reply-To: <200003281152.NAA14996@beta.informatik.hu-berlin.de>
In-Reply-To: <200003281410.QAA20885@beta.informatik.hu-berlin.de>

On Mar 28,  1:52pm, Sven Wischnowsky wrote:
} Subject: Re: autoload +X[zk]
}
} > Note also the handling of the positional parameters. For the first
} > call (i.e.: when the init code from the file is executed) they are not 
} > set. Only for the appended function call are they set up. This is the
} > behaviour the ksh I have here shows.
} 
} Damn. That doesn't work, because the printing functions just output
} `foo "$@"' for the not-really-existing call.

And the    [[ -o kshautoload ]] || foo "$@"   trick doesn't work if we
were to really emulate that ksh behavior, either, does it?

} Hm. What are we supposed to do here? Handle positional parameters
} differently?

For now, I think the answer is:  Handle positional parameters like zsh
always has done for kshautoload (as you pointed out in 10298) and fix
the problem of accurately emulating ksh at a later time.

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


  reply	other threads:[~2000-03-28 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28 11:52 Sven Wischnowsky
2000-03-28 14:10 ` Sven Wischnowsky
2000-03-28 18:27   ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-28 11:40 Sven Wischnowsky
2000-03-27 11:27 Sven Wischnowsky
2000-03-27 10:49 Sven Wischnowsky
2000-03-27 16: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=1000328182738.ZM23045@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=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).