You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using pragma unknown-command = disallow in a script and checking it via elvish --compileonly $script, elvish warns that everything in the edit: namespace is not defined. The natural fix for that seems to be to add a use edit to the script, but that causes the script to fail at runtime.
It would be nice to either make elvish --compileonly aware of the edit module or allow use edit.
Hmm yes the edit: module is weird for historical reasons, it's not an importable module, but a special module directed put in the global namespace in interactive mode.
Allowing use edit is perhaps the best approach; it would also make it possible to start the TUI from a script, with a hypothetical API like:
use edit
edit:start-app
I'm rewriting the Elvish TUI and will take this into account.
What happened, and what did you expect to happen?
When using
pragma unknown-command = disallow
in a script and checking it viaelvish --compileonly $script
, elvish warns that everything in the edit: namespace is not defined. The natural fix for that seems to be to add ause edit
to the script, but that causes the script to fail at runtime.It would be nice to either make
elvish --compileonly
aware of the edit module or allowuse edit
.Output of "elvish -version"
0.21.0
Code of Conduct
The text was updated successfully, but these errors were encountered: