zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Peter Stephenson <pws@ifh.de>
Cc: Zsh hackers list <zsh-workers@math.gatech.edu>
Subject: Re: More Configure problems
Date: Fri, 2 Aug 1996 14:03:06 +0400 (MOW)	[thread overview]
Message-ID: <Pine.SV4.3.95.960802135005.10873A-100000@itsrm1> (raw)
In-Reply-To: <199608020832.KAA23649@hydra.ifh.de>

On Fri, 2 Aug 1996, Peter Stephenson wrote:

> 
> With this set of patches perl built OK with zsh linked to sh and
> passed all tests, the process including & -d, shell escapes, etc.  I
> couldn't rewire /bin/sh, but most shell scripts during the build are
> called with an explicit `sh', so this is quite a good test.
> 

I did link /bin/sh to zsh and ran pel 5.003 Configure; it was O.K.,
including & -d, makedepend and make ;-)

But small problem with command substitution anyway. The following:

% : `
bquote> cat > foo << eof
bquote> a
bquote> eof
bquote> `
>        <-- !!!

runs perfectly on my /bin/sh (and should according to POSIX :)) but not
under zsh. (Including last three patches to heredoc an $(< ...) fix). It
wants something after the last backtick. The same problem with $() form.
If the heredoc delimiter is quoted, it is O.K. 

% : `
bquote> cat > foo << \eof
bquote> a
bquote> eof
bquote> `
%

Again in `` or $() form.

The example is probably perverse; so it just FYI

greetings

-------------------------------------------------------------------------
Andrej Borsenkow 		Fax:   +7 (095) 252 01 05
SNI ITS Moscow			Tel:   +7 (095) 252 13 88

NERV:  borsenkow.msk		E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------



  reply	other threads:[~1996-08-02 12:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-31 21:11 Announcement draft Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01  6:36 ` Bas V. de Bakker
1996-08-01  8:31   ` Peter Stephenson
1996-08-01  9:04     ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01  9:10     ` Announcement draft Andrej Borsenkow
1996-08-01 13:49       ` Here docs Peter Stephenson
1996-08-01 14:07         ` Zoltan Hidvegi
1996-08-01 16:27           ` More Configure problems Peter Stephenson
1996-08-01 17:40             ` Peter Stephenson
1996-08-01 17:55               ` Zoltan Hidvegi
1996-08-01 21:03                 ` Zoltan Hidvegi
1996-08-01 23:30                   ` Zoltan Hidvegi
1996-08-02  8:32                   ` Peter Stephenson
1996-08-02 10:03                     ` Andrej Borsenkow [this message]
1996-08-02 13:29                       ` Zoltan Hidvegi
1996-08-02  1:03             ` Zefram
1996-08-01 14:42   ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12  2:18   ` Zoltan Hidvegi
1996-08-12  4:36     ` Bart Schaefer
1996-08-12  5:00       ` Zefram
1996-08-12  6:01         ` Bart Schaefer
1996-08-12  6:34           ` Bart Schaefer
1996-08-12  6:20       ` Andrej Borsenkow

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=Pine.SV4.3.95.960802135005.10873A-100000@itsrm1 \
    --to=borsenkow.msk@sni.de \
    --cc=pws@ifh.de \
    --cc=zsh-workers@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).