Source multiline grep with pcregrep

pcregrep --color -M -N CRLF "owa_pattern\.\w+\W*\([^\)]*\)" source.sql
grep multiline in Perl regexp syntax with pcregrep
Sample Output
          IF (owa_pattern.match(v_value, trim(v_nodo_legame)||'=(.*.)', v_nodo_dir))
                    IF (owa_pattern.match(setup_rec.value, trim(mandato_rec.cod_mandato)||'=(.*.)', v_rag_soc))
                   IF (owa_pattern.match(setup_rec.value, trim(mandato_nodo_rec.cod_mandato)||'=(.*.)', v_rag_soc))
             IF ( owa_pattern.match(setup_rec.value, '(....).\[', v_value_owa) )
             IF ( owa_pattern.match(p_dati_tecnici, '=(.*.)', v_value_owa) )
             IF ( owa_pattern.match(setup_rec.value, '\[(.*.)\]', v_value_owa) )
         ret := owa_pattern.amatch(
                        line => v_pvalue,
                        from_loc => 1,
                        pat => '(\w+)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*',
         ret := owa_pattern.amatch(
                        line => v_pvalue,
                        from_loc => 1,
                        pat => '(\w+)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*(\w*)\W*',
         retval := owa_pattern.amatch(
               line => v_current_row,
               from_loc => 1, -- Start from begin
               pat => a_tr_record(v_tr_record_ind).regex_compil,
                  v_step := '2.3. owa_pattern.getpat ("'||v_pattern||'", v_pat)';
                  owa_pattern.getpat (v_pattern, a_tr_record(v_tr_record_ind).regex_compil);
                  v_step := '2.4. owa_pattern.getpat ("", v_pat)';
                  owa_pattern.getpat (v_pattern, a_tr_record(v_tr_record_ind).regex_compil);

By: hute37
2010-11-11 12:53:40

What Others Think

without need to install grep variant pcregrep, you can do multiline search with grep. grep -Pzo "(?s)^(\s*)\N*main.*?{.*?^\1}" *.c Explain: -P activate perl-regexp for grep (a powerful extension of regular extensions) -z supress newline at the end of line, subtituting it for null character. That is, grep knows where end of line is, but see input as a big one line. -o print only matching. Because using -z, all file is like a big line, so if there is a match, all file would be printed, this way it don't. in regexp: (?s) activate PCRE_DOTALL, which means that '.' find any character or newline \N find anything except newline, even with PCRE_DOTALL activated .*? find '.' in nongreedy mode, that is, stops as soon as possible. ^ find start of line \1 backreference to first group (\s*) This is a try to find same indentation of method As you can imagine, this print the main method in a C (*.c) source file.
unixmonkey24864 · 526 weeks and 2 days ago
grep version is very cool ;) i like the trick to match closing brace with backreferences ...
hute37 · 526 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: