From: TGAPE! <tgape@cyberramp.net>
To: ramos@ih4ess.ih.lucent.com
Cc: zsh-users@math.gatech.edu
Subject: Re: Perl replacement challenge
Date: Wed, 29 Oct 1997 20:20:44 +0000 (GMT) [thread overview]
Message-ID: <199710292020.UAA01581@dal-tsa14-13.cyberramp.net> (raw)
In-Reply-To: <199710291709.LAA11607@ihnns581.ih.lucent.com> from "ramos@ih4ess.ih.lucent.com" at Oct 29, 97 11:09:44 am
ramos@ih4ess.ih.lucent.com wrote:
>> ramos@ih4ess.ih.lucent.com wrote:
>>> I have a very simple and effective solution:
>>>
>>> # Use "kshdot some_ksh_script" instead of ". some_ksh_script"
>>>
>>> kshdot() { source =(ksh -c ". $* 1>&2; senv") }
>>>
>>> Where 'senv' is the following Perl script:
8><= 8><=
>> But remember you can make emulate local to a function. You might get
>> away with something like
>>
>> kshdot() { emulate ksh; setopt localoptions; . $*; }
>>
>> at least for some of the scripts.
>
> Yup, works for some scripts. But some of them go out of their way to
> try to make sure you're really running an honest ksh.
0=-ksh
Does this help? (Note: you still need emulate ksh, and you probably
will want to change it back, but it works for me in some cases. It
doesn't make the emulation better, but it tends to circumnavigate their
tests to see if you're running ksh.)
Ed
next prev parent reply other threads:[~1997-10-30 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-29 17:09 ramos
1997-10-29 20:20 ` TGAPE! [this message]
-- strict thread matches above, loose matches on Subject: below --
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
1997-10-29 17:11 ` 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=199710292020.UAA01581@dal-tsa14-13.cyberramp.net \
--to=tgape@cyberramp.net \
--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).