Copy-On-Write: how to use?

Section 2.4.6 of the Pcbnew documentation describes the Copy-On-Write feature for editing footprints read from the GitHub repository. This allows the user to define local storage for edited versions of the footprints. I would like to do this. Unfortunately, the instructions are not clear. Two tables are shown. One without the use of the allow_pretty_writing_to_this_dir option. The other is supposed to show an example with the use of the option. But it seems there is an error in the document. Both tables show examples without the option. Can someone provide a correct example? Or at least describe which information is to go in which columns?

OK. Lets make the standard Air_Coils_SML_NEOSID library editable.

Open Pcbnew Library manager and switch to Global Libraries tab, and select Air_Coils_SML_NEOSID row. Under the table press the Options Editor. The new dialog will open. Here select allow_pretty_writing_to_this_dir and click Append selected option. It will be inserted to the options table on the left. Select the Value field and enter the path and the folder - unfortunately by the hand (Thanks Dick) - where you want to store local changes. The folder must exist, so you have to create it before any edits you made in this library.

After all click OK to close options window. The Options field for Air_Coils_SML_NEOSID row should be updated.

You can close Library manager.

Now we gonna edit something with Footprint editor. Select the Air_Coils_SML_NEOSID as working library. Select footprint you want to edit. Made your changes and save updated footprint.
When you look now into the folder pointed in allow_pretty_writing_to_this_dir option you should see your updated footprint (I save as a new one).

That’s all.

Thanks for the excellent explanation!

Unfortunately, allow_pretty_writing_to_this_dir doesn’t appear as an option choice for me. I’ll have to do some more investigation to find out why.

Do you have Plugin Type set as Github for the library you want to edit? Is this remote library?
Have you tried to fill the Options field by hand keeping the syntax [option_name]=[value]?

I was able to fill in the field by hand. It worked! Thank you!