The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Looks like a bug. I tried to replicate the problem and can confirm the same behaviour.
Seems the issue is somewhere in setup.sh and/or in the files it implicitly sources. It unsets the ROS_WORKSPACE variable exported at the beginning. Even if you specify ROS_WORKSPACE by hand it will be deleted after sourcing the setup.bash.
To make roscd work without arguments I can suggest you to set ROS_WORKSPACE explicitly in your .bashrc after the line that sources the relevant setup file.
| | 2 | No.2 Revision |
Looks like a bug. I tried to replicate the problem and can confirm the same behaviour.
Seems the issue is somewhere in setup.sh and/or in the files it implicitly sources. It unsets the ROS_WORKSPACE variable exported at the beginning. Even if you specify ROS_WORKSPACE by hand it will be deleted after sourcing the setup.bash.
To make roscd work without arguments I can suggest you to set ROS_WORKSPACE explicitly in your .bashrc after the line that sources the relevant setup file.
EDIT: opened a ticket.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
