Pop!_OS (Linux)

5158 readers

1 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 1 year ago

MODERATORS

[email protected]

Rust with VS Code (flatpak) (lemmy.world)

submitted 1 year ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

How do people here have their set up? I was looking to set myself up, but get an error that says could not find a process named /path/to/project/projectname

I have found this link (thanks mmstick but it didn't run for me :( )

top 5 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

If you need to develop and link to system libraries with the Flatpak version of VS Code, you will need to install openssh-server on the system, and then using the Remote SSH extension. Then you can SSH from the sandbox to the host system. Alternative, you can develop software using any platform and without relying on system libraries with VS Code Dev Containers with Docker/Podman. Finally, it is possible to use nix-shell as a development environment as an alternative to Docker/Podman.

Personally, I use the Remote SSH extension so that I can use my laptop to develop code that's maintained and compiled by my desktop. That way my laptop can focus purely on rendering the UI and reducing energy consumption. Also justifies keeping the desktop on throughout the day. If not for developing things specifically for Pop, I'd use nix-shell for setting up development environments.

[–] [email protected] 1 points 1 year ago

Thank you for sharing a solution and your workflow. I will be trying it out :)

[–] [email protected] 3 points 1 year ago (1 children)

I've had bad luck installing vs code in a flatpak, the sandbox isn't great for code editors.

[–] [email protected] 1 points 1 year ago

At least I am in good company.

[–] beppi 2 points 1 year ago

Might just be because of the sandboxed nature of flatpaks, I had similar problems on emacs, before realizing I had installed it using flatpak...

For things like text editors, it's mostly better to use non-flatpaks, so they won't have issues accessing extensions or files or whatever, like you're seeing.

load more comments