On May 13, 4:32 pm, Brian Watkins <wildu...@gmail.com> wrote: > Okay, I can get that stack trace, but there's no line for clojure.core/ > divide in your trace. How would I know which function threw the > exception? "eval" isn't very useful. Ideally I'd like a line number, > too.
Right. It's strange I've never even noticed this before. I guess I've never needed it. I can't help with getting 'eval stack trace line numbers, but perhaps I could suggest a small change to your workflow: 1. Don't use the clojure.main repl to enter a lot of fns. Put 'process, 'some-function, 'higher-up in a file using vim (emacs surely works very close to this). 2. Use the _editor_ REPL to call (higher-up 12) This way if there are any errors you'll be able to get the full stack trace with line numbers. If there are problems, just switch buffers, edit, \ef, switch back to the REPL and call (higher-up 12) again. rinse, repeat... -- 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 Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
