leopold

joined 11 months ago
[–] leopold@lemmy.kde.social 1 points 2 months ago

I see. Will avoid, then. I don't like lucid dreaming, always wake up right away. Whenever I notice I'm dreaming it becomes hard not to notice that I'm in my bed and that I can feel my covers and by that point it's all over, so whenever I notice I'm dreaming I just cut the crap and open my eyes for a couple of seconds to wake myself up and then close them again so I can get back to proper sleep.

[–] leopold@lemmy.kde.social 4 points 2 months ago* (last edited 2 months ago) (2 children)

Is this really useful? Like, is this something people ever need to do? I don't do lucid dreams very often, but the rare times a dream has lead me to the thought of "hold on, am I dreaming?" were basically immediately answered by just, uh, vibes, I guess? Like, it's always just been instantly obvious that I'm dreaming the moment I'd start questioning it, no tests necessary. At worst I might have to try to remember what I did the day before and what I was supposed to be doing that day and see if that is at all compatible with the scenario I'm dreaming about, which it usually isn't.

[–] leopold@lemmy.kde.social 6 points 2 months ago (2 children)

Why do you believe a "nutrition brick" would be at all more appetizing than the things described in OP?

[–] leopold@lemmy.kde.social 4 points 2 months ago (1 children)

Esperanto has grammatical gender.

[–] leopold@lemmy.kde.social 19 points 2 months ago* (last edited 2 months ago) (5 children)

Do you... not know how multi-licensing works? You can use the project's code under the terms of whichever license you prefer, you don't use all three at once. Simply putting the AGPLv3 does remove unfair restrictions, because it means you don't have to use either of the proprietary licenses the project was previously only available under.

[–] leopold@lemmy.kde.social 12 points 2 months ago (10 children)

I don't follow. ElasticSearch was only available under proprietary source-available licenses. Now, it's also available under the AGPL, which is open source, meaning ElasticSearch is now open source software. What part of this is deceptive or contradictory?

[–] leopold@lemmy.kde.social 2 points 2 months ago (1 children)

Uh, Cinnamon does not need a compatibility app to run Qt apps. No desktop environment does. You mostly just need to be X11 or Wayland compliant. The same is true with GTK.

[–] leopold@lemmy.kde.social 12 points 2 months ago* (last edited 2 months ago) (1 children)

MV3 doesn't make adblockers impossible, only less effective. It's important to note that MV3 has changed a fair bit since the initial controversy and isn't quite as limiting as it used to be. The fact that adblockers will lose some functionality at all is still a dealbreaker for me and many others which I thankfully won't have to deal with as a Firefox user, but it isn't going to kill adblockers on Chrome and most users will probably just install an MV3-compatible adblocker and move on with their day.

uBlock Origin's developers don't seem to want to make a proper MV3 port, which is fair because they'd probably have to rewrite most of the extension, but they did create the far more minimal uBlock Orgin Lite, which a lot of people have taken to be an attempt at porting uBlock Origin to MV3. It isn't that. On top of MV3's limitations, it also makes the decision to work within these self-imposed restrictions:

  • No broad host permissions at install time -- extended permissions are granted explicitly by the user on a per-site basis.

  • Entirely declarative for reliability and CPU/memory efficiency.

These aren't MV3 limitations, just a thing Gorhill decided to do. See the FAQ. You can get much closer to uBlock Origin within MV3's constraints than uBlock Origin Lite does. Right now, the best option appears to be AdGuard, which has been making a true best-effort attempt at porting their adblocker to MV3 pretty much since the announcement.

[–] leopold@lemmy.kde.social 5 points 2 months ago

Calligra's support for OOXML files is truly garbage and shouldn't be used. Only use it with OpenDocument files.

[–] leopold@lemmy.kde.social 3 points 2 months ago

Whoa, I was convinced Karbon wasn't going to see any further Calligra releases. Seemed to have zero maintainers last I checked, thought it'd go the way of Braindump and Author.

[–] leopold@lemmy.kde.social 12 points 2 months ago* (last edited 2 months ago)

Huh? That's the best thing about Calligra by far. Why waste valuable vertical real estate on toolbars and ribbons when you can shove a sidebar in all of that empty wasted margin space? Plus, the whole thing is customizable. It doesn't have to be a sidebar if you don't like sidebars.

[–] leopold@lemmy.kde.social 10 points 2 months ago* (last edited 2 months ago) (1 children)

itch.io also has a Linux app

10
More Icon Updates (anditosan.wordpress.com)
61
Breeze Icons Update! (anditosan.wordpress.com)
 

I have to use macOS (10.14 IIRC) at school and I'm using Kate as my primary text editor. I'm using the latest release binary here.

Out of the box, three major features don't work. The debugger, the terminal and lsp. After messing around a little, I was able to get lsp working by installing llvm through homebrew for clangd and pointing the lsp config file to the proper location, because my homebrew prefix is the non-default ~/.brew/ due to a lack of admin privileges.

Terminal just crashes Kate the moment you try to open it and the macOS port of Konsole is extremely broken, so I'm not holding out much hope for that (and either way I'm happy with iTerm2), but I feel like there should be a way to get the debugger working. Basically the problem is that the debugger is built for gdb, but macOS ships with lldb. I tried installing gdb through homebrew, but couldn't figure out how to point the debugger to my homebrew prefix. Also looked like there was a way to add additional debuggers and I tried to add lldb that way, but couldn't figure it out either.

If someone has gotten this working, I'd love some help

Update: Made some progress. Found out how to get the debugger to use homebrew gdb. In advanced config, I just changed the command from gdb to ~/.brew/bin/gdb. It's still broken, tho. Won't let me select an executable to debug. I also have a clue on how one might get lldb working. Kate uses a dap standard similar to lsp for working with debuggers. lldb has a dap server called lldb-vscode, which is a part of llvm, which I already have installed. No clue how to work with the dap.json configuration to add it as an available debugger, tho. That's where I'm stuck, right now.

Update2: Got gdb working. Just had to use a full path, meaning /Users/lcouturi/.brew/bin/gdb instead of ~/.brew/bin/gdb

 

FreeBSD has supported Plasma for a long time, but on OpenBSD, it's been a long time coming. I believe a KDE desktop hasn't been available on OpenBSD since Plasma 4, perhaps even KDE 3.

view more: ‹ prev next ›