To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.nntpOpen lugnet.admin.nntp in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / NNTP / 1316
1315  |  1317
Subject: 
Re: // and ** vs {} and [] (was: testing in rtl...)
Newsgroups: 
lugnet.publish, lugnet.admin.nntp
Date: 
Sun, 1 Jun 2003 08:46:27 GMT
Viewed: 
18 times
  
Todd Lehman wrote:
In lugnet.publish, Brian H. Nielsen wrote:
my $BAR = join "", grep { !m/[\Q$foo\E\s]/ } map { chr($_) }
(32..255);

That it would probably get confused by.  What do OEQuoteFix and
Mozilla do in cases like these?

Can't speak for Mozilla, but OEQuotefix doesn't react on the above line (or
any other of Brian's suggestions), it seems to only process special
characters at the beginning, and ending, of a word, and does nothing if
special chars overlap, like *bold/italic/* - I get neither bold nor italic.

(Sorry for the mail Todd, I must've clicked the wrong button)

Anders Isaksson, Sweden
BlockCAD:  http://user.tninet.se/~hbh828t/proglego.htm
Gallery:   http://user.tninet.se/~hbh828t/gallery/index.htm



Message is in Reply To:
  Re: // and ** vs {} and [] (was: testing in rtl...)
 
(...) That's what I used to think too -- but I'm not so sure anymore... (...) the double slash and (2) the http: prefix. (...) I've never seen anyone write anything like that before. But in any case, it's got two leading slashes instead of one. (...) (21 years ago, 30-May-03, to lugnet.publish, lugnet.admin.nntp)

31 Messages in This Thread:









Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR