Autom8 Tree Rules and multi-line Notes fields

[gninja]

I've got my host.notes field populated with multi-line text similar to:

Code: Select all

Location:soma
Product:downloads
Purpose:www

I've got a tree rule that should be creating a 'soma' branch on the Location tree, but I can't seem to find a clean way to deal with the multi-line output.

My Matching pattern is currently:

Code: Select all

^.*Location:(.*?)\s.*$

and my Replacement pattern is:

Code: Select all

${1}

But I end up with a tree leaf named:

Code: Select all

soma Product:downloads Purpose:www

If I update the matching pattern to explicitly check for product & purpose:

Code: Select all

^.*Location(.*?)\nProduct:.*\nPurpose:.*$

.. then it creates the right Tree branch, but if I expand the data I'm storing in the notes field, then I'll have to keep updating the notes field.

Any advice on how to more cleanly accomplish this?

[gandalf]

You're ending the rexexp by searching for a \s (whitespace); but not searching for an LF while "soma" seems to be directly followed by an LF. Well, it may happen, that php-regexp acts a bit strange ... not sure ...
R.

[gninja]

Yes. I'm looking for a way to get it to be greedy about matching text and multiple newlines.

[gninja]

The results I'm getting make it seem like it doesn't matter if I use \n or \s in the match string.

[gandalf]

Does this help:
http://de2.php.net/manual/en/function.preg-match.php

//match newline control character:
preg_match('/\n/','\n'); //pattern matches and is stored as control character 0x0A in the pattern string
preg_match('/\\\n/','\n'); //very same match, but is stored escaped as 0x5C,0x6E in the pattern string

R.

[gninja]

Nope. I seem to have solved it with this, though:

Code: Select all

.*Location:(.*?)\n(.*[\n]?)+

[gandalf]

fine, then
R.