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.
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.
Aw dang. That sucks. But I understand.
Are you sure about that? I dunno if that’s correct.
This is the correct response.
At my job we’ve been asked to remove Docker desktop unless it is absolutely necessary for a client project.
I’ve just been using Docker through command line via WSL and that’s good enough for me.
Right???
Fucking hell.
The french are throwing a hissy fit over that issue. The younger working class has to sacrifice their retirement because “the economy”. Meanwhile you got rich assholes parading on their huge yachts in St-Tropez and the French Riviera thanks to the money they make from dodging taxes.
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.
I love my 2010 Mazda 3. It’s basically the same platform as the Ford focus from the same year. If they were able to eventually make a Focus EV, then I’d bet it’s possible to do the same with my Mazda.
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
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.
Most of the time it’s too received push notifications.
I consider myself above average in terms of Git know how. But I’ve come across situations using rebase where you’re stuck resolving the same conflicts over several commits.
I still don’t understand that part quite well.
This doesn’t happen when you do a normal merge though. Making it easier to manage
Nah. We sent armored trucks to Israel instead.