> The main feature in this release is Derek Mansen's work integrating
> clj-stacktrace into the debugger frames, so now you can get stack traces
> with alignment and colorization. I'm very excited about this release
> since it's a significant usability improvement: http://imgur.com/fD3rA
I get the
Phil
> There are lots of problems with version ranges, but this would be a bad> idea
> for Ring specifically because it would allow backwards-incompatible> versions
> to be pulled in when a new breaking clj-stacktrace version is> released.
Thank you for sharing your thoughts.
2012/1/2 Phil Hage
On Tue, Jan 3, 2012 at 12:32 PM, Phil Hagelberg wrote:
> Cedric Greevey writes:
>
>> Seriously, though. Terminals? Escape codes? Impedance mismatches
>> involving term types and escape codes? What is this, the Dark Ages?
>> Those kinds of problems simply should not trouble us in the 21st
>> centu
Cedric Greevey writes:
> Seriously, though. Terminals? Escape codes? Impedance mismatches
> involving term types and escape codes? What is this, the Dark Ages?
> Those kinds of problems simply should not trouble us in the 21st
> century.
Plonk.
--
You received this message because you are subs
Baishampayan Ghose writes:
>> Getting colors outside M-x clojure-jack-in requires a couple extra steps
>> I forgot to document, I just added it here:
>>
>> https://github.com/technomancy/swank-clojure/commit/94fa71f90e52c55d74
>
> Just curious, you mention loading the file `slime-compile-presave`
> Getting colors outside M-x clojure-jack-in requires a couple extra steps
> I forgot to document, I just added it here:
>
> https://github.com/technomancy/swank-clojure/commit/94fa71f90e52c55d74
Just curious, you mention loading the file `slime-compile-presave`,
but I wonder what it has got to do
Baishampayan Ghose writes:
Hi again,
> The second option gives an error the moment the sldb buffer comes
> up. It says -
>
> error in process filter: insert: Wrong number of arguments: (lambda
> nil (ansi-color-apply-on-region (point-min) (point-max))), 3
Ah, yes. Now I've installed clj-stackt
Tassilo,
> Not that I know of. But you could try to run the ansi translation in
> sldb-mode-hook.
>
> --8<---cut here---start->8---
> (defun th-ansi-colorize-buffer ()
> (ansi-color-apply-on-region (point-min) (point-max)))
>
> (add-hook 'sldb-mode-hook 'th-an
Baishampayan Ghose writes:
Hi Baishampayan,
>> ,[ C-h f ansi-color-for-comint-mode-on RET ]
>> | ansi-color-for-comint-mode-on is an interactive compiled Lisp function in
>> | `ansi-color.el'.
>> |
>> | (ansi-color-for-comint-mode-on)
>> |
>> | Set `ansi-color-for-comint-mode' to t.
>
> Than
On Tue, Jan 3, 2012 at 1:03 PM, Tassilo Horn wrote:
>> Thanks, the above steps worked--almost. I now see the raw ANSI color
>> escape codes and not the colors. How do I tell Emacs to interpret the
>> color codes the right way?
>
> ,[ C-h f ansi-color-for-comint-mode-on RET ]
> | ansi-color-for
Baishampayan Ghose writes:
Hi Baishampayan,
>> Getting colors outside M-x clojure-jack-in requires a couple extra
>> steps I forgot to document, I just added it here:
>>
>> https://github.com/technomancy/swank-clojure/commit/94fa71f90e52c55d74
>
> Thanks, the above steps worked--almost. I now se
On Tue, Jan 3, 2012 at 12:28 AM, Baishampayan Ghose wrote:
>> Getting colors outside M-x clojure-jack-in requires a couple extra steps
>> I forgot to document, I just added it here:
>>
>> https://github.com/technomancy/swank-clojure/commit/94fa71f90e52c55d74
>
> Thanks, the above steps worked--alm
> Getting colors outside M-x clojure-jack-in requires a couple extra steps
> I forgot to document, I just added it here:
>
> https://github.com/technomancy/swank-clojure/commit/94fa71f90e52c55d74
Thanks, the above steps worked--almost. I now see the raw ANSI color
escape codes and not the colors.
Keith Irwin writes:
> The only way I could get the colorized stack-trace was to use M-x
> clojure-jack-in.
>
> Normally, I type "lein swank" on a command line, then use M-x
> slime-connect from Emacs. This is so that I can see the
> clojure.tools.logging output. (I've no idea where it goes when y
Takahiro writes:
> http://imgur.com/5NCEW
> Is any procedure needed?
> I've tried 1.3.4 with clojure 1.2.1/1.3.0 and Emacs 23.3.
> My .emacs.el includes only load-path and marmalade settings.
>
>>> including [ring "1.0.1"] in my project.clj, which uses clj-stacktrace
>>> 0.2.2 instead of 0.2.4.
>
> after the underlying CDT library is released.
1.2.6.2-SNAPSHOT is in clojars, but does anyone happen to know when the cdt
github repo is to be updated? or has the project moved?
Thanks!
On Tue, Dec 27, 2011 at 8:03 PM, Phil Hagelberg wrote:
>
> I just pushed out version 1.3.4 of Swank Clojur
On Thu, Dec 29, 2011 at 3:07 AM, Phil Hagelberg wrote:
>> On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote:
>>> I just pushed out version 1.3.4 of Swank Clojure.
>>
>> Does it work with Clojure 1.2? What exclusions do I need for that in
>> my project.clj?
>
> I'm not aware of any issues with
Hi Sean,
> The only problem is when a future version of a dependency introduces a>
> breaking change (which happens quite a lot with relatively new>
> libraries).You are right. hmm which we should choose might be bepend on which
> attitude is conservative or progressive.
Keith> The only way I c
Hi--
The only way I could get the colorized stack-trace was to use M-x
clojure-jack-in.
Normally, I type "lein swank" on a command line, then use M-x slime-connect
from Emacs. This is so that I can see the clojure.tools.logging output.
(I've no idea where it goes when you use clojure-jack-in.
On Wed, Dec 28, 2011 at 6:43 PM, Takahiro wrote:
> I think ring should specify dependency using version range like below.
> [clj-stacktrace "[0.2.2,)"] ;; 0.2.2 <= x
>
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
> I didn't know it until recently, but now I
Hi,
I don't get colored stacktrace.
http://imgur.com/5NCEW
Is any procedure needed?
I've tried 1.3.4 with clojure 1.2.1/1.3.0 and Emacs 23.3.
My .emacs.el includes only load-path and marmalade settings.
>> including [ring "1.0.1"] in my project.clj, which uses clj-stacktrace
>> 0.2.2 instead of 0.
Baishampayan Ghose writes:
> On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote:
>> I just pushed out version 1.3.4 of Swank Clojure.
>
> Does it work with Clojure 1.2? What exclusions do I need for that in
> my project.clj?
I'm not aware of any issues with using Swank Clojure in 1.2. If you
Gert Verhoog writes:
> On 28/12/2011, at 2:03 PM, Phil Hagelberg wrote:
>> I just pushed out version 1.3.4 of Swank Clojure.
>
> Great stuff, thanks! I ran into the problem with an older
> clj-stacktrace jar as you describe in the documentation, because I'm
> including [ring "1.0.1"] in my projec
On 28/12/2011, at 2:03 PM, Phil Hagelberg wrote:
> I just pushed out version 1.3.4 of Swank Clojure.
Great stuff, thanks! I ran into the problem with an older clj-stacktrace jar as
you describe in the documentation, because I'm including [ring "1.0.1"] in my
project.clj, which uses clj-stacktra
On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote:
> I just pushed out version 1.3.4 of Swank Clojure.
Does it work with Clojure 1.2? What exclusions do I need for that in
my project.clj?
Regards,
BG
--
Baishampayan Ghose
b.ghose at gmail.com
--
You received this message because you are
25 matches
Mail list logo
