From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: A variant of match-end, but after replacement?
Date: Sun, 19 Jul 2015 16:18:08 -0400 [thread overview]
Message-ID: <barmar-E1B534.16180819072015@88-209-239-213.giganet.hu> (raw)
In-Reply-To: mailman.7160.1437335923.904.help-gnu-emacs@gnu.org
In article <mailman.7160.1437335923.904.help-gnu-emacs@gnu.org>,
Marcin Borkowski <mbork@mbork.pl> wrote:
> On 2015-07-19, at 15:41, Pascal J. Bourguignon <pjb@informatimago.com> wrote:
>
> > Marcin Borkowski <mbork@mbork.pl> writes:
> >
> >>> (let ((old-end (prog1 (match-end 1)
> >>> (replace-match "newtext" t t string 1))))
> >>> (do-something old-end))
> >>
> >> Still not there - I can't assume that "newtext" will have the same
> >> length as the thing it replaced...
> >
> > Sorry, I misread what you wanted.
> >
> > (let ((new-end (+ (prog1 (match-beginning 1)
> > (replace-match new-text t t string 1)))
> > (length new-text)))
> > (do-somthing-from new-end))
>
> Thanks! That's easy, and indeed it will work, since the length of the
> replacement is fixed in my use-case.
Yeah, this would be trickier if new-text contained back-references.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2015-07-19 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7146.1437306572.904.help-gnu-emacs@gnu.org>
2015-07-19 12:06 ` A variant of match-end, but after replacement? Pascal J. Bourguignon
2015-07-19 12:22 ` Marcin Borkowski
2015-07-19 13:25 ` Marcin Borkowski
2015-07-20 10:46 ` Nicolas Richard
[not found] ` <mailman.7147.1437308571.904.help-gnu-emacs@gnu.org>
2015-07-19 12:30 ` Pascal J. Bourguignon
2015-07-19 13:20 ` Marcin Borkowski
2015-07-19 13:26 ` Dmitry Gutov
2015-07-19 19:57 ` Marcin Borkowski
[not found] ` <mailman.7150.1437312076.904.help-gnu-emacs@gnu.org>
2015-07-19 13:41 ` Pascal J. Bourguignon
2015-07-19 19:58 ` Marcin Borkowski
[not found] ` <mailman.7160.1437335923.904.help-gnu-emacs@gnu.org>
2015-07-19 20:18 ` Barry Margolin [this message]
2015-07-19 22:45 ` Pascal J. Bourguignon
2015-07-20 0:06 ` Marcin Borkowski
[not found] ` <mailman.7165.1437350800.904.help-gnu-emacs@gnu.org>
2015-07-20 0:33 ` Pascal J. Bourguignon
2015-07-19 11:49 Marcin Borkowski
2015-07-19 20:23 ` Dmitry Gutov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=barmar-E1B534.16180819072015@88-209-239-213.giganet.hu \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).