• 0 Posts
  • 407 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle


  • These days I might do that. The thing is, I’m coming from a situation where windows was installed, fully setup and configured with whatever I needed, so it was way easier to just run that than to redo everything and setup a VM.

    Also, the last piece of software I need is something used to bypass DRMs, and it kinda requires the whole thing to work flawlessly. I’ll see when I come around to launch it again if it’s viable.
















  • Yeah, I know of such “solution”. But what is the point of forcing the change when it doesn’t bring me tangible benefits, brings significant downsides, and only some of these downsides have half-useful workarounds?

    I have no problem with whether wayland existing or it becoming the new standard, but forcing people to move in these circumstances seems a bit silly, especially when some issues stem from people having hardware from one manufacturer that represents around 75% of general consumer systems (according to Steam survey, which might or might not be representative but sure brings a lot of people).

    Thankfully, at least with the distributions I use, switching back and forth is trivial. But given the circumstances, I don’t really understand the extremely heavy push.


  • What are you talking about? You can copy-paste from Terminal programs to GUI programs and vice-versa like everywhere else (with the terminal of course needing CTRL + SHIFT + C / V, which as we know is historical to Unix terminals). I’m doing that for years, so does my family. It works just fine.

    I’m not talking about copy/pasting from the terminal emulator, thank you very much. Just run VIM and have it copy/paste from the global clipboard without setting up esoteric, sometimes DE-dependent stuff, and you’ll understand.

    And bringing up Nvidia now really is bending down backwards to paint Wayland as bad while it’s painfully obvious it’s the driver’s fault.

    Sure. I did not say it was wayland fault. Or anyone else, really. I explained why some people could not “just move on to wayland already you nincompoop” with very tangible issues that still prevent them from doing so. Who is at fault is of no consequence here. If I switch to wayland, I lose features, I have a broken desktop, and throwing away thousands of equipment because “it’s the future” does not sound that great. It’s just a matter of fact. Whether it’s wayland’s fault, plasma’s implementation’s fault, nvidia’s fault, or anyone else’s is irrelevant to the user experience here.

    People can’t go “stop using X and use wayland”, and ignore raised issues by saying “no, that issue you’re having is not a big issue”, “that issue you’re having is not wayland’s fault”, “that issue you’re having does not concern most people”, etc. And reading replies in this thread, it seems people have a hard time imagining circumstances beyond their own.


  • That sounds more like escape sequence not being interpreted, but maybe? It’s a mess.

    Basically, in some implementations (it’s true for at least KDE Plasma), the console app is never seen as “active” (the terminal emulator is), and as such can’t access the clipboard, something like that. There’s third party program you can use, and plugins for things like VIM, but when you get a step further with remote clipboard it’s even worse. And even when solutions exists, there’s weird caveat like “it will work all the time except if you’ve clicked somewhere in the past few seconds” or something.

    I’m sure things will improve over time, but “we’re not there yet”.