cut-words-keep-others

On 1 nov. 08, at 13:02, Derrick Giscloux wrote:

It depends: [route qwe], [zl filter qwe].

> Hello,
>
> I have this message:
>
> qwe 
>
> I'd like to cut "qwe" and keep 
>
> How can I do that?

I had a look at [detox] but the tag is invalid.

The structure of the messages I want to process is:

On 1 nov. 08, at 14:39, Derrick Giscloux wrote:

number ('+') of character which is not '>' ([^>] is a negative class), 

]+> means: you look for the character '
number ('+') of character which is not '>' ([^>] is a negative class),  
followed by a '>'.

this is easy to achieve with the c-string functions externals in my 

collection, here just one way of doing this:

this is easy to achieve with the c-string functions externals in my  
collection, here just one way of doing this:

It is great .. but ... I am still on 4.6.3

Thanks! 
It is great .. but ... I am still on 4.6.3

On 1 nov. 08, at 17:13, Derrick Giscloux wrote:

> It is great .. but ... I am still on 4.6.3

> Thanks!
> It is great .. but ... I am still on 4.6.3
>
> Could you post a screen capture?

how about a message box with a $2 in it?


Once again a win for regular expressions.

Can someone please refresh my memory; are there any maxMSP-specific 

I know there are books and websites and such dealing with regular 

expressions on the whole, but something specific to max, going above and 

beyond the help files would really be killer.

Perhaps as an article on cycling74.com? (if it isn't there already... ahem.)

> and take the third outlet (substrings).

Can someone please refresh my memory; are there any maxMSP-specific 
tutorials going *DEEP* into regexp use?

I know there are books and websites and such dealing with regular 
expressions on the whole, but something specific to max, going above and 
beyond the help files would really be killer.

Emmanuel Jourdan skrev:
> Just use:
>
> regexp ]+>
>
> and take the third outlet (substrings).
>
> ej
>


On 1 nov. 08, at 20:39, Andreas Wetterberg wrote:

> Once again a win for regular expressions.

> Can someone please refresh my memory; are there any maxMSP-specific 

> tutorials going *DEEP* into regexp use?

> I know there are books and websites and such dealing with regular 

> expressions on the whole, but something specific to max, going above 

> and beyond the help files would really be killer.

> Perhaps as an article on cycling74.com? (if it isn't there 

It's complicated to document such kind of thing, as you said, there 

are already tons of awesome book on the subject (I highly recommend 

"Mastering Regular Expression" from Jeffrey Friedl, O'Reilly). Note 

that in the regexp's help file of Max 5 there's a few more concret 

There's no dedicated regexp article, but you can find some funny one 

here, which will give you some ideas about what you can do:

https://cycling74.com/story/2008/6/2/161813/1326

> Once again a win for regular expressions.
>
> Can someone please refresh my memory; are there any maxMSP-specific  
> tutorials going *DEEP* into regexp use?
>
> I know there are books and websites and such dealing with regular  
> expressions on the whole, but something specific to max, going above  
> and beyond the help files would really be killer.
>
> Perhaps as an article on cycling74.com? (if it isn't there  
> already... ahem.)

It's complicated to document such kind of thing, as you said, there  
are already tons of awesome book on the subject (I highly recommend  
"Mastering Regular Expression" from Jeffrey  Friedl, O'Reilly). Note  
that in the regexp's help file of Max 5 there's a few more concret  
examples.

There's no dedicated regexp article, but you can find some funny one  
here, which will give you some ideas about what you can do:

I think you guys are thinking about this too hard.

then all you have to do is put it through a message box with $2 in it, to take the second element of the list. If it's not already a list (i.e. if it's a symbol) then just put it through a fromsymbol object first.

If the list might sometimes be longer than two elements, then just simply use a zl object. For instance, if the list is:

then just put it through a [zl slice 1] object, and take the output of the second outlet. Again, if the initial message is in symbol form, just run it through a fromsymbol object.

then all you have to do is put it through a message box with $2 in it, to take the second element of the list.  If it's not already a list (i.e. if it's a symbol) then just put it through a fromsymbol object first.

If the list might sometimes be longer than two elements, then just simply use a zl object.  For instance, if the list is:

then just put it through a [zl slice 1] object, and take the output of the second outlet.  Again, if the initial message is in symbol form, just run it through a fromsymbol object.


> I think you guys are thinking about this too hard.

Unless I'm mistaken what Derrick wants is to find elements which start 

Unless I'm mistaken what Derrick wants is to find elements which start  
with a ''.

cut words, keep others