From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29239-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17207 invoked by alias); 12 May 2011 14:04:46 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29239
Received: (qmail 15579 invoked from network); 12 May 2011 14:04:32 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.1
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <110512070408.ZM29757@torch.brasslantern.com>
Date: Thu, 12 May 2011 07:04:07 -0700
In-reply-to: <BANLkTin7H+ZDRug_MxZrLD_9uVcxbE+JnA@mail.gmail.com>
Comments: In reply to Mikael Magnusson <mikachu@gmail.com>
 "Re: PATCH: expanding parameters like echo/print builtins" (May 12, 12:40pm)
References: <1305118971-25617-1-git-send-email-mikachu@gmail.com>
	<20110511172114.56080d04@pwslap01u.europe.root.pri>
	<BANLkTika_BsgGtp73S2wreZjSUoRPTAx3A@mail.gmail.com>
	<20110511180748.18f4e67e@pwslap01u.europe.root.pri>
	<BANLkTik6N21VfHXxxvtJ7fRPT9omWkG=sw@mail.gmail.com>
	<20110511182657.2d1d99ae@pwslap01u.europe.root.pri>
	<BANLkTik5tXk=xUYfc7nkBCawT+sJCcmH6A@mail.gmail.com>
	<110512031050.ZM25147@torch.brasslantern.com>
	<BANLkTin7H+ZDRug_MxZrLD_9uVcxbE+JnA@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: PATCH: expanding parameters like echo/print builtins
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On May 12, 12:40pm, Mikael Magnusson wrote:
} Subject: Re: PATCH: expanding parameters like echo/print builtins
}
} On 12 May 2011 12:10, Bart Schaefer <schaefer@brasslantern.com> wrote:
} > [Is there a potential conflict where
} > (%) inserts something that (g) then incorrectly replaces, if you use
} > both of them togher?]
} 
} Well, if (%) inserts something before (g) processes it, (g) will
} replace it, but what would make it incorrect?

Specifically, are there any terminal control sequences that use a
backslash?  A quick grep of /etc/termcap seems to show that there
are some sequences (fs and ds usually, but some others) that use
a backslash.  To avoid those being interpreted as part of a (g)
escape, it might be best to have (g) occur before (%) unless the
user explicitly orders them the other way by nesting.

--