From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hzoli@cs.elte.hu (Zoltan Hidvegi)
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 16:58:02 +0100 (BST) [thread overview]
Message-ID: <4464.199605201558@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199605192234.AAA00866@hzoli.ppp.cs.elte.hu> from "Zoltan Hidvegi" at May 20, 96 00:34:48 am
>Well I do not think that this bug is serious. The biggest advantage of
>metafication is that does not requite significant changes in the lexer. I
>see that in your patch you added IBLANK, INBLANK and ISPECIAL types to the
>null character. I still think that null only needs IMETA. Adding IBLANK
>just complicates thinkg in the lexer and I do not think it is necessary.
The bug has effect regardless of whether NUL is treated as a blank or
not. I added the IBLANK etc. bits on the grounds that NUL ought to be
treated as a blank, just as it's in $IFS. But the shell is indeed
perfectly usable either way, so I won't contest this issue.
>You may ask then why I added it to IFS. The main reason for that was that
>nulls cannot be passed in arguments to external commands. But
>iblank/inblank used only on the shell input which does not have this
>limitation.
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.)
-zefram
next prev parent reply other threads:[~1996-05-20 16:22 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 [this message]
1996-05-20 17:21 ` Zoltan Hidvegi
1996-05-20 17:03 ` Bart Schaefer
1996-05-20 18:36 ` Zoltan Hidvegi
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=4464.199605201558@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=hzoli@cs.elte.hu \
--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).