From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13247 invoked by alias); 12 Jun 2013 06:46:50 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31473 Received: (qmail 18948 invoked from network); 12 Jun 2013 06:46:36 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at bunkus.org designates 78.46.80.115 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bunkus.org; s=mail2013040101; t=1371019591; bh=pBDhTI3yrHxnt4FlptQgdW5FAiicZMto8nAZaadDEpg=; h=In-Reply-To:References:Date:Subject:From:To:Cc; b=Fd/3w2b90o/8LUjvS1fn50FxqRhYZ2gOTZQjzBSB6aYUV1rb6tw9AgEE4X0S4iVOm h3XG2i5xpRegz472Vu6+2yF33AEJfz61Uln8eDwa+AoxFOHwSJnczRBv7kHv00MD+4 ogh+aEea/6kJdqmb8ShhV3ssE/aSJOjmOs2r9/KU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pBDhTI3yrHxnt4FlptQgdW5FAiicZMto8nAZaadDEpg=; b=HxooKfZRcfV3KGlYBtKXrBvYdJ4qV5FcX/i9lUeVuibHfZ1JF5cJlt2k8tU5A9LQne pGTbxOXno847w0tEyoyL7f1Qo+x4xt7kt44fSJTtpdj6cNnIdE1iGJ+M+8MnkazXicJf 6x73kk5THFJMyvRtCvcp53Xbf81lm/XmWKGjkoqLArM0SUW6JOy2mqkid5nN9dIU9QR8 5WJD8lS2qpMEfFwS7foHnumV77WiJq61dAqmdI0GL5Xj4ZwSrij1vvAMI9RInBbrmb23 Bxz3AXZ+78BRVSV8m1xsQjeXhBnXCROTZl40Sl/AzXcikZEJiS+GEP0qbxtBKEDwLPHk ivnw== MIME-Version: 1.0 X-Received: by 10.68.179.99 with SMTP id df3mr17772576pbc.198.1371019589479; Tue, 11 Jun 2013 23:46:29 -0700 (PDT) In-Reply-To: <130611100704.ZM6617@torch.brasslantern.com> References: <130611100704.ZM6617@torch.brasslantern.com> Date: Wed, 12 Jun 2013 08:46:29 +0200 Message-ID: Subject: Re: replace-regex widget not replacing semicolons From: Moritz Bunkus To: Bart Schaefer Cc: zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 Hey, thanks for the thorough analysis. I haven't been aware that & is used for representing the various matched parts, I'm used to $... (Perl) or \... (the usualy Unix tools). Reading the documentation about replace-string and friends I now see & being mentioned, so yes, it does make sense. Sorry for not going there first. Kind regards, mosu