"Main menu" issue on initial run on zsh

"Main menu" issue on initial run on zsh

[Zachary Hill]

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

Not sure if this is the right place for this (never used a mailing list
before) but I found that there is an issue with typing input to the main
menu of zsh on the initial run. (If there's no existing config)

If EDITOR is set to something like vim, vim bindings must be used to type.
For example, when setting up the history settings, one must press "i"
before typing anything into any of the entries.

Sorry if the wording is a bit weird, wasn't sure how to explain the issue.
If you just set the EDITOR environment variable to vim/vi and try to use
the "main menu" to configure some the history settings, you should see what
I mean.

Re: "Main menu" issue on initial run on zsh

[Bart Schaefer]

On Dec 7,  5:28pm, Zachary Hill wrote:
} 
} Sorry if the wording is a bit weird, wasn't sure how to explain the issue.
} If you just set the EDITOR environment variable to vim/vi and try to use
} the "main menu" to configure some the history settings, you should see what
} I mean.

You seem to be talking about the zsh-newuser-install function.

To be really thorough, this should define its own keymap, but for now:

diff --git a/Functions/Newuser/zsh-newuser-install b/Functions/Newuser/zsh-newuser-install
index 37c6029..e4028fd 100644
--- a/Functions/Newuser/zsh-newuser-install
+++ b/Functions/Newuser/zsh-newuser-install
@@ -512,7 +512,7 @@ $default_options[$match[2]])
 	fi
 	print -r "Edit a value.  If it is left blank, nothing will be saved:"
 	edval=$match[2]
-	if vared -p "$match[1]> " -h edval; then
+	if vared -M emacs -p "$match[1]> " -h edval; then
 	  # check this assignment doesn't produce multiple words
 	  # e.g. "HISTFILE=never rm -f ~" does produce multiple words...
 	  # this isn't perfect, e.g. "(this would get split on assignment)",