Ah I see. Thank you for the precision. I might stick with KDE then.
Ah I see. Thank you for the precision. I might stick with KDE then.
What features would that be? Stuff for configuring controllers in the settings for example?
This isn’t really a big deal for me though.
Mine will probably be Bottles.
The team behind that application did a fantastic job. Wine was due for something much more user friendly like this. And integration with Proton, allowing 3D acceleration is the cherry on top.
When using KDE, press meta-T to activate the equivalent of Windows Power Toys’ Fancy Zones.
You can then set tiling zones and when you drag a window, hold shift at the same time to lock it in one of the zones.
I was going to say the same. This was my introduction to MST3K as well.
The movie’s theme song, the actors, the plot and the cast’s comments were the cherry on top.
IDEs have come a long way. But I’ve done qt development using Jetbrains Clion IDE and QTCreator. I don’t remember it being that difficult. Then again, I started programming using Turbo Pascal and Turbo C. So …
I dunno. Having worked with Java and c#, web dev, c++, I found working with QT in C++ to be so much easier.
That’s a good question. I have a few devices that are Linux compatible but require Windows to upgrade the firmware. I don’t know if I trust Wine or Bottles enough to run these applications to update a BIOS. Or if it’s even going to work?
I can always update device firmware through a Windows VM, but not my PC hardware.
Good point.
Auto destruct sequence activated.
I agree.
Unfortunately, from experience, nobody seems to have time for that. They just learn git pull, push, add, commit and merge and that’s about it.
Sometimes they’ll use checkout and end up in detached head and have a panic attack. That’s when I come in. lol
Technically, it went really well.
Yeah that’s what I did as a workaround. Reset (soft) to the first parent commit and do a single commit with all the changes.
What I do locally on my branch is my own business.
Honestly, when doing a merge/pull request into the parent branch, that’s when you squash. You don’t need the entire history of a development branch in main.
Yeah I saw someone else’s answer and I totally learned something new today.
Holy shit! I never took the time to read about it rerere. But it all makes sense now.
However, it’s still a lot of extra steps for what could otherwise be really simple with a regular merge.
Is there really a big advantage in using rebase vs merge other than trying to keep a single line of progress in the history? It’s it really worth all the hassle? Especially if you’re using a squash merge in a pull request…
All it can take is one commit in the parent branch. If your branch has many commits because you’re a commit freak then your fucked.
Especially if the topic is sex, as OP claims. Like WTF.