[PD] Easy way to list used abstractions in patch?
jlistshit
jlistshit at kliklak.net
Thu Jul 27 20:40:51 CEST 2017
Thank you Miller,
that’s at least a better way than going through all by hand and try to list what one finds… that process usually results in missing things here.
Should i file a feature request?
+1
I think everyone would be happy to see this, and it would make PD more accessible for non-programmers, too.
Thank you for all you do.
jayrope
- - -
www.jayrope.com
www.aircushionfinish.com
www.ello.co/jayrope
On Jul 27, 2017, at 19:33, Miller Puckette <msp at ucsd.edu> wrote:
> This is always a pain, sorry - I often want to do this too. I do it this
> way: set "verbose" flag, load the patch, copy all the messages into a
> file, then "grep succeeded <file>", then sort. The linux/Mac sort
> program has a "-u" flag (unique) that suppresses repeats.
>
> But Pd ought to offer a simpler way to do this :)
>
> cheers
> Miller
>
> On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote:
>> I have a simple question, is there an easy way to list used abstractions of a patch?
>>
>> I oftenly pass on patches to fellow musicians and finding used abstractions per patch can be sticky business - i’d like to not send all abstractions i ever made instead :)
>> Thanx for any hints!
>>
>> jayrope
>> - - -
>> www.jayrope.com
>> www.aircushionfinish.com
>> www.ello.co/jayrope
>>
>>
>>
>>
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
More information about the Pd-list
mailing list