zsh-users
 help / color / mirror / code / Atom feed
From: Andrew Main <zefram@tao.co.uk>
To: ramos@ih4ess.ih.lucent.com
Cc: zsh-users@math.gatech.edu
Subject: Re: Perl replacement challenge
Date: Wed, 29 Oct 1997 17:08:34 +0000 (GMT)	[thread overview]
Message-ID: <199710291708.RAA01142@taos.demon.co.uk> (raw)
In-Reply-To: <199710291619.KAA11548@ihnns581.ih.lucent.com> from "ramos@ih4ess.ih.lucent.com" at Oct 29, 97 10:19:56 am

ramos@ih4ess.ih.lucent.com wrote:
>	# Use "kshdot some_ksh_script" instead of ". some_ksh_script"
>
>	kshdot() { source =(ksh -c ". $* 1>&2; senv") }

How about

function kshdot {
  emulate ksh
  setopt localoptions
  . $@
}

-zefram


  parent reply	other threads:[~1997-10-29 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-29 16:19 ramos
1997-10-29 16:46 ` Peter Stephenson
1997-10-29 16:59 ` Bruce Stephens
1997-10-29 17:08 ` Andrew Main [this message]
1997-10-29 17:11 ` Bart Schaefer
1997-10-29 17:09 ramos
1997-10-29 20:20 ` TGAPE!

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=199710291708.RAA01142@taos.demon.co.uk \
    --to=zefram@tao.co.uk \
    --cc=ramos@ih4ess.ih.lucent.com \
    --cc=zsh-users@math.gatech.edu \
    /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).