Fixed. Unfortunately, as this is a bug in rosparam, the fix won't go out until the next release. I'll try and do a ROS 1.0.x patch update soon. - Ken On Tue, Apr 13, 2010 at 9:34 AM, Ken Conley wrote: > You're right, going back through the code I realize that I tried to > circumvent this optparse issue, bug my workaround is faulty. I'll > update the ticket > >  - Ken > > On Tue, Apr 13, 2010 at 9:30 AM, Blaise Gassend wrote: >> That doesn't work for me: >> {{{ >> blaise@bnl: /wg/stor5/blaise $ rosparam set /longitude -- -97.728524 >> Usage: rosparam set [options] parameter value >> >> rosparam: error: invalid arguments. Please specify a parameter value >> }}} >> >> And the fact that only negatives starting with 9 are a problem suggests >> that something stranger is going on. >> >> On Tue, 2010-04-13 at 09:25 -0700, Ken Conley wrote: >>> The issue is telling optparse that options are over: >>> >>> rosparam set /longitude -- -97.728524 >>> >>> Not the most obvious solution, blame POSIX :) >>> >>>  - Ken >>> >>> On Tue, Apr 13, 2010 at 8:21 AM, Jack O'Quin wrote: >>> > Maybe I'm overlooking something obvious here, but this fails: >>> > >>> > $ rosparam set /longitude -97.728524 >>> > Usage: rosparam set [options] parameter value >>> > >>> > rosparam: error: no such option: -9 >>> > >>> > Is there some trick? Quoting does not help. >>> > >>> > I can rosparam load the value from a YAML file, but I still wonder how >>> > to do it from the command line. >>> > -- >>> >  joq >>> > _______________________________________________ >>> > ros-users mailing list >>> > ros-users@code.ros.org >>> > https://code.ros.org/mailman/listinfo/ros-users >>> > >>> _______________________________________________ >>> ros-users mailing list >>> ros-users@code.ros.org >>> https://code.ros.org/mailman/listinfo/ros-users >> >> >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> >