### !!! This file is read-only. Maybe the used editor indicates that. !!!
17 messages · Page 1 of 1 (latest)
Would be nice that user read the docs. https://github.com/mainsail-crew/mainsail-config#mainsail-klipper-macros-and-settings.
Short answer: yes the file is read only.
Long answer: yes, it must be read only as we doing updates to that file if we finding bugs or adding features. If the user would be able to modifying it all that would be gone than. That’s the reason why we added the variable macro and examples how to customize it. If you “feel” the need that you need to update any macro in there you can always make your own copy of it locally and use it. That will come with the cost that you do not benefit from any update we doing at that file.
So everything in the /config folder is read-only, right ? The funny thing is that I had created a few folders and files in that /config folder previously, which are still there, but now are also read-only 😄
So the way to go now is that we create our own /config_myname folder outside the real one and play around with our settings, macros, etc. there ?
No normally not! All files created by you should be writable. Normally only the mainsail.cfg and Timelapse.cfg is read only as they are linked in and belong to separate GitHub checkouts.
There was a moonraker changes that would make a GitHub checkout direct in the /config folder read only
oh okay, then i mixed that up. I'll have a look at it again
Would you suggest reinstalling Moonraker in that case ?
No, in that case we need to understand your folder structure, reinstalling would end in the exact same behavior
I have RatOS installed, which are the config-files from RatRig for their specific printers. That's probably why my /config folder is quite packed. In the klipper-config folder I have the printer.cfg , and then mainly two folders /Tools , which I created and everything in there is perfectly editable, and then the /config folder with many subfolders containing most of the printer-configuration, macros, shell-macros, both created by RatOS and a few files added by myself, which are all read-only now.
I also can't create new files in the /config folder. Seems like I don't have the permission to do edit in that folder. I would like to change that, but I don't know where that can be changed. If you have an idea, let me know 😉
As far as I know this is also a git repo, like mainsail-config, and only a symlink, then would this behaviour be intended. I might be wrong here because obviously I use no RatOS 😉
If you use RatOS you should ask in there discord. There structure is very special so that I am sure they can help much better than we here
It would be nice to provide that link in the header. That was my point.