From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: function and lambda, again References: <3224278790110217@naggum.net> <87vgcbq8xb.fsf@nybo.no> Mail-Copies-To: never From: Erik Naggum Message-ID: <3224432463558449@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Mar 2002 19:40:55 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1015443655 193.71.199.50 (Wed, 06 Mar 2002 20:40:55 MET) NNTP-Posting-Date: Wed, 06 Mar 2002 20:40:55 MET Xref: archiver1.google.com comp.lang.lisp:27973 * Kent M Pitman | This is a great example for those who implement font locking to | understand the importance of getting things right. People come to depend | on shifts or non-shifts of color to tell them something, and if the | shifting algorithm isn't completely accurate, you get newbies asking all | kinds of confused questions. Or worse, you get people just assuming they | shouldn't do the thing that aggravates the bug and building up a whole | religion around it, either because they are confused or because they know | better but can't bear the colors not working right. I note in passing that the same applies to editor symbol completion in a language that has different namespace for symbols depending on whether they follow a left paren or not. Experienced Lispers recognize that this is All Wrong -- this is not a good criterion for functionhood at all, yet it is precisely what Emacs Lisp does in all Lisp modes, and a bug that has spread to other Lisp modes, too. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.