triggers the prompt which I think is highly undesirable. emld uses calls like eml_version() all over the place and in places that will get called indirectly when interactive.
I think that having a package helper like eml_version() around is very useful and that we might want to remove the interactive prompt portion and make the calling semantics:
eml_version() returns the current emld_db value, always
eml_version(foo) sets the emld_db value to foo. Can error if foo is not set correctly
I found a situation that's making me rethink the new behavior we added to
eml_version
that prompts when interactive.This code, from the EML package README:
triggers the prompt which I think is highly undesirable.
emld
uses calls likeeml_version()
all over the place and in places that will get called indirectly when interactive.I think that having a package helper like
eml_version()
around is very useful and that we might want to remove the interactive prompt portion and make the calling semantics:eml_version()
returns the currentemld_db
value, alwayseml_version(foo)
sets theemld_db
value tofoo
. Can error iffoo
is not set correctly