I started on it instead of Obsidian

This is the way. I started on Obsidian, and Logseq is painful in comparison. It’s a good product, but I got accustomed to too many nice conveniences over the past couple of years.

In my country, we can buy pre-paid credit cards in the supermarket using cash. I guess that is still traceable using supermarket security cameras and facial recognition, but if you’re attempting this, I’d make it as difficult as possible.

The POSIX standard is more portable. If you are writing scripts for your system, you can use the full features in the main man pages. If you are writing code that you want to run on other Linux systems, maybe with reduced feature sets like a tiny embedded computer or alternates to gnu tools like alpine linux, or even other unixes like the BSDs, you will have a better time if you limit yourself to POSIX-compatible features and options – any POSIX-compatible Unix-like implementation should be able to run POSIX-compliant code.

This is also why many shell scripts will call #!/bin/sh instead of #!/bin/bash – sh is more likely to be available on tinier systems than bash.

If you are just writing scripts and commands for your own purposes, or you know they will only be used on full-feature distributions, it’s often simpler and more comfortable to use all of the advanced features available on your system.

Not gonna lie, Data breach sounds like a violation of one of Geordi’s crewmates.

I also looked at Excalidraw, which while being web app, runs reasonably well on Android. But some of the functions either don’t work at all or I’m doing something wrong. I was able to import a photo and trace it, but couldn’t find a way to export just the trace outline.

After you trace the photo, can’t you delete the photo from the canvas and just save as SVG? Won’t it save just the trace if that’s all there is?

Yes, driving trains is becoming more and more important as we find out how terrible cars are for the environment. We should protect the profession fiercely!

There are at least two ways to parse your statement, and they interpreted it differently from your intention.

In North America, the driver of a train engine is called an “engineer”, yes.

Honestly, nobody should call themselves an engineer unless they literally drive trains for a living.

I need to make it a priority to give logseq a try. I moved from Joplin to obsidian.md a couple years ago, because i realized an open data format (plaintext markdown files) was more important to me than an open source app (because I can still easily query and manipulate my data with open source CLI tools). I think at this point if I can replicate about 75% of my obsidian workflow in logseq, I’ll make the jump and adapt my workflows to logseq’s strengths and capabiities.

I’m a capable troubleshooter. I’ll take 5 minutes of troubleshooting once or twice a year to save a cumulative few hours opening an app store to manually check for and install updates. I’m glad they’re giving options to both of us!

To reference a movie in common vocabulary is to bring it up in conversation.

Referencing in programming terms like C refers to assigning a value to a variable. You can re-assign those variables to new values and then de-reference (read) the new value.

They are conflating the common meaning of reference with the much more obscure programming definition (obscure at least among non-programmers).

Star wars = “no, I am your father” (reference) Jaws = movie about hunting killer shark (reference) Star wars = movie about hunting killer shark (OP is pretending we can treat movie references like variable references and re-assigns the star wars variable to mean something else) “Hey, have you seen star wars? The movie about hunting a killer shark?” (De-referencing your newly re-assigned variable)

Yu-Ar-El? Is he Kryptonian?

deleted by creator

This is great! When I play GTA, the only thing I want is HOT COFFEE.

🤣

Yes, my comment only applies to the shell history in memory. -c clears history immediately, but you can still reload it from disk if you haven’t overwritten that with -w. If you tend to close your terminal windows frequently and rely on the history feature between sessions, it would benefit you to learn about the intricacies of the on-disk copy of history and how its affected by writes, appends, clears, crashes, etc. I tend to leave my terminal windows open a long time and copy any complex commands out to my PKM if I need to save them for future sessions, so I generally try not to rely on .bash_history, but it has saved my bacon on more than one occasion.

This feels racist against Appalachia. We naturally speak with contractions and are commonly referred to as “unbalanced”.

history displays a list of all commands you have run on the terminal since the history list was last cleared. It is invaluable for referring back to a big complex command or set of commands you ran at some point in the past. The -c flag clears that history.