Dear Masahiro,
In message CAK7LNATygXm=Z42SYYEXW9NJLYkFMa1gPQ8PB2_8Y4DUWYZOaQ@mail.gmail.com you wrote:
Another wants to load "uEnv.txt" to adjust environments, so the environments from a non-volatile device are just annoying for him.
This is largely a matter of taste, but I consider it as a perfectly valid wish.
He just want to clean the saved environments away, and makes the sectors for environments to the initial state.
This, on the other hand, is not reasonable.
If he does not like the saved environment, he is free to use the regular "env" commands to define one he likes: "env default -f -a" or "env default -f var ..." or "env delete -f var ..." followed by a "env save" provide a lot of options.
There should be no need for manipulating stored data structures in obscure ways.
One could discuss if an expension as "env delete -f -a" makes sense...
As Tom pointed out, the latter can use CONFIG_ENV_IS_NOWHERE.
Of course. TIMTOWTDI...
Best regards,
Wolfgang Denk