For your information, there's a paredit port to ccw in progress :-)
2010/1/27 Howard Lewis Ship :
> I too would love to see this. I can't tell you how many times I've
> dropped a ) from a (ns and spent forever hunting it down.
>
> On Wed, Jan 27, 2010 at 8:22 AM, Chouser wrote:
>> On Wed, Jan 27
Superb. Getting a fix so fast.. Open Source at its best!
I tried it. Works as expected.
On Jan 27, 8:50 pm, Chouser wrote:
> On Wed, Jan 27, 2010 at 1:00 PM, Rich Hickey wrote:
>
> > On Jan 27, 11:22 am, Chouser wrote:
> >> On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
> >> > This exception is
On Wed, Jan 27, 2010 at 1:00 PM, Rich Hickey wrote:
>
>
> On Jan 27, 11:22 am, Chouser wrote:
>> On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
>> > This exception is the biggest time waster for me when working with
>> > Clojure. It doesn't give you a hint of where the problem really is.
>> > I st
On Jan 27, 11:22 am, Chouser wrote:
> On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
> > This exception is the biggest time waster for me when working with
> > Clojure. It doesn't give you a hint of where the problem really is.
> > I strongly suggest to improve parse error messages to contain
> >
+1 for paredit. Writing lisp without an IDE geared towards the
language is miserable. Bracket matching is a must-have feature for
lisp programmer. Higher in importance than anything else.
On Jan 27, 9:48 am, Jarkko Oranen wrote:
> You should really give paredit.el a go some time. It feels silly
You should really give paredit.el a go some time. It feels silly to
worry about matching parentheses nowadays.
That aside, I am supportive of any improvement in either compiler or
reader error messages.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
Yes Rich, Please approve this patch!
On Jan 27, 6:22 pm, Chouser wrote:
> On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
> > This exception is the biggest time waster for me when working with
> > Clojure. It doesn't give you a hint of where the problem really is.
> > I strongly suggest to improve
I too would love to see this. I can't tell you how many times I've
dropped a ) from a (ns and spent forever hunting it down.
On Wed, Jan 27, 2010 at 8:22 AM, Chouser wrote:
> On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
>> This exception is the biggest time waster for me when working with
>> Cl
On Wed, Jan 27, 2010 at 4:03 AM, Gabi wrote:
> This exception is the biggest time waster for me when working with
> Clojure. It doesn't give you a hint of where the problem really is.
> I strongly suggest to improve parse error messages to contain
> meaningful info.
I just wrote a patch to LispRe
This exception is the biggest time waster for me when working with
Clojure. It doesn't give you a hint of where the problem really is.
I strongly suggest to improve parse error messages to contain
meaningful info.
--
You received this message because you are subscribed to the Google
Groups "Cloju
10 matches
Mail list logo