Oops, that patch had my debugging statements in it. Here's the correct
one to use.

On Wed, Dec 10, 2008 at 11:44 AM, Bill Clementson <[EMAIL PROTECTED]> wrote:
> Hi Matt,
>
> I had a bit of free time this morning, so I looked into this further
> and came up with a patch (attached). I've forwarded the patch to
> Jeffrey as well, so it should find it's way into swank-clojure in due
> course.
>
> Cheers,
> Bill Clementson
>
> On Wed, Dec 10, 2008 at 9:57 AM, Bill Clementson <[EMAIL PROTECTED]> wrote:
>> Hi Matt,
>>
>> Yes, you should let Jeffrey know about the bug.
>>
>> - Bill
>>
>> On Wed, Dec 10, 2008 at 9:20 AM, MattyDub <[EMAIL PROTECTED]> wrote:
>>>
>>> Thanks for confirming the bug, Bill.  Should we post this to Jeffrey
>>> Chu (assuming it's a swank-clojure issue)?  What's the protocol at
>>> this point?
>>> -Matt
>>>
>>> On Dec 9, 11:03 pm, "Bill Clementson" <[EMAIL PROTECTED]> wrote:
>>>> Hi Matt,
>>>>
>>>>
>>>>
>>>> On Tue, Dec 9, 2008 at 6:43 PM, MattyDub <[EMAIL PROTECTED]> wrote:
>>>>
>>>> > I did an 'svn update' on my clojure (I'm now at revision 1149), and
>>>> > ran ant clean, then ant (the default target).  Then I deleted my old
>>>> > swank-clojure directory, and did a git clone of 
>>>> > git://github.com/jochu/swank-clojure.git.
>>>> > I made sure my .emacs was correctly pointing to the appropriate
>>>> > paths.  I still get the same error.  Perhaps I'm using it
>>>> > incorrectly?  What is the proper usage?  I start slime:
>>>> > M-x slime
>>>> > then load the file by using C-x C-e on the following line in ants.clj:
>>>> > (load-file "c:/home/ants.clj")
>>>> > Then in a buffer pointing to ants.clj, I put the point over a call to
>>>> > render-place, and do M-.  And I get this stack trace:
>>>> > Debugger entered--Lisp error: (error "Synchronous Lisp Evaluation
>>>> > aborted.")
>>>> >  signal(error ("Synchronous Lisp Evaluation aborted."))
>>>> >  error("Synchronous Lisp Evaluation aborted.")
>>>> >  funcall(error "Synchronous Lisp Evaluation aborted.")
>>>> >  apply(funcall (error "Synchronous Lisp Evaluation aborted."))
>>>> >  (let* ((tag ...) (slime-stack-eval-tags ...)) (apply (function
>>>> > funcall) (catch tag ... ...)))
>>>> >  slime-eval((swank:find-definitions-for-emacs "render-place"))
>>>> >  slime-find-definitions-rpc("render-place")
>>>> >  funcall(slime-find-definitions-rpc "render-place")
>>>> >  slime-find-definitions("render-place")
>>>> >  (slime-edit-definition-cont (slime-find-definitions name) name
>>>> > where)
>>>> >  (or (run-hook-with-args-until-success (quote slime-edit-definition-
>>>> > hooks) name where) (slime-edit-definition-cont (slime-find-definitions
>>>> > name) name where))
>>>> >  slime-edit-definition("render-place")
>>>> >  call-interactively(slime-edit-definition)
>>>>
>>>> > I must be doing something wrong - any ideas what?
>>>> > -Matt
>>>>
>>>> Hmm, looks like I was mistaken in my earlier email. I get the same
>>>> thing when I do M-. on "render-place". However, if I place the point
>>>> on "defn" (or any other symbol name that is in a jar file), it goes to
>>>> the correct source in the jar file. At first, I thought it was because
>>>> ant.clj was not in the class path; however, it doesn't work when
>>>> ant.clj is in the class path either. I applied the
>>>> find-definitions-for-emacs patch proposed in the earlier email;
>>>> however, that doesn't work either. This used to work for local
>>>> definitions and was broken a few svn changes ago. It was fixed for
>>>> clojure definitions that are in jar files; however, it seems to still
>>>> be broken for local definitions.
>>>>
>>>> - Bill
>>> >>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Attachment: patch
Description: Binary data

Reply via email to