[FluidNC Issue#1515] Configure file line one corrupted :

#1 – MitchBradley 于 2025-06-23

The usual cause of this problem is the use of a “rich text” editor that saves formatting information along with the plain text. You need to use a “plain text” editor. On Windows, you can use Notepad. On Mac, you can tell TextEdit that you want to use Plain Text mode as opposed to Rich Text https://support.apple.com/guide/textedit/open-documents-txte51413d09/mac

#2 – MitchBradley 于 2025-06-23

I just now added a warning about this to the wiki’s “Config File Overview” page. http://wiki.fluidnc.com/en/config/overview#overview

#3 – oldmangezr 于 2025-06-23

That makes sense!  Thanks very much.  I’ll try again 😊 I was having trouble with Note Pad which wouldn’t allow me to save as a  .yaml file, even under all saving as yaml.text.  So I loaded a true yaml file editor but it never caught the error. I ran the $SS command and saw the symbols.  I thought they were perhaps formatting symbols but I couldn’t seem to get rid of them.   Is there any problem produced downloading a raw vs copied example file from the library?  Thanks again I appreciate your input.  JcSent from my iPhoneOn Jun 23, 2025, at 12:04 PM, Mitch Bradley @.**> wrote:MitchBradley left a comment (bdring/FluidNC#1515)
The usual cause of this problem is the use of a “rich text” editor that saves formatting information along with the plain text. You need to use a “plain text” editor. On Windows, you can use Notepad. On Mac, you can tell TextEdit that you want to use Plain Text mode as opposed to Rich Text https://support.apple.com/guide/textedit/open-documents-txte51413d09/mac

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.*>

#4 – MitchBradley 于 2025-06-23

You can save as .yaml with Notepad. You just have to change the file type to “all files”

!Image

Or you could save as .txt, then rename the file with Explorer or whatever. Or you could save as .txt then set $config/filename=something.txt .

FluidNC doesn’t really care what the extension is. The only naming rule is that the name including the extension must match the value of $config/filename. A .yaml extension is convenient for people that use YAML-aware editors, since they will notice the extension and enable syntax highlighting and other fancy features. Other than that, FluidNC just requires that the contents of the file are in YAML format without any other junk, but does not really care about the name extension.

Raw or copied doesn’t matter, so long as the technique you use does not introduce other characters like line numbers.

#5 – MitchBradley 于 2025-06-23

I’m not sure exactly what you mean by “the library”. There are many different sources of config file examples, including multiple GitHub repositories, the FluidNC wiki, and other places on the web. There is no specific source that is called “the library”, and different locations have different methods for downloading and copying, so when you ask about “raw vs copied from the library”, I cannot give you an accurate answer.

#6 – oldmangezr 于 2025-06-23

Thanks again. Library was a poorly chosen reference to the Github repository for Fluidnc examples of configuration files.   My apologies.  I need to learn to be more precise.   Thank you so much for the helpful information.  I have a lot of learning ahead of me.  Challenges are good.Sent from my iPhoneOn Jun 23, 2025, at 2:31 PM, Mitch Bradley @.*> wrote:MitchBradley left a comment (bdring/FluidNC#1515)
I’m not sure exactly what you mean by “the library”. There are many different sources of config file examples, including multiple GitHub repositories, the FluidNC wiki, and other places on the web. There is no specific source that is called “the library”, and different locations have different methods for downloading and copying, so when you ask about “raw vs copied from the library”, I cannot give you an accurate answer.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.*>