zsh-workers
 help / color / mirror / code / Atom feed
From: Moritz Bunkus <moritz@bunkus.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: replace-regex widget not replacing semicolons
Date: Wed, 12 Jun 2013 08:46:29 +0200	[thread overview]
Message-ID: <CANPayMS5wfkjkLV640AoLtn4nCkYXQ6JxNc2-y5qcPc0Om5OOQ@mail.gmail.com> (raw)
In-Reply-To: <130611100704.ZM6617@torch.brasslantern.com>

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


      reply	other threads:[~2013-06-12  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 12:49 Moritz Bunkus
2013-06-11 17:07 ` Bart Schaefer
2013-06-12  6:46   ` Moritz Bunkus [this message]

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=CANPayMS5wfkjkLV640AoLtn4nCkYXQ6JxNc2-y5qcPc0Om5OOQ@mail.gmail.com \
    --to=moritz@bunkus.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).