ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Ok I'm not sur I got your problem:

Regarding rosed usage:
The main advantage of using rosed is that it uses the ROS package architecture. So you won't need to be inside any folder, you just need the environment variable $ROS_PACKAGE_PATH set. You set it by sourcing your workspace ("source ~/my_workspace/devel/setup.bash") and you shoud be able to use rosbash commands (roscd, rosls, rosed...).

rosed is working as follow : rosed PACKAGE_NAME FILENAME.
so if your run "rosed beginner_tutorial CMakeLists.txt" it will work
"rosed CMakeLists.txt" won't because CMakeLists.txt is a file, not a package.

If you are in the right folder you can just use "nano FILENAME", or "vim FILENAME" or any editor you use. rosed won't be of any value if you are already in the right package.

If your packages are not recognized:
source your workspace : "source ~/catkin_ws/devel/setup.bash"
update your package list : "rospack profile"
then you should be able to use rosbash commands : try "roscd beginner_tutorial"

If roscd works but rosmsg show doesn't work:
This means that your messages have not been generated. You need to build your package to generate the messages. To build your workspace you need to go in your workspace "cd ~/catkin_ws" and run "catking_make", you will see blue lines saying that your messages have been generated. Now rosmsg show should work

Hope this helps,