unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: regexp on emacs how to...
Date: Mon, 01 Sep 2014 16:24:51 +0800	[thread overview]
Message-ID: <87oauzlpd8.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 941334fe-5c17-4777-aa91-312533ae0500@googlegroups.com

renato.pontefice@gmail.com writes:

> Il giorno domenica 31 agosto 2014 00:39:00 UTC+2, Thorsten Jolitz ha scritto:
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>> 
>> 
>> 
>> > This might give some false positives, but not miss any tags:
>> 
>> >
>> 
>> > "\\[-[^^\000]+?-]"
>> 
>> 
>> 
>> Ups, this should actually be:
>> 
>> 
>> 
>> "\\[-[^\000]+?-]"
>> 
>> 
>> 
>> -- 
>> 
>> cheers,
>> 
>> Thorsten
>
> It doesen't work :-(
>
> can you try to explain me what kin of search try to do this expression?

In cases like this, regexp-builder can often be useful. Go to the buffer
containing your RTF text, M-x regexp-builder, and then start building
your regexp incrementally. Many times this is enough to show you what
was wrong with the original one.




  reply	other threads:[~2014-09-01  8:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 21:01 regexp on emacs how to renato.pontefice
2014-08-30 22:17 ` Thorsten Jolitz
2014-08-30 22:39   ` Thorsten Jolitz
     [not found]   ` <mailman.7955.1409438369.1147.help-gnu-emacs@gnu.org>
2014-09-01  8:15     ` renato.pontefice
2014-09-01  8:24       ` Eric Abrahamsen [this message]
2014-09-01  9:14         ` Thorsten Jolitz
2014-09-01  9:10       ` Thorsten Jolitz
     [not found]       ` <mailman.8023.1409562921.1147.help-gnu-emacs@gnu.org>
2014-09-01 10:11         ` renato.pontefice
2014-09-01 10:28           ` Thorsten Jolitz
2014-09-01 10:38           ` Álvar Ibeas
2014-09-01  9:56 ` Nicolas Richard
     [not found]   ` <CAF83ECB74PD7An-scqk74gN4YzrGC9DW8at1-cCFzV1utYSFRQ@mail.gmail.com>
2014-09-02 10:53     ` Nicolas Richard
     [not found]     ` <874mwrrudt.fsf@yahoo.fr>
     [not found]       ` <CAF83ECB2NbV0QdCbd0H8Z-PJB0ZbYboswpjFudc__9JQH+P=1Q@mail.gmail.com>
2014-09-02 11:03         ` Nicolas Richard
     [not found]         ` <mailman.8096.1409655669.1147.help-gnu-emacs@gnu.org>
2014-09-03  9:24           ` renato.pontefice
2014-09-03  9:25             ` renato.pontefice
2014-09-03 10:47               ` Nicolas Richard
     [not found]               ` <mailman.8184.1409741111.1147.help-gnu-emacs@gnu.org>
2014-09-04 10:48                 ` Renato Pontefice
2014-09-05 12:02                   ` Nicolas Richard
     [not found]                   ` <mailman.8325.1409918483.1147.help-gnu-emacs@gnu.org>
2014-09-10  8:55                     ` Renato Pontefice
2014-09-10 10:01                       ` Nicolas Richard
     [not found]                       ` <mailman.8606.1410343132.1147.help-gnu-emacs@gnu.org>
2014-09-10 10:20                         ` Renato Pontefice
2014-09-10 13:52                           ` Nicolas Richard
     [not found]                           ` <mailman.8618.1410357057.1147.help-gnu-emacs@gnu.org>
2014-09-11  7:29                             ` Renato Pontefice

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=87oauzlpd8.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.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.
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).