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

[bug] ros.createCatkinPackage requires a ROS workspace to be opened #1290

Open
hitbuyi opened this issue Apr 27, 2024 · 0 comments
Open

[bug] ros.createCatkinPackage requires a ROS workspace to be opened #1290

hitbuyi opened this issue Apr 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@hitbuyi
Copy link

hitbuyi commented Apr 27, 2024

Linux: (Dist/Version) ubuntu20.04
ROS 1: Dist noetic

what is the bug

ros.createCatkinPackage requires a ROS workspace to be opened
Screenshot from 2024-04-27 18-16-07

Repro steps

  1. install vscode
    Version: 1.88.0
    Commit: 5c3e652f63e798a5ac2f31ffd0d863669328dc4c
    Date: 2024-04-03T13:25:57.039Z
    Electron: 28.2.8
    ElectronBuildId: 27744544
    Chromium: 120.0.6099.291
    Node.js: 18.18.2
    V8: 12.0.267.19-electron.0
    OS: Linux x64 5.15.0-106-generic
  2. mkdir p /src
  3. ctrl+shif+p,-> catkin_make,->ROS Create Catkin Package

expected behavior

This is caused by path problem, when code . and the hidden file catkin_workspace should be in the same directory, and I expect vscode can recogize directory which is clicked by mouse in vscode window, that is more friendly to a newbie
First up, when I got the information "ros.createCatkinPackage requires a ROS workspace to be opened", I did assumingly two things : 1) open a terminal, run roscore 2) open the project folder. This misguide most beginners, ROS workspace to be opened actually menas the hidden file catkin_workspace should be in the same folder, not meaning "opened" it. I think change the error hint,or optimize the creating package method will be a good way to deal with this issue.

@hitbuyi hitbuyi added the bug Something isn't working label Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant