![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
Did you read the article?
Did you read the article?
someone please correct me if I’m wrong but I believe that for it to be possible, the application that plays the mkv file would have to have a remote execution exploit and the code for the virus would be executed through the player. the player would be required to have elevated privileges. I think this is exceptionally unlikely for vlc
I have 1010 fingers
In my opinion, the settings file isn’t where this information should be presented. I would put these notes in the release log and readme and example settings file. I have also written this information to logging during startup so a user knows what to do, or I write a migration that does the change automatically if that’s possible.
This is only my opinion and you can use the comment method described like “//“: “Deprecated”
if desired.
For settings files I always have an example file with sensible values filled in and along with descriptive keys that serves as reasonable documentation. If something is truly unknowable, I’ve probably done something wrong.
Agreed. Except that it’s not easier to write imo
Every time I have reached for TOML I have ended up using JSON. The first reason is that Python standard library can read but not write TOML, which is generally useless for me. The second reason is TOML does not add any benefit over JSON. It’s not that much easier to read and IMO JSON is easier to write by hand because the syntax rules are completely obvious.
You close apps by double tapping the TV/control button then swipe up, similar to other iOS devices. It’s rarely necessary but super easy.
You turn the Apple TV off by tapping the TV/control button and selecting power off.
Typing sucks on all remotes but having an iPhone nearby allows you to use the phone’s keyboard.
Notable. Cross platform (no mobile app), sync with cloud drive of your choice, markdown support, easy interface.
Only if the code base is well tested.
Edit: always add tests when you change code that doesn’t have tests.
I don’t follow the 50 character rule, but to answer your first question: imo, no, don’t mention where you fixed the bug. This is a commit message that is explicitly tied to the place where you fixed the bug. You can go into more detail in the PR if you need to.
deleted by creator