Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [bug] backslash stripped in sh/ksh emulation
- X-seq: zsh-workers 21866
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [bug] backslash stripped in sh/ksh emulation
- Date: Tue, 11 Oct 2005 14:43:42 +0000
- In-reply-to: <20051011123624.70fc9626.pws@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20051011083842.GA5380@sc> <20051011123624.70fc9626.pws@xxxxxxx>
On Oct 11, 12:36pm, Peter Stephenson wrote:
}
} So I've introduced a variant of Bnull, the ghost of a backslash, called
} Bnullkeep.
I was a bit skeptical of this when I read the description, but looking at
the patch I think it's actually OK. This shouldn't change anything when
GLOB_SUBST is not set, right?
} Nonetheless, this doesn't give me a warm, fuzzy feeling. If anyone can
} think of places where this might have the wrong effect...
subst.c and exec.c seem to be the only source files that mention both
INULL and GLOBSUBST, or call shtokenize() [exec.c only when GLOBSUBST
is set]. So on first blush I think you've covered it nicely.
} (It's just possible we could get away with only using Bnullkeep by suitable
} changes, simplifying the code a bit.)
Did you mean "only using Bnull"? Otherwise I don't follow.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author