all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: "B. T. Raven" <btraven@nihilo.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: regexp hell
Date: Fri, 28 Dec 2012 11:25:42 +0400	[thread overview]
Message-ID: <8638yqy6x5.fsf@w2139spb.ru.yotateam.com> (raw)
In-Reply-To: <kbjfs802enm@news4.newsguy.com> (B. T. Raven's message of "Fri, 28 Dec 2012 00:57:05 -0600")

On 28/12/2012 10:57, B. T. Raven wrote:

> I am trying to byte-compile my .emacs for the first time and I see the
> complaint "replace-string is to be used interactively..." or something.
> I am using the form:
>
>   (replace-string "\\" "\\\\" nil (point-min) (point-max))
>
> in a function and it seems to work but I can't make any equivalent re's
> work in re-search-forward (the suggested equivalent  to be used in a
> lisp programm). I can't get past the "trailing backslash" error. Is
> there something kosher for the above replace-string form?
>
> Thanks,
>
> Ed
>

You can use `search-forward' (which searches for string, not for regexp),
as it is suggested in documentation for `replace-string':

  (while (search-forward FROM-STRING nil t)
    (replace-match TO-STRING nil t))

Then with the above strings it should replace one backslash with two.

But if you still need to write a regexp, it seems that you need to
double the amount of backslashes. To include a backslash in a regexp you
need to prefix it with another backslash and each backslash should be
prefixed with another one when written in a lisp program (so, 4
backslashes in a program for a single one in regexp).

-- 
Filipp Gunbin



  reply	other threads:[~2012-12-28  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28  6:57 regexp hell B. T. Raven
2012-12-28  7:25 ` Filipp Gunbin [this message]
     [not found] ` <mailman.16202.1356679556.855.help-gnu-emacs@gnu.org>
2012-12-28 17:33   ` B. T. Raven

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=8638yqy6x5.fsf@w2139spb.ru.yotateam.com \
    --to=fgunbin@fastmail.fm \
    --cc=btraven@nihilo.net \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.