zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hniksic@srce.hr (Hrvoje Niksic)
Cc: zsh-workers@math.gatech.edu
Subject: Re: quoting bug
Date: Fri, 21 Jun 1996 16:18:13 +0100 (BST)	[thread overview]
Message-ID: <14295.199606211518@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <kign31xusji.fsf@jagor.srce.hr> from "Hrvoje Niksic" at Jun 21, 96 04:43:13 pm

>Zefram (A.Main@dcs.warwick.ac.uk) wrote:
>> POSIX requires the SH_WORD_SPLIT behaviour.  It also requires field
>> splitting in normal words, as well as the result of expansions:

Actually it appears that it doesn't.  It's been a while since I read
this area of the standard, but as I had specifically looked up this
issue I thought I had remembered it correctly.  I think it would be
nice to implement this kind of field splitting anyway (predicated on
SH_WORD_SPLIT, and have POSIX_FIELD_SPLIT to get POSIX behaviour).

>What do you think of setting shwordsplit when the environmental
>variable POSIXLY_CORRECT is set?

I think that we should have a POSIX emulation mode ("emulate posix").
It would be nice to use it by default if invoked as sh with
POSIXLY_CORRECT set in the environment.  We are going to need a couple
of options for POSIX conformance that contradict sh and ksh
compatibility.

-zefram



  reply	other threads:[~1996-06-21 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-21 13:17 Raymond Nijssen
1996-06-21 13:29 ` Zefram
1996-06-21 13:55   ` Bruce Stephens
1996-06-21 14:03     ` Zoltan Hidvegi
1996-06-21 14:24       ` quoting bug, and comparisons with ksh93 Bruce Stephens
1996-06-21 14:37         ` Zoltan Hidvegi
1996-06-21 14:17     ` quoting bug Zefram
1996-06-21 14:30       ` Zoltan Hidvegi
1996-06-21 14:43       ` Hrvoje Niksic
1996-06-21 15:18         ` Zefram [this message]
1996-06-21 14:48       ` Chet Ramey
1996-06-21 16:54   ` Raymond Nijssen

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=14295.199606211518@stone.dcs.warwick.ac.uk \
    --to=a.main@dcs.warwick.ac.uk \
    --cc=hniksic@srce.hr \
    --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).