From: Igor Sosa Mayor <joseleopoldo1792@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: regex edit mode
Date: Tue, 30 Sep 2014 19:55:10 +0200 [thread overview]
Message-ID: <87iok50z9d.fsf@gmail.com> (raw)
In-Reply-To: 00d69071-b746-4544-a4b6-01fc9e29e5a3@googlegroups.com
Sam Halliday <sam.halliday@gmail.com> writes:
> Hi all,
>
> It is sometimes confusing, when writing a regex in elisp, to remember all the escaping rules that are in play.
>
> Does anybody on this list know of a minor mode that would allow the
> user to edit regexes so that escaping is not necessary, but for the
> escaping to occur "under the hood".
>
> Imagine being able to place the point over a string containing a regex
> (which is using escapes) and then call an interactive function which
> makes the escape characters go away and if special characters are
> entered, the escapes are added automagically. When exiting the minor
> mode, the raw string with escapes would appear again.
>
> It would be equally fantastic to be able to do this for other languages that have their own escaping rules: java/scala come to mind.
>
> Just a thought. It would really brighten up my day if it were possible.
not exactly what you are looking for, but... do you know this function?
,----[ C-h f regexp-builder RET ]
| regexp-builder is an alias for `re-builder' in `re-builder.el'.
|
| (regexp-builder)
|
| Construct a regexp interactively.
| This command makes the current buffer the "target" buffer of
| the regexp builder. It displays a buffer named "*RE-Builder*"
| in another window, initially containing an empty regexp.
|
| As you edit the regexp in the "*RE-Builder*" buffer, the
| matching parts of the target buffer will be highlighted.
|
| [back]
`----
--
:: Igor Sosa Mayor :: joseleopoldo1792@gmail.com ::
:: GnuPG: 0x1C1E2890 :: http://www.gnupg.org/ ::
:: jabberid: rogorido :: ::
next prev parent reply other threads:[~2014-09-30 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 16:55 regex edit mode Sam Halliday
2014-09-30 17:55 ` Igor Sosa Mayor [this message]
2014-09-30 18:18 ` Rasmus
2014-09-30 19:10 ` Marcin Borkowski
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=87iok50z9d.fsf@gmail.com \
--to=joseleopoldo1792@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).