Proposal: Active "dirty" files

General Discussion
2

Can you elaborate on what the benefit would be?

In my opinion:

  • “Dirty” sounds a bit harsh. The Linux kernel calls it tainted, which is not really much nicer. Its explanation can be found here: Tainted kernels — The Linux Kernel documentation
  • The flags give an early warning that something has been modified. What and with which consequences remain to be evaluated.
  • Someone who can read the klippy.log is very well able to distinguish between the modifications and also able to assess if issues and modifications are related.
  • There is only one single extra that is deemed generally harmless, and this is gcode_shell_command.py. However, even this can be used to crash Klipper by executing not-so-harmless shell commands.
  • The proposed differentiation just for one single extra and to avoid situations like MCU 'mcu' shutdown: Move queue overflow Nr.2 - #5 by hcet14 seems not justified.

Just my 2 cents.