From: ············@gmail.com
Subject: content highlighting
Date: 
Message-ID: <1119208949.392910.265660@g49g2000cwa.googlegroups.com>
Hi,

in all lisp environments I've seen so far, the highlighting is for
syntax, which for me is just waste of colorful ink. Highlighting
comments and constants in a programming language is like highlighting
preposition and conjunction in a human one.

What I would find useful is highlighting
  - symbols exported from the package
  - destructive forms
  - forward method declarations

etc, in other words, things a clever compiler takes into account or
warns about. It would be useful and helpful, and the power of modern
computer would not be wasted on stupid things like painting 'error' in
red in a function's list of parameters just because there is a system
function of the same name.

Is/was there an IDE that does that for Common Lisp?

David

From: Christophe Rhodes
Subject: Re: content highlighting
Date: 
Message-ID: <sqzmtm2lfd.fsf@cam.ac.uk>
·············@gmail.com" <············@gmail.com> writes:

> in all lisp environments I've seen so far, the highlighting is for
> syntax, which for me is just waste of colorful ink. Highlighting
> comments and constants in a programming language is like highlighting
> preposition and conjunction in a human one.
>
> What I would find useful is highlighting
>   - symbols exported from the package
>   - destructive forms
>   - forward method declarations
>
> etc, in other words, things a clever compiler takes into account or
> warns about. It would be useful and helpful, and the power of modern
> computer would not be wasted on stupid things like painting 'error' in
> red in a function's list of parameters just because there is a system
> function of the same name.
>
> Is/was there an IDE that does that for Common Lisp?

If you're going to ILC, you may find Brian Mastenbrook's presentation
(on Wednesday, I believe) interesting.  If not, then you may want to
read the paper, which describes the syntax analysis facilities in the
Climacs editor (website at <http://common-lisp.net/project/climacs/>,
paper on request before Wednesday).  It's not a finished product --
it's barely a started one! -- but it is quite fun to hack on, and it
certainly has the infrastructure to support the kind of feedback that
you want (note that I am not claiming that it currently implements the
feedback that you want out of the box :-).

Christophe
From: Madhu
Subject: Re: content highlighting
Date: 
Message-ID: <m3ll54wgaq.fsf@robolove.meer.net>
Helu  		[OT]

* Kent M Pitman <······@nhplace.com> <·············@nhplace.com> :
|   http://groups-beta.[...]thread/6d271470518e28c2/07b036c01b719aed
|   http://groups-beta.[...]/msg/33e7a350c72d6ce3?hl=en

When citing one's cll articles, I would appreciate it if one could
take the trouble of including the Message-ID header in addition to the
google cookie.

[I often read news offline, and do have a local indexed cache of the
cll archive, and could very well look up your articles, and follow
past discussions.

However using google's URL naming makes that impossible. I'd rather
access my own cache than wade through google's advertising, when I
asynchronously go online.]

Also, groups-gamma.google.com might change the hash cookie 5 years
down the line, while the usenet articles are more timeless than that.

--
Best Regards
Madhu
From: Kent M Pitman
Subject: Re: content highlighting
Date: 
Message-ID: <uvf48qj7x.fsf@nhplace.com>
Madhu <·······@meer.net> writes:

> Helu  		[OT]
> 
> * Kent M Pitman <······@nhplace.com> <·············@nhplace.com> :
> |   http://groups-beta.[...]thread/6d271470518e28c2/07b036c01b719aed
> |   http://groups-beta.[...]/msg/33e7a350c72d6ce3?hl=en
> 
> When citing one's cll articles, I would appreciate it if one could
> take the trouble of including the Message-ID header in addition to the
> google cookie.

Point noted.

Btw, when citing the deficiencies of my citation, I would appreciate
it if you could take the trouble to include the entire reference, so I
could dereference it and give you the message id. ;)