While I do like fish syntax, you don't really need to learn it. You can just use it for your interactive use in the terminal while writing your scripts in bash.

Stay with one of the big boys: Debian, Ubuntu, Fedora, openSUSE, then you're golden. For NVIDIA users I guess I'd still recommend something Ubuntu based: Ubuntu, Kubuntu, Pop_OS!, etc because the drivers can be preinstalled.

On Fedora you need to install the NVIDIA drivers from rpmfusion, and on openSUSE you need an additional repo. It's an extra step, but otherwise I'd strongly recommend one of these two.

The hands in the fourth pane...

In that section, if you click the button to configure the Mouse Mark effect, you can see the shortcuts for clearing Mouse Mark:

• Clear last mouse mark: Super + Shift + F12
• Clear all mouse marks: Super + Shift + F11

We need more OSes that support cheap phones available in third world countries instead of mid-range phones in first world countries.

Took me an embarrasing amount of time to realize it's a Scrooge McDuck comic and that's Donald at the top right :D

This German expression idiomatically translates to "I'll be damned!", "Blow me down!" or "Shiver me timbers!", but the literal translation would be something like "Mice bite me!".

It's interestingly similar to an equivalent in Portuguese where we say "Macacos me mordam!", "Monkeys bite me!", which is how we traditionally translate this. I wonder if the expression exists in both languages or maybe the German comic was translated using the Portuguese version as base?

If, instead, you won’t do it and prefer to keep Bugzilla as the main issue tracking platform, could you tell us why?

Here are the reasons why: https://community.kde.org/Get_Involved/Issue_Reporting/Why_not_GitLab_Issues

The tldr is that Gitlab Issues is limited for users, developers and triagers compared to current Bugzilla, given the current KDE infrastructure. These are just technical issues. The moment Gitlab solves those limitations, KDE would gladly use it.

[...] since they’re right there by the code base.

Note the section "Bugs need to be filed against individual repos". At it stands right now, if a non-technical user finds a plasmashell bug, they can just go to "File a bug":

and they're greeted with this:

And then they can choose Plasma and then plasmashell, both with very descriptive text mentioning what should be reported there. It's not too bad to find the right place to report things, to be honest. And there's an "I don't know" field, which is great. :)

Finding issues can be a bit finnicky, yeah. But you can click on the search field in the first page, type what you want to find, click on Quick Search and you get a list of results based on your keywords, and you can also click on the Search button and then click on Simple Search to look for some keyword in a specific product. Once you know it's pretty simple.

That is a decent way of finding out whether the person is a native English speaker, actually.

This rarely happens to non-native speakers.

I can't tell you why this is happening, but what is clearly happening is that your apps are being run under a nested kwin_wayland instance. It's as though you were running kwin_wayland krunner.

If anyone’s wondering, my main issue with Wayland was that it wasn’t setting the DISPLAY and WAYLAND_DISPLAY environment variables for some reason, and this would cause all kinds of software like Steam and Firefox to not even launch. I tried setting them manually but that didn’t go do well either.

My guess is that whatever fix you attempted here caused this, so you'd need to be more specific about what you tried.

My understanding of Linux programming is that it’s mostly done in a code editor, then compiled on the command line.

That's not really true. You can do that, but with most IDEs (and some text editors) you really don't need to do that. You can do everything from the IDE.

I’m aware that cmake exists, and I’ve used it a bit, but I don’t like it. VS lets me just drop a .h and .cpp file into the solution explorer and I’m good-to-go. Is there really no graphical alternative for Linux?

It depends on the IDE and how it handles project files. Nowadays Qt Creator for example can just create your source code files and automatically add them to the generated project CMake. I'm pretty sure other IDEs or text editors have this functionality when paired with CMake or Meson too.

It must be noted that if the IDE has some custom project file manager (like Visual Studio does with sln and vcproj files) and you use it exclusively, you'll likely restrict your project to one platform and one IDE. Using something like CMake or Meson will make it easier to do crossplatform development and will let your users build the project without needing that specific IDE.

Personally I like modern CMake, the problem is that you'll see a lot of projects in the wild doing old CMake style, which is awful. Meson is okay, although it feels very Pythonic to me and lacks some features I use for Qt stuff.

Everything. It doesn't accurately describe the issue (animation stutter when using an HDD or during heavy I/O) and it doesn't mention the solution (put the cache folder in tmpfs), plus it obviously follows the traditional sensationalist tone used in clickbait.

The point is to be deliberately vague to bait people into watching it.

Welcome Linux furson :P

Arch is fine, it doesn't take as much to maintain it as it seems. Just be sure to read the System Maintenance (especially "Upgrading your system") and General Recommendations pages.

To be clear, Arch is also one of the big boys, just not my personal recommendation for beginners.

I'd do that without a sigh :p

I was thinking, with the recent news of a contributor to GitLab adding support for forge federation, some time we could see that being enabled in the KDE instance as well, I hope.

It would be cool indeed. It would mean that people on KDE Invent could make issues and MRs directly to the Freedesktop Gitlab, for example, if both were federated.

FYI for whoever is reading this: it wasn't just a theme, but a Global Theme: it can include a Plasma Style, a color scheme, an icon theme, a panel layout template, an SDDM theme, wallpapers and widgets. Widgets are capable of running arbitrary code, just like GNOME extensions.

Here's the response article from one of our main developers: http://blog.davidedmundson.co.uk/blog/kde-store-content/

In the short term we need to communicate clearly what security expectations Plasma users should have for extensions they download into their desktops.

We need to improve the balance of accessing third party content that allows creators to share and have users to get this content easily, with enough speed-bumps and checks that everyone knows what risks are involved.

Longer term we need to progress on two avenues. We need to make sure we separate the "safe" content, where it is just metadata and content, from the "unsafe" content with scriptable content.

Then we can look at providing curation and auditing as part of the store process in combination with slowly improving sandbox support.

Looks like an old bug with kscreen that could cause two screens to merge together and would be worked around exactly the same way you did. I used to have that whenever a blackout happened, but only with Plasma 5, and often on X11.

I love the interesting use of IPA to have the characteristic sentence stand out.

Correct. The requirements are:

• put a link to the community anywhere in a Mastodon toot and a post is automatically generated on Lemmy
• the first line becomes the title/headline
• additionally, a recent change in Lemmy removed Markdown formatting from headlines, so instances that are sufficiently up-to-date will have links and hashtags show up as literal text instead of links: https://pawb.social/comment/1624631

Goals