Ask Your Question

Revision history [back]

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.

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.