PerryPeak

@voracread I think ~/.config is the standard config file location on Linux (for apps that follow XDG standards) so it should also have config files for non-kde apps

@Secret300 @kde I think KDE neon has editions for testing KDE software

@Locutus @kde I think they said operating system because people coming from Windows might not know what a desktop environment is

@MJBrune @Ashiette I tried doing it as quickly as I can and it didn’t work the first time (result appeared what looks like about 0.1-0.2s later) but it did work in subsequent attempts (even when looking for other apps)
CPU: i5-1135G7

If you look for an app and then for a different app, does it find it quickly? I suspect it might be reading the .desktop files lazily (meaning it only reads them the first time you look for something)
Edit: nvm ksycoca is there to prevent that

@iturnedintoanewt I think it’s fixed in 5.27.7 https://bugs.kde.org/show_bug.cgi?id=466192

@Bro666 @croydon I think he meant that it should be added to the lemmy community’s description (on some fedi software it appears as a normal account, or one with a group or bot label). It would probably be best if lemmy or Mastodon added something that labels it as a community or explains what a “group” is, but the description could also say it, like how the KDE subreddit’s description starts with “Kreddit, the KDE Community on Reddit” (it’s for a different reason but it could work).

@InverseParallax @semperverus if I understood https://yuenhoe.com/blog/2012/08/associating-firefox-profiles-with-kde-activities/ correctly, it uses a protocol called XSMP which programs need to support, but for me it only ever changed things inside plasmashell so either not a lot of programs support XSMP or XSMP doesnt work on Wayland. I think it would be more useful if it integrated Flatpak and snap, and used them to mount a different config directory based on the activity an app was launched it but idk if that would work well

@odium @SirLotsaLocks based on the name and my knowledge about wayland, I think it allows fullscreen programs to directly render to the buffer that will be shown on the screen instead of having to first render to some other buffer and then have kwin copy it to the one that will be displayed on the screen.
Note that this is a 2 year old post about Plasma 5.21 so you probably already have a newer version of Plasma installed.

@UrbenLegend @carlschwan
If you look at KDE’s mastodon (https://floss.social/@kde) you will see that they boosted Carl’s toot announcing it (https://floss.social/@carlschwan/110595345431992114)