From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5887 invoked by alias); 31 Oct 2013 18:01:57 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18081 Received: (qmail 6828 invoked from network); 31 Oct 2013 18:01:52 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uAiacD2jNTAoVNrr8Se+hVCpMvrjWNpIrEVTt4G3x2Q=; b=IKXEc68g8OuzTk5+kZLZ/ohzUohWG2I85ioq24eMJQskeSX979mbmJl/ntBJlbN6JI HfMoELaPg2jg1IPA35m9KsDr1PKs2puxi5ZrZ7fsBMbQufvinaQ5vp09T71fKmzA3LYI hqaX1YkeEVI/uu5neiZ2++RaDrPEhrZqsV0cWCfakebSTBkScDZGWvirH0rG7PAdXZu9 4W9wZU+50MVtPzxLVnaA9hKUC7C/wWX8p1w3PfOmmSgeQ/tp2DcIkEKIpNvJ4F415HpI 4838sVyJI8kp6EsK/ma44hsI5Z6i3jtsbvTJCeZ07sTDdK0dfah6FXY3ayaDF8jwwSRb vPNQ== X-Gm-Message-State: ALoCoQkgnxwemqqU+PkjqSW0SvtTud38gMSsq9tHboH4sPNityVNuuXYDnUoR2bA8JnHMBK70wxX MIME-Version: 1.0 X-Received: by 10.43.63.15 with SMTP id xc15mr1526530icb.67.1383242510356; Thu, 31 Oct 2013 11:01:50 -0700 (PDT) In-Reply-To: <131031080946.ZM9189@torch.brasslantern.com> References: <131023064759.ZM9762@torch.brasslantern.com> <131025102311.ZM9171@torch.brasslantern.com> <131029231921.ZM7202@torch.brasslantern.com> <131030115149.ZM8228@torch.brasslantern.com> <131031080946.ZM9189@torch.brasslantern.com> Date: Thu, 31 Oct 2013 13:01:50 -0500 Message-ID: Subject: Re: Duplicating TRANSIENT_RPROMPT for left PROPMT? From: Jesse Hathaway To: Bart Schaefer Cc: ZSH Users Mailing List Content-Type: multipart/alternative; boundary=bcaec51d2a3477f41704ea0d3e93 --bcaec51d2a3477f41704ea0d3e93 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Oct 31, 2013 at 10:09 AM, Bart Schaefer wrote: > On Oct 31, 9:07am, Jesse Hathaway wrote: > } > } I tried grabbing the latest tarball from the website and compiling it, > but > > I wouldn't have expected this to be a problem that would fix anyway ... I thought it was a long shot, I just wanted to make sure debian had not added some strange patch. } the results are the same: > } > } ~| /usr/local/bin/zsh -x > } +/home/jhathaway/.zshrc:1> PS1='%~ ' > } +/home/jhathaway/.zshrc:2> vim_ins_mode=' > } -- INSERT --' > } +/home/jhathaway/.zshrc:3> vim_cmd_mode=' > } -- COMMAND --' > } +/home/jhathaway/.zshrc:10> zle -N zle-keymap-select > } +/home/jhathaway/.zshrc:11> zle -N zle-line-init zle-keymap-select > } +/home/jhathaway/.zshrc:20> zle -N zle-line-finish > > > Let's try "zsh -v" instead of "zsh -x" so we can see the function > definitions. > ~| /usr/local/bin/zsh -v set -o vi PS1='%~ ' vim_ins_mode=$'\n'"-- INSERT --" vim_cmd_mode=$'\n'"-- COMMAND --" zle-keymap-select() { vim_mode="${${KEYMAP/vicmd/${vim_cmd_mode}}/(main|viins)/${vim_ins_mode}}" POSTDISPLAY="$vim_mode $KEYMAP" zle redisplay } zle -N zle-keymap-select zle -N zle-line-init zle-keymap-select zle-line-finish() { if [[ -n $POSTDISPLAY ]] then POSTDISPLAY='' zle redisplay fi } zle -N zle-line-finish ~ Also, how are you choosing whether to be in vi mode or emacs mode? The > default is emacs mode, unless you have EDITOR=vi in the environment or > something. > Using the EDITOR environment variable, I also tried setting it explicitly with `set -o vi` Try editing the zle-keymap-select function to put the actual keymap name > into POSTDISPLAY, e.g. > > POSTDISPLAY="$vim_mode $KEYMAP" see above. Thanks, Jesse --bcaec51d2a3477f41704ea0d3e93--