alias nano='nano -A -D -E -F -T 4 -Z -g -i -l -m -q -t -% -_'
and you need to enable syntax highlighting in nanorc (not all distros enable it by default)
include /usr/share/nano/*.nanorc
also there are additional/improved rules for highlighting here https://github.com/galenguyer/nano-syntax-highlighting and you can rebind every key, but it seems that it doesn't support 'chaining' of keys nor multiple modifier keys at the same time.
Both nano and emacs suffer from the same problem - bad defaults. You need to pass like ten options to nano for it to work as expected to edit configuration files and small scripts.
At first you were concerned about backup access, there are multiple facrors of backup access.
Regarding other issues, you either use disk encryption (and a lot of other things as well) and accept these concerns as part of the deal or you dont use it. That's why actual security involves threat modeling and mitigation. Encryption by itself gives little more then headache.
CC1? Usb type-c cables probably. I've seen that they are a bit cracked on others as well, I have 3 spare hotends when the'll die. Also changed two buildplates for bbl ones (require small adapter installation can be found on printables, they were ~2 times cheaper) because they were getting patchy. That's all, extremely reliable machines so far.
Changed hotend on that e5-max, still can't get it to print reliably, I'll try installing cartgrapher in the future, but it just doesn't seem to react to heat predictably, so no expectations there.
alias nano='nano -A -D -E -F -T 4 -Z -g -i -l -m -q -t -% -_'and you need to enable syntax highlighting in nanorc (not all distros enable it by default)include /usr/share/nano/*.nanorcalso there are additional/improved rules for highlighting here https://github.com/galenguyer/nano-syntax-highlighting and you can rebind every key, but it seems that it doesn't support 'chaining' of keys nor multiple modifier keys at the same time.