X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Lapo Luchini Subject: Re: Limited regex support in newlib cripples syntax highlighting in nano Date: Fri, 29 Aug 2008 11:43:42 +0200 Lines: 24 Message-ID: References: <31c5d6500808010103r1a0c3823p70351cc15fbf1f23 AT mail DOT gmail DOT com> <20080807134511 DOT GE3806 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Thunderbird 2.0.0.16 (X11/20080728) In-Reply-To: OpenPGP: id=C8F252FB X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Lapo Luchini wrote: > Corinna Vinschen wrote: >> On Aug 1 10:03, Tomi Belan wrote: >>> Cygwin regex.h implementation doesn't support some special sequences, >>> for example \< (beginning of word), \> (end of word) and \b (word >>> boundary). >> >> What you're looking for are perl regular expressions and they are >> only available if nano is built against the perl regex library which >> apparently it isn't. > > There isn't any configure option to use pcre from nano, and including > pcreposix.h instead of regex.h strangely produces compilation errors. Nope, that was a silly typo, I manager to produce the package. Unfortunately some of the distributed .nanorc syntax files are not compatible with PCRE syntax so I'll have to work on it a bit more. Expect a new release shortly. -- Lapo Luchini - http://lapo.it/ “ECC curves are divided into three groups, weak curves, inefficient curves, and curves patented by Certicom” (Peter Gutmann, 2001-08-10) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/