Hey guys,
I'm having problems porting a PD patch from Linux to Osx(!) and I think it may be something to do with gatom. Is there a limit to the length of gatom? My patch involves a lot of shell operations (using ggee/control/shell - the osx version appears to have only one outlet, is there a reason?) and I can only make gatom 80 characters long. I think this is why a * appears in my pathnames at the 80th character, e.g. /Users/patricksutherland/Documents/Edkelly/testinput/Andrew Sachs/excerpts/Ex-*
On the other hand this is coming from a [ makesymbol %s-voicing] where the %s is another path.
It works fine under Linux, but in osx things don't work! Anyone know why/how to fix it?
Best, Ed
-> -> --> ---> -----> --------> -------------> r3search + praktik EK5perimenz
How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
On Thu, Nov 03, 2005 at 04:36:34PM +0000, Ed Kelly wrote:
patch involves a lot of shell operations (using ggee/control/shell - the osx version appears to have only one outlet, is there a reason?) and I can only make gatom 80 characters long. I think this is why a * appears in my pathnames at the 80th character, e.g. /Users/patricksutherland/Documents/Edkelly/testinput/Andrew Sachs/excerpts/Ex-*
On the other hand this is coming from a [ makesymbol %s-voicing] where the %s is another path.
It works fine under Linux, but in osx things don't work! Anyone know why/how to fix it?
i couldnt get shell to work how i wanted on linux, or to work at all on windows, so i made a [popen] which is in CVs.. you could try that, but be warned it is not threaded at all, yur pd will 'freeze' while its waiting for return..
your [shell] issue is probably not too complicated, maybe an OSX user can figure it out :)
carmen wrote:
make gatom 80 characters long. I think this is why a * appears in my pathnames at the 80th character, e.g. /Users/patricksutherland/Documents/Edkelly/testinput/Andrew Sachs/excerpts/Ex-*
this is an issue with [print] (as has been discussed several times on this list(and others)).
it has _nothing_ to do with the theoretical length of symbols and/or [symbol\
no big help though...
mfg.adsr. IOhannes
Found the problem with the character length!
[ makesymbol] has a maximum character length of 80. I inserted a 1 in the source code (180) and re-compiled
paths.
The shell problem persists - I'll try to get popen or shell working for osx with a [ done( right outlet - tomorrow (need food now!)
Best, Ed
-> -> --> ---> -----> --------> -------------> r3search + praktik EK5perimenz
___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
It seems that 80 is quite short for [makesymbol]. Any reason not to
make it longer? I think most filesystems have a limit of 256 chars for
filenames, for example.
.hc
On Nov 3, 2005, at 12:43 PM, Ed Kelly wrote:
Found the problem with the character length!
[ makesymbol] has a maximum character length of 80. I inserted a 1 in the source code (180) and re-compiled
- job done! I no longer get a * at the end of my file
paths.
The shell problem persists - I'll try to get popen or shell working for osx with a [ done( right outlet - tomorrow (need food now!)
Best, Ed
-> -> --> ---> -----> --------> -------------> r3search + praktik EK5perimenz
___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with
voicemail http://uk.messenger.yahoo.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into the
possession of everyone, and the receiver cannot dispossess himself of
it."
- Thomas
Jefferson
Hans-Christoph Steiner wrote:
It seems that 80 is quite short for [makesymbol]. Any reason not to
make it longer? I think most filesystems have a limit of 256 chars for
filenames, for example.
well, for filenames use [makefilename] ;-)
seriously, i have no idea why there is this 80 characters limit. i have now changed it to MAXPDSTRING (in CVS)
probably it would be a nice idea to make this resettable by the user.
mfg.asdr IOhannes