Decency or even legality. If Zuck knowingly hosts hate speech, you don’t want that federated onto your platform or you can be sued, too.
Decency or even legality. If Zuck knowingly hosts hate speech, you don’t want that federated onto your platform or you can be sued, too.
Oh, so LibreOffice is actually a fork of OpenOffice, meaning back in 2010, the devs copied the code from OpenOffice and have been developing it further from there. So, it’s like your parents just got upgraded to the newest edition of the office suite they were using. A lot of it should still be familiar to them.
Basically, the devs had to change the name for legal/political reasons. In all other ways, LibreOffice is the continuation of OpenOffice.
OpenOffice
Most Linux distros come with LibreOffice pre-installed. That’s what you want. OpenOffice pretty much stopped being developed in 2010 and the developers moved over to LibreOffice.
Oh, when you’re coding something in a Git repo and you realize that you need to make a different change before you continue coding (e.g. switch to a branch, pull newest changes, or just create a separate smaller commit for part of your change), then you can run git stash push
to put away your current changes, then make your other change, and then run git stash pop
to bring your ongoing changes back. I recommend reading git stash --help
, if you want to use it.
Sometimes, though, you might end up just taking it into a different direction altogether or simply forget that you had something stashed. That’s when that indicator comes in handy. Because while you can have multiple things stashed, I do find it’s best not to keep them around for too long. If you do want to keep them for longer, then you can always create a branch and commit it as WIP onto there, so that you can push it onto a remote repo.
Yep, here’s my Starship prompt, for example:
So, I have it configured to show:
means I have something stashed,I’ve been enjoying Fira Sans and Fira Mono for far too long: https://mozilla.github.io/Fira/
I’ve got basically the bspwm workflow, but on KDE.
So, bspwm has tiling of windows and doesn’t want you to minimize (nowadays, it actually has a minimize-feature, but back when I last used it, it didn’t). As a result, if a window is open, it is visible on some workspace. If you want to hide windows, put them on a different workspace.
I like that workflow, because while it probably seems complex when you first hear about it, it actually simplifies things. When you’re looking for a window, you don’t have to check all the workspaces and minimized windows and behind other windows.
KDE adds to that, in that I can have a workspace overview in my panel, so where I can see all workspaces with the windows that are visible on them (which with this workflow is all windows on that workspace). I like to call it my minimap.
It makes the workflow a lot easier to use, but it also allows me to group workspaces by location. So, if I’m working on a topic, I often have a Firefox window on one workspace, my text editor on the workspace below and then a terminal on the workspace below that. If I then realize, I need to quickly look up something for a related topic, I’ll open up a new Firefox window two workspaces below that (leaving an empty workspace as separator). If I do something completely different, I might leave a whole bunch of empty workspaces in between. Or, well, KDE actually allows grouping workspaces with a feature called “Activities”, so I’ll often switch Activities.
I find that works a lot better for multi-tasking than the traditional Windows workflow of one window per application, with all kinds of different topics mixed into all kinds of ungrouped windows. If I switch between topics, I just go to the right location on my minimap and I’ve all the topic-related information in the windows that are there.