From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20626 invoked by alias); 5 Jan 2011 20:51:53 -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: 15687 Received: (qmail 49 invoked from network); 5 Jan 2011 20:51:50 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW, T_FRT_BELOW2 autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.216.43 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=kxrO50B6b3NT9hdhxjPkgNY4NypA9OlQC2B1hBUJjUU=; b=SaakSWLeuWA9JMbC2x3nxcTe0pfnGBnBrENVx5TfKIgp8oIIEI/4zYzoOxlUj/TjnJ xMLjoio4XGfUGiMc0MYjk3wN9omgl61zZiKIRlBd1FnhPQSOsaI2YrcUEc555kmPqgvO Z72YuGQHAGJwvfl2Sxz53R+vjDQacwxJBEqZc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=cnLUTP+MGknLe0eZ/Vkru/6ACBMjzhfg+E8MgoluyrNHnZvKsu8bZslNJO2p84w0tW aOPil41pTrcRQE9bjySjy1dJ+HJlIyS6FNKLhfHkU71M+vQGCWFQAF9X+NK9ejZbrh+p b/9Z7qReXDrjiuCAnHT825AAPKHcJJ19skaow= MIME-Version: 1.0 In-Reply-To: <0E5EA7AC-5442-477E-8AC4-8337E05524EA@gmail.com> References: <997733.11083.qm@web65612.mail.ac4.yahoo.com> <20110102102556.34910f31@atmarama.noip.me> <0E5EA7AC-5442-477E-8AC4-8337E05524EA@gmail.com> From: Julien Nicoulaud Date: Wed, 5 Jan 2011 21:44:59 +0100 Message-ID: Subject: Re: How to get syntax highlighting working?? To: Sorin Ionescu Cc: zsh-users@zsh.org Content-Type: multipart/alternative; boundary=0016e64b03b6a379ba04991f76f0 --0016e64b03b6a379ba04991f76f0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Sorin, we know about it: https://github.com/nicoulaj/zsh-syntax-highlighting/issues#issue/26 (by the way, please try to use the project to report issues instead of the mailing-list, because not all contributors watch it) We will try to fix this ASAP. 2011/1/5 Sorin Ionescu > The 'Bind all ZLE events from zle -la to highlighting function.=92 loop o= n > line 216 is problematic. It overwrites existing bindings and conflicts wi= th > other scripts. For example, I have a vi-mode oh-my-zsh plugin that indica= tes > when ZSH is in vicmd in ~/.oh-my-zsh/plugins/vi-mode/vi-mode.plugin.zsh > which I have pasted bellow. > > > > # Allow command line editing in an external editor. > autoload -Uz edit-command-line > > # If mode indicator wasn't setup by theme, define a default. > if [[ "$MODE_INDICATOR" =3D=3D "" ]]; then > > MODE_INDICATOR=3D"%{$fg_bold[red]%}<%{$reset_color%}%{$fg[red]%}<<%{$res= et_color%}" > fi > > function zle-line-init { > zle reset-prompt > } > > # If I am using vi keys, I want to know what mode I'm currently using. > # zle-keymap-select is executed every time KEYMAP changes. > # From http://zshwiki.org/home/examples/zlewidgets > rprompt_cached=3D$RPROMPT > function zle-line-init zle-keymap-select { > RPROMPT=3D"${${KEYMAP/vicmd/$MODE_INDICATOR}/(main|viins)/$rprompt_cache= d}" > zle reset-prompt > } > > # Accept RETURN in vi command mode. > function accept_line { > RPROMPT=3D$rprompt_cached > builtin zle .accept-line > } > > zle -N zle-line-init > zle -N zle-keymap-select > zle -N accept_line > zle -N edit-command-line > > # Avoid binding ^J, ^M, ^C, ^?, ^S, ^Q, etc. > bindkey -d # Reset to default. > bindkey -v # Use vi key bindings. > bindkey -M vicmd "^M" accept_line # Alow RETURN in vi command. > bindkey -M vicmd v edit-command-line # ESC-v to edit in an external edito= r. > > bindkey ' ' magic-space > bindkey -M vicmd "gg" beginning-of-history > bindkey -M vicmd "G" end-of-history > bindkey -M vicmd "k" history-search-backward > bindkey -M vicmd "j" history-search-forward > bindkey -M vicmd "?" history-incremental-search-backward > bindkey -M vicmd "/" history-incremental-search-forward > > bindkey -M viins "^L" clear-screen > bindkey -M viins "^W" backward-kill-word > bindkey -M viins "^A" beginning-of-line > bindkey -M viins "^E" end-of-line > > > On 5 Jan 2011, at 06:08, Michel wrote: > > > Thanks ! I haven't awser because I haven't network at home, but your > > work is really nice. > > > > Thank you very much to all contributors ! > > _____________________ > > Michel BARRET > > > > > > > > 2011/1/5 Julien Nicoulaud : > >> Thanks William, > >> I applied your fix: > >> > https://github.com/nicoulaj/zsh-syntax-highlighting/commit/a640bb8b96fe95= 077b8a8ddc6a31f49912a060ee > >> . > >> > >> > >> 2011/1/5 William > >> > >>> Hi, > >>> > >>> I know this is a poor excuse for a patch, but access to git is blocke= d > >>> from here. > >>> To get this to work with my config, I had to change this line; > >>> local aliased_command=3D${"$(alias $arg)"#*=3D= } > >>> to > >>> local aliased_command=3D"${"$(alias $arg)"#*= =3D}" > >>> in _zsh_highlight-zle-buffer, line 166 (in the current version anyway= ). > >>> > >>> nice work btw! > >>> > >>> > >>> On Sun, Jan 2, 2011 at 10:25, Gour wrote: > >>>> On Sat, 25 Dec 2010 19:09:37 +0100 > >>>>>>>>>> "Julien" =3D=3D wrote: > >>>> > >>>> Julien> Hi, > >>>> Julien> just to say I've created a repository and added everyone who > >>>> Julien> made changes as author: > >>>> Julien> https://github.com/nicoulaj/zsh-syntax-highlighting > >>>> > >>>> Thanks a lot...Even reason less to switch to fish. ;) > >>>> > >>>> Otoh, I wonder if it is going to be included as part of zsh? > >>>> > >>>> > >>>> Sincerely, > >>>> Gour > >>>> > >>>> -- > >>>> > >>>> Gour | Hlapicina, Croatia | GPG key: CDBF17CA > >>>> ---------------------------------------------------------------- > >>>> > >>> > >>> > >>> > >>> -- > >>> LIVE LIKE YOUR CAPS LOCK BUTTON IS JAMMED. > >>> > >> > > --0016e64b03b6a379ba04991f76f0--