From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10366 invoked from network); 17 Dec 2008 22:53:23 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 17 Dec 2008 22:53:23 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 13767 invoked from network); 17 Dec 2008 22:53:18 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 17 Dec 2008 22:53:18 -0000 Received: (qmail 21054 invoked by alias); 17 Dec 2008 22:53:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26154 Received: (qmail 21042 invoked from network); 17 Dec 2008 22:53:11 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 17 Dec 2008 22:53:11 -0000 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by bifrost.dotsrc.org (Postfix) with ESMTP id 84C48801E288 for ; Wed, 17 Dec 2008 23:53:08 +0100 (CET) Received: by yw-out-2324.google.com with SMTP id 5so57816ywb.81 for ; Wed, 17 Dec 2008 14:53:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=L7Pfpg99md7sHMymiMrq4R8qZlzf0tLmol8Thrx5faY=; b=Is36ZJ/+jvgRc07OpTUtYGljyT0Uy7sM0nPPMe5jG9qheI7c2/Lkjb+lrOe3RLQ7DQ 7H4MLluCfcda15Q8W0TPZDdZLjYGccYhAm0l20k17Qv406jMCjfSa2QI+iRR/tiBqZ27 IIu4KTwLXockpzmHbyLntIPCJTcRnceQKgVB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=gU90QxIEtHw0yPSpqb1Q4T76q3Thd/KbtyzhYhMTbxuDL4JrvXLIXlVUW2QgaN/71A B/NZCHxECIST3Y2r0BvpzLQbMFlr31Sf81VXMfHLq7pYDzEQDzb4yGQ+cU8f/WOSUBSi yZPuBZBkyMu2rlZ9oPTK50905huoz8fwpkvRc= Received: by 10.100.94.14 with SMTP id r14mr1016063anb.68.1229554386522; Wed, 17 Dec 2008 14:53:06 -0800 (PST) Received: by 10.100.43.19 with HTTP; Wed, 17 Dec 2008 14:53:06 -0800 (PST) Message-ID: <2d460de70812171453v52c1723cse9d6a0b8a3395043@mail.gmail.com> Date: Wed, 17 Dec 2008 23:53:06 +0100 From: "Richard Hartmann" To: "Zsh Workers" Subject: Plans for zle_highlighting? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: ClamAV 0.92.1/8777/Wed Dec 17 18:36:59 2008 on bifrost X-Virus-Status: Clean Hi all, what are the plans for zle_highlighting? Will it be extended into supporting fully-fledged syntax highlighting[1]? Having the same colours in Vim and ZSH would be awesome :) Also, I think it would help to spur completion code development if there was a highlighting context that matches everything the completion system expects/does not expect to be there. Sprinkle some spelling correction on top (think ls -colour or mplayer -force-idx; both very 'easy' typos to make) and you have yet another feature at which ZSH excels. Richard PS: Yes, I remember the thread about accessing what the completion system thinks should be put at the current position of the cursor. That would very likely need to be addressed first. [1] http://fishshell.org/screenshots.html