Optional automatic `source install/setup.bash` in cwd when using ROS 2 CLI commands

I think there is a misunderstanding that I’m seeing here. I don’t need this for myself. I know how to make an alias for ros2 and how to use direnv. This question was originally brought up by someone else in the Discord, and it’s extremely common for people to source then run a ros2 command in a new terminal. So common that it should be an option that users can easily opt into if they don’t want to deal with this themselves. As I’ve mentioned in the Discord message chain on this, you could certainly offer the alias, but there might be quirks with autocompletion that might need to be dealt with at the lower level. While I don’t think this would be trivially easy, I don’t think it would be impossibly difficult to implement either. Most people that I have worked with have a simple workflow that would be much more convenient if they didn’t have to spam source for their overlays, and didn’t have to write a custom alias on every new system they use.

1 Like