Or have a single general footer that they all refer to.
Error message? McAfee can’t write to the drive because it’s full of photos of their grandchildren and dogs, so it clicks up “can’t write to c:\temp\sqlite_arcane_computer_magic.log: Disk is full”, and it goes from there?
deleted by creator
Assuming that they went out to look for it, and didn’t just poke google with (“sqlite hacked my computer”) until they found a phone number.
If they had gotten the phone number for a company called Super Queasy Lite and Easy/SQLitE instead of the developers, the company might well have received the calls instead.
I don’t think that’s how you’re meant to use a WHERE
.
It even has questionably-helpful mysterious blinky lights at the bottom right which may or may not do anything useful.
The box what goes bang if you poke it wrong.
The computer is inaccessible, and if you did that, the best way to fix it, while also avoiding any other potential issues stemming from that, is just to reinstall the thing.
It seems like it would be fairly easy to find. All you need to do is find out where the price drops massively, and work backwards from there, since it doesn’t change the code going forward.
Wayland really doesn’t like RDP/remote access, so X is the only way to go if you want that to work properly.
You can if you want, but Lemmy doesn’t translate them, like Mastodon does, and you might find them conflicting with the header Markup.
That, and Lemmy users used to a more Reddit-like structure of posting might get rather annoyed by it, since it would clog up the feed with unhelpful information.
The mistake is clicking it, and not speaking to it. Try “hello computer”.
If the embedded system is old or poorly-maintained enough, there might be more Rust than you’d think.
Unless FPS means “files per second”, I don’t see why it would, past the point of usability. You can only type so quickly, and 50 frames is as meaningful as 144.
If you get to that point where frames per second does matter, you’re either the fastest typist known to mankind, or it might be worth finding a more efficient way of doing what you’re doing.
Unclear. They don’t give their reasoning beyond “complicated = bad”, and very specifically leave it up to the imagination of the reader.
While they make some interesting points with regards to overcomplication and scope creep, there are also good reasons why we’re still not using programs like ed
as text editors, such as it being arcane and unintuitive.
vi
will at least helpfully point out :exit is not an editor command
. Instead, ed
will not-so-helpfully point out ?
.
When you think of a bloated text editor, you would not expect VI to be that. If anything, it’s closer to the opposite.
You can easily log and archive things that happen on an open protocol, not so much a proprietary one like discord.
That’s the part where you give up and randomly shove/unshove symbols in until the code works.
Or if you find the project a while later, and the link/server is dead, either because the maintainer forgot to update the link, or the server shut down/removed invites for some reason, like spam prevention.
Or it turns out you accidentally left caps lock on, and now you’re locked out for a few minutes.