My thoughts too. I think it should work using "normal" escaping mechanisms on the command line and lead to predictable results, ie. "quoted" strings end up as symbols in Pd.
The fault could also lie in pesend which should do the escaping before sending as well. > On Mar 18, 2021, at 10:29 AM, [email protected] wrote: > > Message: 2 > Date: Thu, 18 Mar 2021 09:18:32 +0100 > From: IOhannes m zmoelnig <[email protected] <mailto:[email protected]>> > To: [email protected] <mailto:[email protected]> > Subject: Re: [PD] symbols with zero paddings and spaces > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 3/17/21 2:25 PM, Christof Ressi wrote: >> >> Note the different position of the backslash! I'm not sure if this >> particular escaping behavior is actually intended or just works by >> chance... Generally, it would be great to document Pd's string escaping, >> because it is not entirely obvious. > > > something like that was reported as > https://github.com/pure-data/pure-data/issues/1277 > <https://github.com/pure-data/pure-data/issues/1277> > > i'm pretty convinced that the backslash escaping of numbers to force > them to symbols is accidental and should not be relied on. > whenever i find the time, i would like to fix this bug. > > > gfmdasr > IOhannes -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
