From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs regexp problem
Date: Thu, 31 Jan 2008 17:06:35 +1100 [thread overview]
Message-ID: <8763xamsus.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 87k5lsqxem.fsf@thalassa.informatimago.com
Pascal Bourguignon <pjb@informatimago.com> writes:
> "mailpitches@email.com" <mailpitches@email.com> writes:
>
>> Hello, I'm doing an emacs replace-regexp and the regexp behaves
>> differently from how it behaves in Python, and also differently from
>> how I expect.
>>
>> I'm trying to add quotes around the parameter in a function call.
>> I.e.:
>> func(param) should be converted to func('param')
>>
>> I use the following command:
>> M-x replace-regexp [enter] get\((.*)\) [enter] get('\1')) [enter]
>>
>> and the result is func(param) is converted to func('(param)')
>>
>> Why are those extra parentheses appearing in there; is this an error
>> on emacs' part?
>
> Read the doc! (info "(emacs)Regexps")
>
> emacs regexp are more like BRE than ERE in this respect.
>
>
> Use: M-x replace-regexp RET get(\(.*\)) RET get('\1')) RET
Isn't there an extra ) at the end which shouldn't be there?
Also, note the RE's are greedy. This means you probably want to modify
the \(.*\) so that it only matches on the smallest possible match or you
could get odd results if there are any lines with multiple get()s in
them.
Tim
>
> --
> __Pascal Bourguignon__ http://www.informatimago.com/
>
> READ THIS BEFORE OPENING PACKAGE: According to certain suggested
> versions of the Grand Unified Theory, the primary particles
> constituting this product may decay to nothingness within the next
> four hundred million years.
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-01-31 6:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 18:00 Emacs regexp problem mailpitches
2008-01-29 18:50 ` Pascal Bourguignon
2008-01-31 6:06 ` Tim X [this message]
2008-01-29 19:20 ` Joel J. Adamson
2008-01-29 23:14 ` Xah Lee
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=8763xamsus.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--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.