I used Zotero all through uni, but I’ve recently discovered JabRef. Zotero probably has more features and polish, but JabRef has one killer feature: Your plaintext BibLaTeX file is your reference database. So you can version control and collaborate on your reference file with git. No export required.

But how do you authenticate to your secret manager? How do you prevent evil scripts from also doing this?

My favourite game was always hacking around in Wine to make games work. Once I got them working I lost interest and moved on to the next game… Now I don’t have time to play games. :(

You can also type ZZ (uppercase, so hold Shift) to write and quit. But for all of the above you have to be in normal mode, so if it doesn’t work, try pressing Esc first.

Depends what you’re trying to learn, and how much of a beginner you are. If you want to learn the shell, try the Software Carpentry tutorials:

• The Unix Shell - Software Carpentry
• Version Control with Git

If you know the basics, you might try honing your skills with CLI Mystery (murder mystery puzzle).

You’ll probably want to learn how to use the following:

• SSH
• Command-line text editor. Choose one of the following:
  • Nano <- Smallest learning curve
  • Vim (or Neovim) <- My favourite (See Mastering the Vim Language)
  • Emacs <- Some people like it

The final tip is: It’s usually better in the long run to spend 2 hours reading the documentation than 2 minutes searching the web. Reading the documentation helps you to understand the big picture, and gives you a much better foundation. Of course, if you’re reading the documentation and don’t understand something, searching the web is an OK way to figure it out.

I mainly use Python, so my workflow is the same on every OS: Neovim and a shell, usually one of each in a vertical split. This transfers nicely to remote SSH sessions too, and even works in Termux on my phone!

Have you investigated whether it’s possible to test your cross-compiled builds in Qemu, rather than copying them to the host?

I think they said in the release article that they were going to roll 115 out slowly because it’s such a big change.

My 3 year old daughter has a 2010 MacBook running AntiX. She knows how to boot it, press Enter on the dual-boot screen, and is getting close to being able to select Stardew Valley from the app menu. She also enjoys playing GCompris.

I have a git repository in ~/dotfiles, and symbolic link the ones I want as I need them. I’ve only just started tracking my dotfiles and I’m not super disciplined with it yet, so I still have slightly different setups on each system.

The first step is to make sure your hardware is supported. I’ve found the linux hardware database to be invaluable getting new systems configured. The site is overwhelming at first, but the easy path is to just click the big ‘Probe your computer’ button and follow the instructions. Once you’ve done a probe, you’ll get a web-page with a listing of all your computer’s hardware and the support status. Even better, you get links to additional drivers or kernel modules required to get stuff working which isn’t supported out of the box.

I’d suggest maybe stick with Godot 3 until 4.1 comes out. I just started playing with 4, and hit a bug where Godot will hard crash whenever you try to view the Terrains tab if you’ve created terrain sets, used them in your scene, then deleted the terrain sets.

Also, Godot 4 doesn’t have as good support for older systems due to the new Vulkan backend. I worked around this by switching to the mobile renderer which works better on my old hardware.

Hanukkah of Data by the Visidata team was fun.

Can I suggest duckdb? You can start out writing SQL directly on top of CSV and Parquet files. But then if you want/need to do something more complicated, you can import duckdb into Python, keep running the SQL you already wrote, convert it to a Pandas or Polars dataframe, transform it, then query the result in SQL.