Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roscd behaviour without input is different between rosbash and roszsh #72

Closed
javanegmond opened this issue Dec 9, 2014 · 4 comments
Closed
Milestone

Comments

@javanegmond
Copy link

Hi,

The rosbash version of roscd checks CMAKE_PREFIX_PATH, while the roszsh version does not. As a result, after source'ing (setup.[bash|zsh], depending on the shell I use) the bash behaviour of roscd without parameters goes to /path/to/workspace/devel, while the zsh behavior is the following error:
No ROS_WORKSPACE set. Please set ROS_WORKSPACE to use roscd with no arguments.

Is there a specific reason for this difference in behaviour?

@dirk-thomas
Copy link
Member

It is likely not intentional but has either been broken during recent updates to the zsh stuff or different people implementing the different shells weren't aware of it. Please feel free to provide a match to the zsh scripts to make it behave like bash.

@javanegmond
Copy link
Author

Alright, I believe my pull request fixes it. I checked and it also applies to hydro-devel. Should I make the changes for that and do another pull request?

I haven't checked rostcsh, it could be that changes in rosbash aren't reflected in there either.

@dirk-thomas
Copy link
Member

You don't have to create a separate PR for other distros. After it has been merged (and a potential soak time) it will be considered for being backported.

ROS workspace don't even have a setup.tcsh entry point anymore. I don't think it is used anymore anywhere.

dirk-thomas added a commit that referenced this issue Dec 29, 2014
@dirk-thomas
Copy link
Member

This has been cherry-picked to the hydro-devel branch and released as 1.10.11.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants