zsh-users
 help / color / mirror / code / Atom feed
From: Julien Nicoulaud <julien.nicoulaud@gmail.com>
To: Sorin Ionescu <sorin.ionescu@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: How to get syntax highlighting working??
Date: Wed, 5 Jan 2011 21:44:59 +0100	[thread overview]
Message-ID: <AANLkTikKm-GNAJRw604jOmMfJ_DYFGSBzop0ktE_Dft5@mail.gmail.com> (raw)
In-Reply-To: <0E5EA7AC-5442-477E-8AC4-8337E05524EA@gmail.com>

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

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)
 <https://github.com/nicoulaj/zsh-syntax-highlighting/issues#issue/26>We
will try to fix this ASAP.


2011/1/5 Sorin Ionescu <sorin.ionescu@gmail.com>

> The 'Bind all ZLE events from zle -la to highlighting function.’ loop on
> line 216 is problematic. It overwrites existing bindings and conflicts with
> other scripts. For example, I have a vi-mode oh-my-zsh plugin that indicates
> 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" == "" ]]; then
>
>  MODE_INDICATOR="%{$fg_bold[red]%}<%{$reset_color%}%{$fg[red]%}<<%{$reset_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=$RPROMPT
> function zle-line-init zle-keymap-select {
>  RPROMPT="${${KEYMAP/vicmd/$MODE_INDICATOR}/(main|viins)/$rprompt_cached}"
>  zle reset-prompt
> }
>
> # Accept RETURN in vi command mode.
> function accept_line {
>  RPROMPT=$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 editor.
>
> 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 <julien.nicoulaud@gmail.com>:
> >> Thanks William,
> >> I applied your fix:
> >>
> https://github.com/nicoulaj/zsh-syntax-highlighting/commit/a640bb8b96fe95077b8a8ddc6a31f49912a060ee
> >> .
> >>
> >>
> >> 2011/1/5 William <sirrobin2318@gmail.com>
> >>
> >>> Hi,
> >>>
> >>> I know this is a poor excuse for a patch, but access to git is blocked
> >>> from here.
> >>> To get this to work with my config, I had to change this line;
> >>>                        local aliased_command=${"$(alias $arg)"#*=}
> >>> to
> >>>                        local aliased_command="${"$(alias $arg)"#*=}"
> >>> in _zsh_highlight-zle-buffer, line 166 (in the current version anyway).
> >>>
> >>> nice work btw!
> >>>
> >>>
> >>> On Sun, Jan 2, 2011 at 10:25, Gour <gour@atmarama.net> wrote:
> >>>> On Sat, 25 Dec 2010 19:09:37 +0100
> >>>>>>>>>> "Julien" == <julien.nicoulaud@gmail.com> 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.
> >>>
> >>
>
>

      reply	other threads:[~2011-01-05 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-25 13:16 Guido van Steen
2010-12-25 18:09 ` Julien Nicoulaud
2011-01-02  9:25   ` Gour
2011-01-05  9:56     ` William
2011-01-05 10:35       ` Julien Nicoulaud
2011-01-05 11:08         ` Michel
2011-01-05 20:20           ` Sorin Ionescu
2011-01-05 20:44             ` Julien Nicoulaud [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikKm-GNAJRw604jOmMfJ_DYFGSBzop0ktE_Dft5@mail.gmail.com \
    --to=julien.nicoulaud@gmail.com \
    --cc=sorin.ionescu@gmail.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).