Jeff - Thanks for the in depth reply - I'll leave my wording at "don't use
spaces in the machine name". I was smart enough to figure out thats what
caused my problem but a rookie still apprehensive would likely give up at that
point. I actually understand what you explained - I must be getting my brain
back into the thought processing I used to have it trained to do when I was
writing QuickBasic programs as a kid. When 2.3 comes out I'll have to install
and revise my tutorial accordingly.
Must be nasty weather in other places - people are posting back quite a bit -
that or I'm just popular! (I know - it has to be the former rather than the
latter :-L ) Weather is nice here (right now) wish I was allowed to go jumping
around but hey EMC2 gets my talents for a bit :) I'd be in the garage
machining myself if the doctor hadn't said no-no to that for at least 2 or 3
days.
Greg
www.distinctperspectives.com
----- Original Message -----
From: Jeff Epler
To: Enhanced Machine Controller (EMC)
Sent: Saturday, August 02, 2008 1:44 PM
Subject: Re: [Emc-users] Possible bugreport needed?
On Sat, Aug 02, 2008 at 12:43:44PM -0400, Stephen Wille Padnos wrote:
> This bug has been fixed in TRUNK, so it will be in EMC2 2.3 for sure.
> I'm not sure if it's an oversight or if there's a "good reason" why the
> fix hasn't been backported to the 2.2 branch. If it's just an
> oversight, the fix will be in 2.2.6, which will be released before 2.3.
Allowing spaces in configuration paths required a change to halcmd
parsing that might break some working configurations. For this reason,
I have so far chosen not to put the fix in version 2.2.
Basically, the emc runscript executes something like this:
halcmd loadusr io -ini "$INIFILE"
Let's say that infile is "/bad idea.ini". "/bad idea.ini" goes to the
'halcmd' program as a single positional argument, but halcmd then does a
round of parsing and turns it into two arguments: "/bad" and "idea.ini".
The change causes halcmd not do to this parsing, and thus avoid
splitting the word again.
However, this can affect valid halcmd invocations, because before this
change you could write
halcmd "loadusr and2 count=1"
or
halcmd loadusr and2 count=1
in a shell script and get the same result. After my change, the first
command will be an error because "loadusr and2 count=1" (the whole thing
taken as one argument) doesn't name a valid command.
Jeff
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
