.launch extension actually becoming a plain text file instead of a .launch file...
Hey guys, I am relatively new to ROS, as i am working with it for my research project. I have been learning fairly quickly on how to navigate through Ubuntu and how to use ROS. I have been working with different things including PID, ros_control, etc, and I have been following tutorials; some of them require me to make a .launch file, simply by making a blank file, and naming it with the .launch extension and copying and pasting the code. When doing all of this, the file does not actually become a .launch file for me, it becomes a plain text file... I did the same thing when creating a .xml file, adding that extension and it became a .xml file.
I'm not exactly sure what I am doing wrong. If anyone has a quick solution it would be much appreciated. Thanks!
Is it possible that you just wonder why your text-editor does not apply xml-highlighting if you open a launch file?
What do you mean by that? By the way, by xml I meant .yaml...When I try to launch the ".launch" files that I created that aren't actually launch files, it gives me an error obviously. Does anyone else know how I can create a legitimate .launch file?
I think what NEngelhard was trying to say is that in Ubuntu, and Linux in general, ASCII text file extensions don't really define the file. In this case, what is most likely happening is that your code editor doesn't know what a *.launch file is, and doesn't apply highlighting...
so it just "becomes a plain text file." If you actually run the launch file with
roslaunchthen it will work.