From: Seweryn Kokot <sewkokot@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How modify numbers in a region by a multiplier?
Date: Thu, 1 Jul 2010 20:36:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20100701T222754-940@post.gmane.org> (raw)
In-Reply-To: AANLkTinRxWKi91S38k-I5-379RckIIQutJTBNbzL-CMt@mail.gmail.com
Juanma Barranquero <lekktu <at> gmail.com> writes:
> Qiang Guo is right, though, in pointing that you're using a fixed
> `end' but the buffer or region length is potentially changing with
> every replace.
Is there a canonical solution to this problem, since it seems that it should
happen frequently when using the following structure:
(while (re-search-forward "\\([0-9.]+\\)" end t)
(replace-match (format "%.2f" (* (string-to-number (match-string 1))
multiplier))))
I tried this in a buffer with just "1 4 5 5 4 5 4" and specifying
the multiplier of 0.001 gives
Debugger entered--Lisp error: (error "Invalid search
bound (wrong side of point)")
re-search-forward("\\([0-9.]+\\)" 14 t) ...
or modifies only a part of the buffer if the content of
the buffer is "1 4 5 5 4 5 4 " (just adding one space).
Then using my function gives
0.00 0.00 0.01 5 4 5 4
P.S. The function now is as follows:
(defun my-multiply-numbers-in-region-or-buffer (multiplier)
(interactive "nSpecify a multiplier (default is 0.001): ")
;; if nil - RET multiplier is 0.001
(let (beg end object)
(if (use-region-p)
(progn
(setq object "region")
(setq beg (region-beginning))
(setq end (region-end)))
(setq object "buffer")
(setq beg (point-min))
(setq end (point-max)))
(unless multiplier
(setq multiplier 0.001))
(goto-char beg)
(while (re-search-forward "\\([0-9.]+\\)" end t)
(replace-match (format "%.2f" (* (string-to-number (match-string 1))
multiplier))))
(message "Numbers in %s modified by multiplier %s." object multiplier)))
next prev parent reply other threads:[~2010-07-01 20:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 13:55 How modify numbers in a region by a multiplier? Seweryn Kokot
2010-07-01 14:16 ` Juanma Barranquero
2010-07-01 14:31 ` Seweryn Kokot
2010-07-01 15:56 ` Juanma Barranquero
2010-07-01 20:10 ` Seweryn Kokot
2010-07-01 20:16 ` Juanma Barranquero
2010-07-01 20:36 ` Seweryn Kokot [this message]
2010-07-01 22:38 ` Juanma Barranquero
2010-07-02 6:41 ` Seweryn Kokot
2010-07-02 9:33 ` Juanma Barranquero
2010-07-02 9:53 ` Seweryn Kokot
2010-07-02 10:05 ` Juanma Barranquero
2010-07-02 18:15 ` Štěpán Němec
2010-07-02 20:30 ` Juanma Barranquero
2010-07-05 9:49 ` Seweryn Kokot
2010-07-05 11:46 ` Juanma Barranquero
2010-07-05 13:40 ` Seweryn Kokot
[not found] ` <mailman.4.1278330410.9916.help-gnu-emacs@gnu.org>
2010-07-05 13:30 ` David Kastrup
[not found] ` <mailman.2.1278016589.8594.help-gnu-emacs@gnu.org>
2010-07-01 20:42 ` David Kastrup
2010-07-01 21:03 ` Andreas Politz
2010-07-01 15:01 ` Dan Davison
2010-07-01 20:16 ` Seweryn Kokot
[not found] ` <mailman.0.1277993821.20412.help-gnu-emacs@gnu.org>
2010-07-01 14:19 ` David Kastrup
2010-07-01 16:54 ` Qiang Guo
[not found] ` <mailman.1.1278003297.20718.help-gnu-emacs@gnu.org>
2010-07-01 18:54 ` Pascal J. Bourguignon
[not found] <mailman.0.1277992530.1006.help-gnu-emacs@gnu.org>
2010-07-01 14:19 ` Marc Mientki
2010-07-01 15:55 ` Andreas Politz
2010-07-01 16:45 ` Pascal J. Bourguignon
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=loom.20100701T222754-940@post.gmane.org \
--to=sewkokot@gmail.com \
--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).