Linux

48145 readers

872 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Integrating VSCode and Distrobox (lemmy.world)

submitted 1 year ago by rainier@lemmy.world to c/linux@lemmy.ml

9 comments fedilink hide all child comments

Following up on a recent post on Distrobox...

For those using VSCode with Distrobox, how do you all do it? distrobox wiki suggests two approaches: flatpak + dev containers and running vscode from within distrobox.

Which do you prefer and why?

I've experimented with both and got both running with Wayland. Using the latter approach (vscode within distrobox), I couldn't quite get the running instances to be recognized by GNOME shell as the same vscode app that launched it. It shows up as code-url-handler, and doesn't share the same icon on the dash. The flatpak approach doesn't seem to have this issue.

you are viewing a single comment's thread
view the rest of the comments

[–] rainier@lemmy.world 2 points 1 year ago (1 children)

What do you mean by a "window rule"?

[–] Kekin@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

Here's some info on it: https://userbase.kde.org/KWin_Rules

From the overview:

KWin allows the end-user to define rules to alter an application's window attributes.

For example, when an application is started, it can be forced to always run on Virtual Desktop 2. Or a defect in an application can be worked-around to force the window above others.