zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@nbn.com
Cc: A.Main@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu
Subject: Re: 8-bit patch for zle_tricky.c
Date: Mon, 20 May 1996 20:36:16 +0200 (MET DST)	[thread overview]
Message-ID: <199605201836.UAA05688@bolyai.cs.elte.hu> (raw)
In-Reply-To: <960520100350.ZM22705@candle.brasslantern.com> from Bart Schaefer at "May 20, 96 10:03:49 am"

> } > Adding it to $IFS has no effect in this matter, because zsh does not do
> } > field splitting on normal words.  (It should, at least if SH_WORD_SPLIT
> } > is set.)
> } 
> } I do not think so.  Neither bash nor ksh93 does this.  Look:
> } 
> } % ksh
> } $ count () { echo $# ; }
> } $ IFS=/
> } $ count as/df/gh
> } 1
> } 
> } SH_WORD_SPLIT only changes the result of substitutions.
> 
> zsh% /bin/sh
> $ IFS=/
> $ echo/bar
> bar
> $ exit/1
> zsh% echo $?
> 1
> zsh%

Yes, the original Bourne Shell used IFS in the lexer to separate words but
I think that this does not conform the POSIX Shell and Utilities standard.
Also it may be a security hole if IFS is exported.  That's why bash and
ksh does not use IFS here, and zsh should not use it either.

Zoltan



  reply	other threads:[~1996-05-20 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-18 11:51 Zefram
1996-05-19 22:34 ` Zoltan Hidvegi
1996-05-20 15:58   ` Zefram
1996-05-20 17:21     ` Zoltan Hidvegi
1996-05-20 17:03       ` Bart Schaefer
1996-05-20 18:36         ` Zoltan Hidvegi [this message]
1996-05-20 21:09           ` Zefram
1996-05-20 22:43             ` Hrvoje Niksic
1996-05-20 22:55               ` Zefram
1996-05-20 23:08                 ` Hrvoje Niksic
1996-05-20 23:36                   ` Zefram
1996-05-20 17:54       ` Zefram
1996-05-20 22:25         ` Hrvoje Niksic
1996-05-20  1:01 ` Zoltan Hidvegi

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=199605201836.UAA05688@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=schaefer@nbn.com \
    --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).