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
Make a namespace, say, $edit:minibuf:ns: that one can assign a namespace to. Name lookups in the minibuffer should check there first, followed if necessary by the usual interactive lookup. New variables created by var or fn should go in the interactive namespace as now. Thus the only way to alter the minibuffer namespace is to assign a new one to edit:minibuf:ns:.
Rationale
Commands made to be run in the minibuffer don't usually make sense elsewhere. This avoids polluting the interactive namespace with irrelevant commands.
What new feature should Elvish have?
A separate namespace for use in the minibuffer
Make a namespace, say,
$edit:minibuf:ns:
that one can assign a namespace to. Name lookups in the minibuffer should check there first, followed if necessary by the usual interactive lookup. New variables created byvar
orfn
should go in the interactive namespace as now. Thus the only way to alter the minibuffer namespace is to assign a new one toedit:minibuf:ns:
.Rationale
Commands made to be run in the minibuffer don't usually make sense elsewhere. This avoids polluting the interactive namespace with irrelevant commands.
Output of "elvish -version"
0.21.0-dev.0.20240320152034-dfe675a0b467
Code of Conduct
The text was updated successfully, but these errors were encountered: