-
Notifications
You must be signed in to change notification settings - Fork 914
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
roslaunch tab: do not show files with a particular prefix or inside a particular subdirectory #254
Comments
+1 What do the core ROS devs think about this? |
There is no convention in ROS where to put files within a package. These are only recommendations. So requiring launch files to be in a certain subfolder will very likely break existing code. Establishing conventions might be a good idea but can likely only be put in place with a major version of ROS. The |
I agree that we should not impose a convention like putting everything to be included in a include folder. Regarding the renaming of specific launchers from For TurtleBot, we also have a significant amount of launchers, which are need to handle TB 1&2. To make it easier for users we plan to rename the launchers intended to be used only as includes to However, since the |
An alternative would be naming the files which should not be launch from the console with a suffix |
True, that would be a simple solution and superior to just |
I'd prefer .launch.xml to suppress the autocomplete. A trailing underscore On Thu, Aug 1, 2013 at 6:42 PM, Marcus Liebhardt
|
The proposed suffix |
I'm happy with this approach as well. |
Export architecture_independent flag in package.xml
Rename launch files as xml or something else is a good idea, but... would not be better to ignore, for example, all launch files inside "include" directories? Or all that start with "_"? Or whatever other convention. Like this we keep the semantics of the .launch extension.
The text was updated successfully, but these errors were encountered: