[-] [email protected] 5 points 20 hours ago

I set up mine same as I did on desktop. Copied my custom filters over and enabled all of the default ones. Works well enough.

[-] [email protected] 5 points 4 days ago

Because it's not actually a good idea.

You create text that is basically impossible to search. Like, for instance, do a Ctrl+F on this page and search for "Bold". You'll see the example from OP doesn't get picked up, because it's not a B, it's a 𝗕. And it's not an o, it's an 𝗼. And so on. Or how about this? Go on Google and copy-paste this word from OP: "s̵t̵r̵o̵k̵e̵". Now, stroke isn't a particularly unusual word, but this thread is just about the only result Google returns. Because it's not stroke. It's s̵t̵r̵o̵k̵e̵.

It's also bad for accessibility. A lot of the time screen readers just won't know what to do with your bold or italic Unicode text.

And of course this only works for characters for which Unicode actually has these variants. Not a problem with the Latin alphabet, but what about Arabic? Cyrillic? Chinese? Devanagari? Hangul? Not gonna work.

These characters are from the Mathematical Alphanumeric Symbols code block. They're stylized Greek and Latin letters meant chiefly for use in mathematical contexts. The Unicode standard explicitly advises against using them to fake markup for the reasons outlined above and more. A simple markup language is just about always going to be preferable to faking it with Unicode.

[-] [email protected] 20 points 5 days ago

Source? Last I checked, the Steam Deck was very much in the minority even when narrowed down to just desktop Linux.

[-] [email protected] 41 points 2 weeks ago* (last edited 2 weeks ago)

It is significantly less powerful when compared to LibreOffice, lacking support for many features. It offers less applications than LibreOffice. It is significantly less customizable than LibreOffice. It's built on bloated web tech. It lacks RTL support.

I am not paranoid about OnlyOffice's origin. I also do not think it is the best office suite on Linux by a mile.

29
Release of KDE Stopmotion 0.8.7 (gruenich.blogspot.com)
submitted 3 weeks ago by [email protected] to c/[email protected]
[-] [email protected] 33 points 1 month ago* (last edited 1 month ago)

It's not an unpopular opinion that Apple is the only one that does sleep right. It is an unpopular opinion that this is only possible because they have a complete walled garden and that open platforms are fucked, especially considering it is easy and common to install applications from outside the App Store on macOS. We used to have sleep figured out, that's what S3 was. But then hardware vendors dropped it. So yes, drivers and hardware vendors are part of the problem. The Steam Deck is an example of an open platform where sleep works fine.

13
submitted 1 month ago by [email protected] to c/[email protected]
[-] [email protected] 38 points 1 month ago* (last edited 1 month ago)

Sure.

Wine 9.9 bug fixes:

#56000 Window title is not set with winewayland

Wine 9.8 minor changes:

winewayland.drv: Enable wglDescribePixelFormat through p_get_pixel_formats.
winewayland.drv: Set wayland app-id from the process name.
winewayland.drv: Implement SetWindowText.
winewayland: Get rid of the now unnecessary surface wrapper.

Wine 9.7 minor changes:

winewayland: Remove now unnecessary swapchain extents checks.
winewayland: Remove now unnecessary swapchain wrapper.

Wine 9.5 minor changes:

configure: Check the correct variable for the Wayland EGL library.
winewayland.drv: Implement wglCreateContextAttribsARB.
winewayland.drv: Implement wglShareLists.
winewayland.drv: Implement wgl(Get)SwapIntervalEXT.

Wine 9.4 major changes:

Initial OpenGL support in the Wayland driver.

Wine 9.4 minor changes:

winewayland.drv: Add skeleton OpenGL driver.
winewayland.drv: Initialize core GL functions.
winewayland.drv: Implement wglGetExtensionsString{ARB,EXT}.
winewayland.drv: Implement wglGetProcAddress.
winewayland.drv: Implement wglDescribePixelFormat.
winewayland.drv: Implement wglSetPixelFormat(WINE).
winewayland.drv: Implement OpenGL context creation.
winewayland.drv: Implement wglMakeCurrent and wglMakeContextCurrentARB.
winewayland.drv: Implement wglSwapBuffers.
winewayland.drv: Handle resizing of OpenGL content.
winewayland: Remove now unnecessary vulkan function name mapping.
winewayland: Remove unnecessary vkDestroySurfaceKHR NULL checks.

New minor versions of Wine are released every two weeks. Last major Wayland update was in 9.4. Smaller updates have happened every release since, except 9.6.

[-] [email protected] 29 points 1 month ago* (last edited 1 month ago)

is this flamebait? we really don't need this stale-ass debate revived for the millionth time. everything that had to be said has been said and no one is going to budge from their positions. there is nothing to be gained from reposting some old controversial 2021 blog post about this outside of more flaming. it's time to move on. this is a waste of everyone's time.

if you're a developer, support themes if you want to support them, don't support them if you don't. if you're a user, use the apps you want to use. if you care about theming, use the apps that support it. if you don't, good for you. there doesn't need to be anything more to it.

[-] [email protected] 40 points 2 months ago* (last edited 2 months ago)

nearly your entire system is written in C and you're worried about a simple fetch program

26
submitted 2 months ago by [email protected] to c/[email protected]
38
submitted 2 months ago by [email protected] to c/[email protected]
102
submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

Amarok was KDE's flagship music player during the KDE3 and Plasma 4 days. For Plasma 5, a new music player called Elisa was created with Kirigami which is the current KDE flagship music player. The last full release of Amarok was 2.9.0 in 2018, still targeting Qt4. A Plasma 5 port was started with the intention of being released as Amarok 3.0, but despite a usable alpha 2.9.71 release in 2021, the full 3.0 release was never completed. Outside of the occasional odd pull request, the project was essentially dead and was listed as unmaintained by apps.kde.org.

Two weeks ago, occasional contributor Tuomas Nurmi, author of over a third of these pull requests, made a push to become an Amarok maintainer, starting this thread in the mailing list: https://mail.kde.org/pipermail/amarok-devel/2024-March/014748.html

In the thread, Tuomas expresses his desire to revive Amarok. He believes a second alpha for 3.0 can be released in mid-April and a full Plasma 6 port could be completed within 2024 after the release of 3.0. Tuomas has since created a fair amount of merges and fixes in preparation for 3.0 and has shown no sign of stopping.

This is very exciting news. For many, Elisa isn't a satisfying replacement for Amarok. It simply doesn't come close to matching Amarok's power and features. It also has the drawback of being a convergent application, meaning compromises have to be made to make the interface work well on smartphones.

It's also victim to the many drawbacks of Kirigami. Theming is worse since Plasma has to convert QtWidget themes to QtQuick themes, which works great for Breeze, but meh for everything else. There is no good equivalent for KStandardAction/QAction, KHamburgerMenu or KStandardShortcut. Any Kirigami app that wants customizable toolbars and shortcuts need to go out of their way to implement them, while QtWidgets apps just get them for free. You also don't have a good QDockWidget equivalent that I know of. Apps that do bother to reimplement some of these features (Haruna is the only one I know of) still don't have toolbar customization to nearly the same extent QtWidgets apps do. Most Kirigami apps don't bother with this at all and lose a lot of customizability in the process. Elisa is not Haruna, tho. There is no shortcut customization, there is no toolbar to customize and that hamburger menu can't be turned into a menubar.

For years, the solution was Strawberry, a fork of Amarok still under active development. Thing is, Strawberry is a fork of Clementine, itself a fork of Amarok 1.4. That's old. That's 2008 Amarok, not 2018 Amarok. Clementine had its first release in 2010, when Amarok was still going strong. It was for good reason, Amarok 2.0 introduced a very divisive redesign of the interface, which prompted a fork. But this means 2.0+ Amarok and Strawberry are actually very different beasts. For those who were using Amarok 2.9, switching to Strawberry meant switching to a new music player, making it far from an ideal successor. So I'm very much excited for the return of Amarok, the best music player KDE has had.

25
Haruna 1.0.2 (haruna.kde.org)
submitted 3 months ago by [email protected] to c/[email protected]
13
Kile 2.9.95 / 3.0 beta 4 released (gruenich.blogspot.com)
submitted 3 months ago by [email protected] to c/[email protected]
27
Breeze Icon Update March 16, 2024 (anditosan.wordpress.com)
submitted 3 months ago by [email protected] to c/[email protected]
85
submitted 4 months ago by [email protected] to c/[email protected]
35
Icon Updates for March, 2024 (anditosan.wordpress.com)
submitted 4 months ago by [email protected] to c/[email protected]
17
submitted 4 months ago by [email protected] to c/[email protected]
25
submitted 4 months ago by [email protected] to c/[email protected]
[-] [email protected] 27 points 5 months ago* (last edited 5 months ago)

So just to clarify, there's no way to support the DualShock 3 without introducing a security hole? Or is the security hole only a problem with the current driver which could eventually be fixed, rather than something inherent to the device? Also, is there a list of affected devices outside the DualShock 3? Will the Wiimote still work, for instance?

The DualShock is old, but I've always appreciated how I could have all of my gamepads just work on Linux, from the Wiimote to the DualSense. On Windows, most of them needed third party unofficial drivers to be installed and/or would be missing functionality, like motion controls or Bluetooth support. Would be a big shame if it just stopped working wirelessly. Still, I have a lot of significantly better gamepads by now, including a DualSense, so DualShock 3 support isn't something I really need anymore unless I have a lot of people over and need to connect a lot of controllers.

[-] [email protected] 24 points 5 months ago

It never occurred to me before reading this comment that there actually is a use case for the execute permission. To me it was always just this annoying thing I have to do whenever I download an executable which I didn't have to do on Windows.

[-] [email protected] 48 points 5 months ago

Can people who very clearly haven't read the article stop commenting the equivalent of "works on my machine", please? I know it's a long article, but it's worth a read. It's not anti-Wayland and it's definitely not pro-X11. It just outlines a few limitations of Wayland and problems with how Wayland is currently being developed. It's a great follow up to Nate's blog post, which was posted here a while back and got pretty popular.

[-] [email protected] 36 points 6 months ago

Oh boy, 102 comments. Knowing Phoronix, I bet those are a treat to read.

view more: next ›

leopold

joined 7 months ago