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

roslaunch tab: do not show files with a particular prefix or inside a particular subdirectory #254

Closed
corot opened this issue Jul 19, 2013 · 8 comments

Comments

@corot
Copy link

corot commented Jul 19, 2013

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.

@bit-pirate
Copy link

+1

What do the core ROS devs think about this?

@dirk-thomas
Copy link
Member

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 .launch extension makes it pretty clear what these files are. Why should they be renamed into .xml in the first place?

@bit-pirate
Copy link

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 .launch to .xml, we copied that from PR2 folders, which hold a big amount of launchers. If someone uses roslaunch's tab completion on such a folder, he will see an overwhelming list of launchers. For beginners it's hard to figure out, which launchers can be used directly and which ones are used only as includes.

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 .xml in order to hide them from the tab completion.

However, since the .xml ending removes important meaning, i.e. it's a xml file for roslaunch, we would prefer to keep the .launch ending and instead add an underscore or similar.

@dirk-thomas
Copy link
Member

An alternative would be naming the files which should not be launch from the console with a suffix .launch.xml. That would hide it from the completion but still keep the semantic obvious.

@bit-pirate
Copy link

True, that would be a simple solution and superior to just .xml. However, an underscore suffix would be cleaner, no?

@tfoote
Copy link
Member

tfoote commented Aug 2, 2013

I'd prefer .launch.xml to suppress the autocomplete. A trailing underscore
is unpronouncable and would make differentiating files quickly in a file
list very hard as it's one small character different.

On Thu, Aug 1, 2013 at 6:42 PM, Marcus Liebhardt
[email protected]:

True, that would be a simple solution and superior to just .xml. However,
an underscore suffix would be cleaner, no?


Reply to this email directly or view it on GitHubhttps://github.com//issues/254#issuecomment-21981823
.

@dirk-thomas
Copy link
Member

The proposed suffix .launch.xml achieves the goal of not showing the files in completion of roslaunch while maintain the semantic meaning of being a launch file. Since this "solves" the request without changing any code we won't implement any special handling like underscore suffix etc.

@bit-pirate
Copy link

I'm happy with this approach as well.

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

4 participants