Not a serious issue: running the conversion tool twice about upgrade-scripts-for-0.17 HOT 4 CLOSED

Also, I ran this against my ~/.config/elvish directory as it existed before my previous invocation of this tool. With the exception of the removal of the code that was so old it had parse errors.

Please close this as soon as you determine there is no reasonable way to obviate problems caused by running the tool twice in a row.

from upgrade-scripts-for-0.17.

The tool is supposed to be idempotent; at least it shouldn't turn a valid Elvish program into an invalid one. Can you share more of script after one conversion that becomes invalid after the second run?

from upgrade-scripts-for-0.17.

@krader1961 looking at the code you are having problematic it seems to be a result not of running the tool twice, but with an empty argument list? That was raised in #4 and fixed now.

from upgrade-scripts-for-0.17.

@xiaq Yes, that is precisely the problem I ran into. This

set edit:insert:binding[Ctrl-R] = []{ interactive:history >/dev/tty 2>&1 }

was being translated to this

set edit:insert:binding[Ctrl-R] = {||] interactive:history >/dev/tty 2>&1 }

The errors I saw from running the migration tool was apparently due to my elvish and associated source being ~2 months old.

from upgrade-scripts-for-0.17.