Re: [ANN] Ultra v0.5.1 - a Leiningen plugin for a superior development environment

[W. David Jarvis]

Gotcha!

This behavior is controlled by the plugin Ultra uses for pretty-printing,
Whidbey, and on its lower-level pretty-printing library Puget
. As far as I can tell there isn't an
option to control for this, though the project's author might be open to a
PR. Sorry I can't be of more help :( -- but glad you like it anyways! :)

 - V

On Thu, Jan 12, 2017 at 12:35 PM, Mars0i  wrote:

> On Thursday, January 12, 2017 at 12:25:38 PM UTC-6, David Jarvis wrote:
>>
>> I'm not sure, though I have a hypothesis - is this an issue for all
>> sequences, or just for maps?
>>
>
> All sequences.  Well, not exactly--see below.  But I don't mind the one
> entry-per-line behavior for maps.  It bothers me for simple
> sequences--lists, vectors, etc.
>
> I just realized that the behavior depends on the :width setting and the
> size of the output.  For example if I enter (range 20), the entire sequence
> will be displayed on one line.  If I use range with an argument large
> enough to make the output longer than the :width setting, I get one element
> per line.  However, that's generally not what I want.  I'd rather see as
> many elements as possible, letting the terminal wrap the output (or maybe
> something a little nicer but similar, but terminal wrapping is good
> enough).  This actually led to me disabling ultra earlier today, so I
> wouldn't have to scroll up to peruse a sequence of 200 doubles.  I like its
> other features, though!
>
> --
> 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
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojure/OjRe5WXaXBE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
203.918.2328

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Ultra v0.5.1 - a Leiningen plugin for a superior development environment

[W. David Jarvis]

I'm not sure, though I have a hypothesis - is this an issue for all
sequences, or just for maps?

On Thu, Jan 12, 2017 at 7:58 AM, Mars0i  wrote:

> Hi David (or anyone else)-   Is there a way to make sequences print all on
> one line, as in the default repl behavior, rather than with one element per
> line?  I haven't found anything about this in the documentation or in the
> whidbey config map.   Thanks.
>
> --
> 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
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/clojure/OjRe5WXaXBE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 203.918.2328
>
>
>
>

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Ultra v0.5.1 - a Leiningen plugin for a superior development environment

[W. David Jarvis]

Hey there!

To answer your first question, I keep this sort of configuration in my
~/.lein/profiles.clj. That file looks like this right now:

{:user {:ultra {:repl true}
:plugins [[venantius/ultra "0.5.1"]
  [lein-pprint "1.1.2"]]}}

To answer your second question -- the printer configuration sits as a
dynamic var over in whidbey.repl/printer. There's a convenience function
you can access directly -- whidbey.repl/update-options! that will call
`alter-var-root` on the configuration for you. So your standard usage would
be something like [untested]:

 (whidbey.repl/update-options! (assoc whidbey.repl/printer :your-new-key
your-new-val))

Personally, if I run into something like that I usually just restart my
repl, but hopefully the above is helpful.

Cheers,

 ~ V

On Tue, Jan 10, 2017 at 9:37 PM, Mars0i  wrote:

> One more question--should have included it before.  Is there a way to
> change the print width apart from in profile.clj or project.clj, e.g. with
> a function in the repl.  That way I resize the terminal to see more on each
> line, I wouldn't have to exit out and change the width.  Thanks-
>
> --
> 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
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/clojure/OjRe5WXaXBE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 203.918.2328
>
>
>
>

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] New releases: Glow 0.1.4 and Ultra 0.5.0

[W. David Jarvis]

Fellow Clojurists - 

I'm happy to announce new releases of both Glow and Ultra. 

Glow  is a library for syntax 
highlighting of Clojure source code. It uses ANTLR for parsing and lexing, 
which allows you to bypass concerns about accidentally evaluating the input 
source code while getting better performance than Instaparse. Glow is 
capable of generating ANSI highlighting for the terminal, or HTML/CSS 
highlighting for the web.

Glow 0.1.4 is a fairly simple update, just updating the underlying 
dependencies on clj-antlr and on ANTLR itself.

Ultra  is a Leiningen plugin for a 
superior development environment. It provides a colorized REPL, a 
syntax-highlighted version of `source` (powered by Glow), better data 
structure diffs for test output, and nicer stacktraces. 

Ultra 0.5.0 includes a number of changes, including:

   - Better test reporting on logical expressions
   - ...faster initialization time and a smaller footprint overall
   - ...several bugfixes

Future releases will do your laundry and write your application code for 
you.

Happy hacking,

 - Venantius

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Ultra 0.4.1 released

[W. David Jarvis]

Hey all - 

Happy to announce the release of Ultra 0.4.1! Not too many new features, 
but a number of important bug fixes / desired behavioral changes:

   - Fixed a bug wherein the default colorscheme was devoid of colors. In 
   fact, generally removed colorscheme configuration - I've had no indication 
   that anybody was actually setting custom colorschemes, so from this point 
   on Ultra just gives you a smart default.
   - Added logic to intelligently fall back to Ultra version 0.3.4 when on 
   a Clojure project that didn't yet have reader conditional support. This has 
   been a major frustration for me in using my own library, and I'm hopeful 
   this helps others who work in libraries and applications with older 
   versions of Clojure.
   - Updated all plugin dependencies to their latest versions otherwise. 

As always, the project page can be found 
here: https://github.com/venantius/ultra

Enjoy!

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Ultra 0.4.0

[W. David Jarvis]

Howdy all - 

I'm happy to announce the release of Ultra 0.4.0.

CHANGELOG:
 * Fixed the diff-dispatching interface to correctly diff types - in 
particular, resolves a bug when diffing hash-maps and array-maps.
 * Adds a syntax-highlighted `source`!
 * Adds support for custom printer options, including the width, whether 
metadata is printed, custom delimiters, etc.
 * Updates dependencies and cleans up Ultra's dependency injection model.

Custom `source` at the REPL looks like this:



Due to the requirement for reader conditional support in Ultra's underlying 
dependencies, version 0.4.0 is only available on projects using Clojure 
1.7.0 and later. For those who require Clojure 1.6.0, I recommend staying 
with Ultra 0.3.4.

Cheers!

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Glow 0.1.3, now with server-side syntax highlighting of Clojure source in HTML/CSS

[W. David Jarvis]

Hi everyone!

I'm happy to announce the release of Glow 
 0.1.3. This new release adds the 
ability to generate syntax-highlighted blocks of HTML from an input string 
of Clojure source code. Generated HTML will sit in a div element with class 
"syntax", and a pre block underneath that. Individual elements are 
contained within span tags, much like Pygments. 

You can use your own CSS, or you can use `glow.core/generate-css` with a 
colorscheme map to have Glow generate a CSS file for you. 

Cheers!

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Yagni 0.1.4 released

[W. David Jarvis]

Happy to announce the long-delayed release of Yagni 0.1.4!

This release includes the following major changes: 

 * Fixed a ClassNotFound exception when Yagni encountered a function with a 
name like a class constructor (e.g. `-Something`)
 * Removed the log4j dependency entirely.
 * Cleaned up the main `run-yagni` function to expose a cleaner, more 
functional interface.

Planned changes in Yagni 0.1.5 are support for reader literals, which most 
of the groundwork has been laid for.

As always, feedback/issues/comments welcome :)

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Yagni 0.1.4 released

[W. David Jarvis]

A link to the project page might not have been a bad 
idea: https://github.com/venantius/yagni

On Friday, August 28, 2015 at 9:59:25 AM UTC-7, W. David Jarvis wrote:

 Happy to announce the long-delayed release of Yagni 0.1.4!

 This release includes the following major changes: 

  * Fixed a ClassNotFound exception when Yagni encountered a function with 
 a name like a class constructor (e.g. `-Something`)
  * Removed the log4j dependency entirely.
  * Cleaned up the main `run-yagni` function to expose a cleaner, more 
 functional interface.

 Planned changes in Yagni 0.1.5 are support for reader literals, which most 
 of the groundwork has been laid for.

 As always, feedback/issues/comments welcome :)

  - V


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Glow version 0.1.2 released - a parser and syntax highlighter for Clojure source code.

[W. David Jarvis]

In this particular case, I wanted something that would work specifically on
strings of Clojure code rather than on forms directly. I could obviously go
from the former to the latter but I had hoped to avoid the use of
read-string in this case as well.

Tbh, I've also found c.t.a. to be a little intimidating in the past, though
given what I know now it might be a good time to return to the project to
take a look at what it has to offer some of my other projects.

On Tue, Aug 18, 2015 at 9:21 AM, Aaron Cohen aa...@assonance.org wrote:

 I'm curious why you chose to write your own parser rather than use
 clojure.tools.analyzer https://github.com/clojure/tools.analyzer?

 On Tue, Aug 18, 2015 at 10:53 AM, W. David Jarvis venant...@gmail.com
 wrote:

 Hey all -

 I'm happy to announce the release of version 0.1.2 of Glow
 https://github.com/venantius/glow, the syntax highlighting library I
 open-sourced about a month ago.

 This release comes with a number of massive changes as to the underlying
 nature of the library. In essence, I've moved away from a
 regular-expression driven approach in favor of using a lexical parser to
 build up a parse tree from the input string, which is then transformed into
 a syntax-highlighted string.

 This has two advantages. First, it avoids a major problem I was having
 with the regular expression approach in the form of a StackOverflowError
 when attempting to identify long string literals within the input string.
 Second, it produces an intermediate parse tree which can be transformed
 using fairly standard Instaparse transformations to achieve arbitrary
 formatting output (handy if, for instance, one wanted to produce HTML
 output or hiccup templates).

 It has some disadvantage as well. It's somewhat slower, though I believe
 the code to be more maintainable and comprehensible. It also requires the
 input source code to be valid and parseable Clojure code, which you can
 think of as either an advantage or a disadvantage :P

 Although I had hoped initially to use Instaparse for the project's
 parser, I ended up getting considerably better performance from ANTLR /
 clj-antlr, and so that's the path I've gone down. You can take a look at
 the ANTLR Clojure grammar Glow uses here
 https://github.com/venantius/glow/blob/master/resources/parsers/Clojure.g4
 - I believe it to be comprehensive, and it handles a number of edge cases
 that the grammar in the main ANTLR grammar repo does not.

 As always, I hope you get some usage out of this, and please do files
 issues, PRs, etc (project page: https://github.com/venantius/glow) - or
 just tweet at me @venantius https://twitter.com/venantius.

 Cheers,

  - V

 --
 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
 ---
 You received this message because you are subscribed to the Google Groups
 Clojure group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/MDS961nvpFE/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 

venanti.us
203.918.2328


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Glow version 0.1.2 released - a parser and syntax highlighter for Clojure source code.

[W. David Jarvis]

Hey all - 

I'm happy to announce the release of version 0.1.2 of Glow 
https://github.com/venantius/glow, the syntax highlighting library I 
open-sourced about a month ago.

This release comes with a number of massive changes as to the underlying 
nature of the library. In essence, I've moved away from a 
regular-expression driven approach in favor of using a lexical parser to 
build up a parse tree from the input string, which is then transformed into 
a syntax-highlighted string. 

This has two advantages. First, it avoids a major problem I was having with 
the regular expression approach in the form of a StackOverflowError when 
attempting to identify long string literals within the input string. 
Second, it produces an intermediate parse tree which can be transformed 
using fairly standard Instaparse transformations to achieve arbitrary 
formatting output (handy if, for instance, one wanted to produce HTML 
output or hiccup templates).

It has some disadvantage as well. It's somewhat slower, though I believe 
the code to be more maintainable and comprehensible. It also requires the 
input source code to be valid and parseable Clojure code, which you can 
think of as either an advantage or a disadvantage :P

Although I had hoped initially to use Instaparse for the project's parser, 
I ended up getting considerably better performance from ANTLR / clj-antlr, 
and so that's the path I've gone down. You can take a look at the ANTLR 
Clojure grammar Glow uses here 
https://github.com/venantius/glow/blob/master/resources/parsers/Clojure.g4 
- I believe it to be comprehensive, and it handles a number of edge cases 
that the grammar in the main ANTLR grammar repo does not. 

As always, I hope you get some usage out of this, and please do files 
issues, PRs, etc (project page: https://github.com/venantius/glow) - or 
just tweet at me @venantius https://twitter.com/venantius.

Cheers,

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Initial release of Glow, a tiny library for syntax highlighting Clojure source code

[W. David Jarvis]

Unfortunately, since Glow doesn't use a lisp reader as it's underlying
syntax engine, locals highlighting isn't something that the project can
easily support. Allen Rohner pointed me in the direction of a few other
underlying lisp/clojure readers that might open up avenues for that sort of
feature, and I'd definitely be interested in exploring it, but barring
outside contributions at the moment I think the project will probably stick
with its regex implementation for the immediate future.

Even so - someone else also opened an issue on the project page asking for
HTML output and it wouldn't be that hard to generalize the actual
highlighting process to target multiple output types. I'll noodle on it
some more.

On Mon, Aug 3, 2015 at 1:30 AM, Reid McKenzie rmckenzi...@gmail.com wrote:

 On the contrary, I would argue that there is some interesting stuff
 like locals highlighting that existing highlighting solutions don't or
 can't offer. However as you say pygments fulfills my requirements.

 Reid

 --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/ntz-YPxwryA/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 

venanti.us
203.918.2328


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Initial release of Glow, a tiny library for syntax highlighting Clojure source code

[W. David Jarvis]

I thought about it early on but considered that a space that's largely
already addressed by highlight.js et al. If there's another use case you
had in mind for it that highlight et al. don't satisfy I'd be happy to look
into it :)

On Sun, Aug 2, 2015 at 7:55 AM, Reid McKenzie rmckenzi...@gmail.com wrote:

 Very nice! Have you put any effort into an HTML output target?

 Reid

 --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/ntz-YPxwryA/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 

venanti.us
203.918.2328


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Initial release of Glow, a tiny library for syntax highlighting Clojure source code

[W. David Jarvis]

Hey all - 

I'm very happy to announce yet another OSS project, Glow, which is intended 
to provide a minimal and simple way to enable you to produce 
syntax-highlighted strings of Clojure source code. 

The project page can be found here https://github.com/venantius/glow, and 
as usual I've written up a little blog post about it here 
http://blog.venanti.us/glow/. 

Some screenshots of what it looks like in use can be found below:

https://lh3.googleusercontent.com/-51YuQlep6Mg/Vb0p0_OXOqI/87o/W541BSFchLA/s1600/glow.png

https://lh3.googleusercontent.com/-HX8ZCXgrJtU/Vb0p5kMhDoI/87w/yFXig9P2d3g/s1600/glow_2.png

If you're curious why I did this, I'll happily refer you to this 
https://github.com/venantius/ultra/issues/15#issuecomment-126903426 issue 
on the Ultra project page.


I'm actively soliciting pull requests to improve the library's regular 
expressions - they're tolerably acceptable for now, but I'm no regex expert 
and so a sharp eye would definitely be welcome. 


Hope everyone's having a good weekend otherwise.


Cheers,


 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tool authors: ClojureScript support in tools.namespace?

[W. David Jarvis]

Yagni uses dir/scan-all and tracker. Would love to have ClojureScript 
support.

On Saturday, July 25, 2015 at 7:29:24 PM UTC-4, Brian Marick wrote:

 Midje 

 Stuart Sierra wrote: 
  1. Do you need/want ClojureScript support? 

 Eventually, but not soon. 

  
  2. What namespaces (repl, find, dir, file, parse) do you call in 
  tools.namespace? 

 repl, dir, track, reload 

  
  3. How would you like to distinguish between get me Clojure 
  sources and get me ClojureScript sources? 

 I don't have an opinion. 


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Pink 0.2.0, Score 0.3.0

[W. David Jarvis]

This might be a naive question, but for someone who's only tangentially 
familiar with the space, where does this fit in to the overall Clojure 
music/sound ecosystem (re: overtone et al)?

On Saturday, July 25, 2015 at 1:03:44 PM UTC-4, Steven Yi wrote:

 Thanks Ruslan and best of luck in your musical work! 

 On Sat, Jul 25, 2015 at 12:24 AM, Ruslan Prokopchuk fer@gmail.com 
 javascript: wrote: 
  Steven, thank you for continuing to develop Pink  Score! I have some 
 music 
  projects as my slowly-moving-forward-hobbies, and having pure java, no 
 deps 
  like Supercollider, engine for one of them is very precious! 
  
  пятница, 24 июля 2015 г., 23:47:30 UTC+3 пользователь Steven Yi написал: 
  
  Hi All, 
  
  I'd like to announce the release of Pink 0.2.0 and Score 0.3.0: 
  
  [kunstmusik/pink 0.2.0] 
  [kunstmusik/score 0.3.0] 
  
  Pink is an audio engine library, and Score is a library for 
  higher-level music representations (e.g. notes, phrases, parts, 
  scores). 
  
  ChangeLogs are available at: 
  
  https://github.com/kunstmusik/pink/blob/master/CHANGELOG.md 
  https://github.com/kunstmusik/score/blob/master/CHANGELOG.md 
  
  The quick version is Pink now has some new effects (ringmod, freeverb, 
  chorus) as well as some new filters and delay-based audio functions. 
  Score has a new sieves namespace for Xenakis-style sieves. (An example 
  of sieves and freeverb is available in the music-examples project 
  [1]). 
  
  For any questions, please feel free to email me or post on the 
  pink-users list.  For issues and PR's, please use the facilities on 
  Github for each of the projects. 
  
  Thanks! 
  steven 
  
  
  [1] - 
  
 https://github.com/kunstmusik/music-examples/blob/master/src/music_examples/sieves.clj
  


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Yagni 0.1.2 released!

[W. David Jarvis]

Hey everyone - 

I'm happy to announce the release of version 0.1.2 of Yagni 
(https://github.com/venantius/yagni).

The big focus of this release is around improved JVM/Java interoperability, 
particularly around `defprotocol`, `deftype` and `defrecord` forms. 
Previously Yagni had trouble constructing graph nodes for classes, and 
didn't know to connect generator functions with associated classes or their 
underlying declarations, but it does now. 

I've written up a blog post describing the prior interoperability issues 
and the approach taken in this release 
here: http://blog.venanti.us/static-analysis-clojure-jvm/

There are also some minor bugfixes and convenience updates; I've removed 
logging configuration and added nonzero exit codes when Yagni detects 
unused declarations, which should be helpful for those seeking to use Yagni 
in a continuous integration environment.

As always, feedback, issues, pull requests welcome :)

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Ultra 0.3.4 released

[W. David Jarvis]

Hey all - 

This is, tbh, not a particularly impressive release, and is mostly just 
keeping the project's dependencies up-to-date. It does clear some of the 
way forward for future ClojureScript support in Ultra, but it's not quite 
there yet. Still, for those feeling in need of a refresher (especially if 
you weren't already on 0.3.3), go nuts! :)

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Introducing Yagni, a Leiningen plugin for finding unused code

[W. David Jarvis]

Thanks for the feedback; I agree that it would be nice for Yagni to expose
a functional interface for other programs. I'll add it to the to-do list :)

 - D

On Thu, Jul 2, 2015 at 11:02 AM, Stuart Halloway stuart.hallo...@gmail.com
wrote:

 Thanks Colin, that is exactly it.


 On Thu, Jul 2, 2015 at 2:27 AM, Colin Fleming colin.mailingl...@gmail.com
  wrote:

 I may be putting words in Stuart's mouth here, but what I believe he
 meant is that it would be great if Yagni were just a Clojure library with a
 function you could call passing it everything it needs (probably source
 paths and entry point details), and ideally returning the results as data.
 Then the lein plugin could just call that function and print the results,
 but other tooling which might not use lein could also take advantage of
 Yagni.

 Great work BTW, Yagni looks very cool. I'm planning to implement
 something similar in Cursive but I'll be using the IntelliJ infrastructure
 to do it. The idea is the same, though.

 On 2 July 2015 at 06:31, W. David Jarvis venant...@gmail.com wrote:

 Hey Stuart -

 Could you clarify what you meant your comment? I'm not sure I understand
 what you mean by a pure function in this context.

  - David

 On Tue, Jun 30, 2015 at 8:10 AM, Stuart Halloway 
 stuart.hallo...@gmail.com wrote:

 Nice.

 It would be really cool if run-yagni was a pure function of
 source-paths and mains.  This would make the dependency on lein optional
 and allow adoption on e.g. mainland Java projects.

 Stu

 On Tue, Jun 30, 2015 at 5:44 AM, Yehonathan Sharvit vie...@gmail.com
 wrote:

 Yagni ignore `cljs` files.

 I have opened an issue here:
 https://github.com/venantius/yagni/issues/26




 On Thu, Jun 25, 2015 at 1:53 AM, W. David Jarvis venant...@gmail.com
 wrote:

 Indeed. I'd argue it's better not to have unused code in the codebase
 in the first place, regardless of what the Closure compiler does to help
 when it comes to compiling assets.

 I haven't tested this with cljs projects, but on the face of it I
 don't see why Yagni's methodology wouldn't work. If you get a chance to
 give it a try I'd love the feedback :)

 On Wednesday, June 24, 2015 at 2:58:14 PM UTC-7, juan.facorro wrote:

 That's a good point.

 On Wednesday, June 24, 2015 at 6:53:43 PM UTC-3, Fluid Dynamics
 wrote:

  FMIIW, but I think they serve orthogonal purposes. Google Closure
 finds code (mostly library parts your program doesn't use) that your
 particular program doesn't need and omits it from the build to save 
 disk
 and bandwidth. Yagni finds obsolete code that is no longer reached in 
 your
 program or from *any* public entry point to your library (whether a
 particular program uses that entry point or not) and issues warnings, 
 so
 you know that either something is maintenance deadweight or you have a 
 bug
 because you *meant* to call it somewhere but forgot, or it's become
 accidentally shadowed or something.

   --
 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
 ---
 You received this message because you are subscribed to a topic in
 the Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/fGhjG70w0_U/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 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
 ---
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic

Re: [ANN] Introducing Yagni, a Leiningen plugin for finding unused code

[W. David Jarvis]

Hey Stuart -

Could you clarify what you meant your comment? I'm not sure I understand
what you mean by a pure function in this context.

 - David

On Tue, Jun 30, 2015 at 8:10 AM, Stuart Halloway stuart.hallo...@gmail.com
wrote:

 Nice.

 It would be really cool if run-yagni was a pure function of source-paths
 and mains.  This would make the dependency on lein optional and allow
 adoption on e.g. mainland Java projects.

 Stu

 On Tue, Jun 30, 2015 at 5:44 AM, Yehonathan Sharvit vie...@gmail.com
 wrote:

 Yagni ignore `cljs` files.

 I have opened an issue here: https://github.com/venantius/yagni/issues/26




 On Thu, Jun 25, 2015 at 1:53 AM, W. David Jarvis venant...@gmail.com
 wrote:

 Indeed. I'd argue it's better not to have unused code in the codebase in
 the first place, regardless of what the Closure compiler does to help when
 it comes to compiling assets.

 I haven't tested this with cljs projects, but on the face of it I don't
 see why Yagni's methodology wouldn't work. If you get a chance to give it a
 try I'd love the feedback :)

 On Wednesday, June 24, 2015 at 2:58:14 PM UTC-7, juan.facorro wrote:

 That's a good point.

 On Wednesday, June 24, 2015 at 6:53:43 PM UTC-3, Fluid Dynamics wrote:

  FMIIW, but I think they serve orthogonal purposes. Google Closure
 finds code (mostly library parts your program doesn't use) that your
 particular program doesn't need and omits it from the build to save disk
 and bandwidth. Yagni finds obsolete code that is no longer reached in your
 program or from *any* public entry point to your library (whether a
 particular program uses that entry point or not) and issues warnings, so
 you know that either something is maintenance deadweight or you have a bug
 because you *meant* to call it somewhere but forgot, or it's become
 accidentally shadowed or something.

   --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/fGhjG70w0_U/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 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
 ---
 You received this message because you are subscribed to the Google Groups
 Clojure group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  --
 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
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups Clojure group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojure/fGhjG70w0_U/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojure+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 
 venanti.us
 203.918.2328
 





-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Introducing Yagni, a Leiningen plugin for finding unused code

[W. David Jarvis]

Indeed. I'd argue it's better not to have unused code in the codebase in 
the first place, regardless of what the Closure compiler does to help when 
it comes to compiling assets. 

I haven't tested this with cljs projects, but on the face of it I don't see 
why Yagni's methodology wouldn't work. If you get a chance to give it a try 
I'd love the feedback :)

On Wednesday, June 24, 2015 at 2:58:14 PM UTC-7, juan.facorro wrote:

 That's a good point.

 On Wednesday, June 24, 2015 at 6:53:43 PM UTC-3, Fluid Dynamics wrote:

  FMIIW, but I think they serve orthogonal purposes. Google Closure finds 
 code (mostly library parts your program doesn't use) that your particular 
 program doesn't need and omits it from the build to save disk and 
 bandwidth. Yagni finds obsolete code that is no longer reached in your 
 program or from *any* public entry point to your library (whether a 
 particular program uses that entry point or not) and issues warnings, so 
 you know that either something is maintenance deadweight or you have a bug 
 because you *meant* to call it somewhere but forgot, or it's become 
 accidentally shadowed or something.



-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Introducing Yagni, a Leiningen plugin for finding unused code

[W. David Jarvis]

Hello everyone. 

I'm happy to announce the initial release of Yagni, a Leiningen plugin for 
finding unused code. 

At a high level, Yagni works by identifying all of the interned vars in the 
namespaces findable within your :source-paths, and then walking the forms 
of those vars.

As it walks the forms, it builds a graph of references to other vars. It 
then searches the graph from a set of entrypoints (by default your 
project's :main method), and emits warnings for any vars that it couldn't 
find in the graph's search.

There's some other clever stuff going on there and some options for 
additional customization as well. I've written up a blog post, located here 
http://blog.venanti.us/yagni/, that goes into considerably more detail on 
how the plugin works and what the project's roadmap looks like. 

For those of you who want to look at the repository, it's on GitHub 
here: https://github.com/venantius/yagni

And, of course, for those of you who just want to get started fiddling, you 
can add the following to your project's plugins map `[venantius/yagni 
0.1.1]` and type `lein yagni` to give it a whirl.

Cheers!

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Ultra 0.3.0 released - Leiningen plugin for a superior development environment

[W. David Jarvis]

A little embarrassed to say that 0.3.0 shipped with a material bug; if 
you're going to upgrade there's an 0.3.1 release that doesn't have this 
problem.

On Monday, March 2, 2015 at 11:16:59 AM UTC-8, W. David Jarvis wrote:

 Hi all - 

 I'm happy to announce the release of Ultra 0.3.0. This release contains 
 several significant bugfixes and adds some significant initialization 
 optimizations.

 Bugfixes:
  - Ultra now honors custom `print-methods` instead of overriding them with 
 a set of defaults. 
  - Tests comparing objects of different classes that run over multiple 
 lines are now properly aligned.

 Initialization optimizations:
  - Disabled features in Ultra now no longer load their respective 
 namespaces.
  - Ultra now hooks into REPL and test initialization only, meaning that 
 other lein tasks don't take a performance hit on startup. 

 As always, issues, bugs, feature requests, etc. are welcome over at the 
 project site: https://github.com/venantius/ultra

  - V


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Ultra 0.3.0 released - Leiningen plugin for a superior development environment

[W. David Jarvis]

By which I mean 0.3.2, unless you want to see my println debug statements. 

On Monday, March 2, 2015 at 12:41:07 PM UTC-8, W. David Jarvis wrote:

 A little embarrassed to say that 0.3.0 shipped with a material bug; if 
 you're going to upgrade there's an 0.3.1 release that doesn't have this 
 problem.

 On Monday, March 2, 2015 at 11:16:59 AM UTC-8, W. David Jarvis wrote:

 Hi all - 

 I'm happy to announce the release of Ultra 0.3.0. This release contains 
 several significant bugfixes and adds some significant initialization 
 optimizations.

 Bugfixes:
  - Ultra now honors custom `print-methods` instead of overriding them 
 with a set of defaults. 
  - Tests comparing objects of different classes that run over multiple 
 lines are now properly aligned.

 Initialization optimizations:
  - Disabled features in Ultra now no longer load their respective 
 namespaces.
  - Ultra now hooks into REPL and test initialization only, meaning that 
 other lein tasks don't take a performance hit on startup. 

 As always, issues, bugs, feature requests, etc. are welcome over at the 
 project site: https://github.com/venantius/ultra

  - V



-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Ultra 0.3.0 released - Leiningen plugin for a superior development environment

[W. David Jarvis]

Hi all - 

I'm happy to announce the release of Ultra 0.3.0. This release contains 
several significant bugfixes and adds some significant initialization 
optimizations.

Bugfixes:
 - Ultra now honors custom `print-methods` instead of overriding them with 
a set of defaults. 
 - Tests comparing objects of different classes that run over multiple 
lines are now properly aligned.

Initialization optimizations:
 - Disabled features in Ultra now no longer load their respective 
namespaces.
 - Ultra now hooks into REPL and test initialization only, meaning that 
other lein tasks don't take a performance hit on startup. 

As always, issues, bugs, feature requests, etc. are welcome over at the 
project site: https://github.com/venantius/ultra

 - V

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Ultra 0.2.1 - pprint-source, and playing nicely with CIDER

[W. David Jarvis]

*Ultra: a Leiningen plugin for a superior development environment.*
Release 0.2.1 comes with two changes - one feature, one (major) bugfix.


*First, the feature: pprint-source*
Ultra now has a function for pretty-printing source at the REPL - like 
`source`, but nice looking. At the moment it's squirreled away in 
`ultra.repl/pprint-source` since it uses `read-string`, which is unsafe. At 
some point I might hook it into clojure.repl/source (since - as far as the 
unsafeness goes - you'd already have to have the code in question on your 
classpath), but I'm still weighing the pros and cons there.


*Second, the bugfix: playing nicely with CIDER*
Ultra's been responsible for an unfortunate nREPL middleware ordering bug 
ever since it was open sourced. The effect of this bug (documented here: 
https://github.com/clojure-emacs/cider/issues/961) was to really screw up a 
lot of the CIDER middleware. This latest release forces the nREPL 
middleware Ultra depends on to load first, which gets rid of the problem. 

3 to the emacs community.

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ANN: vim-cljfmt: a vim plugin for cljfmt, the Clojure formatting tool

[W. David Jarvis]

Today I'm open sourcing vim-cljfmt 
(https://github.com/venantius/vim-cljfmt). As the name implies, it's a vim 
plugin for weavejester's cljfmt, intended to fit into the vim developer's 
workflow much as gofmt does, with a BufWritePre hook to format your code on 
write. It leverages Fireplace.vim's quasi-REPL to do the formatting, so it 
doesn't cause Vim to hang while waiting for Lein to run, either (the 
initial `require` of the cljfmt namespace into the REPL will take a sec, of 
course, but you'll only have to do it once). 

Feedback, bug reports, etc. very welcome.

-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: vim-cljfmt: a vim plugin for cljfmt, the Clojure formatting tool

[W. David Jarvis]

Interesting - I'm not sure what that would look like but I'd love to see 
what you come up with. I've got a few different vim plugins along these 
lines that I'm working on so I'd be interested in comparing notes at some 
point.

On Wednesday, February 4, 2015 at 12:28:33 PM UTC-8, Bozhidar Batsov wrote:

 Nice!

 I think it'd be a good idea to wrap cljfmt in a nREPL middleware that we 
 can use from both CIDER and fireplace (and possibly other editors). I might 
 look into adding this to cider-nrepl.

 On 4 February 2015 at 19:07, W. David Jarvis vena...@gmail.com 
 javascript: wrote:

 Today I'm open sourcing vim-cljfmt (
 https://github.com/venantius/vim-cljfmt). As the name implies, it's a 
 vim plugin for weavejester's cljfmt, intended to fit into the vim 
 developer's workflow much as gofmt does, with a BufWritePre hook to format 
 your code on write. It leverages Fireplace.vim's quasi-REPL to do the 
 formatting, so it doesn't cause Vim to hang while waiting for Lein to run, 
 either (the initial `require` of the cljfmt namespace into the REPL will 
 take a sec, of course, but you'll only have to do it once). 

 Feedback, bug reports, etc. very welcome.

 -- 
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clo...@googlegroups.com 
 javascript:
 Note that posts from new members are moderated - please be patient with 
 your first post.
 To unsubscribe from this group, send email to
 clojure+u...@googlegroups.com javascript:
 For more options, visit this group at
 http://groups.google.com/group/clojure?hl=en
 --- 
 You received this message because you are subscribed to the Google Groups 
 Clojure group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to clojure+u...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: vim-cljfmt: a vim plugin for cljfmt, the Clojure formatting tool

[W. David Jarvis]

I'm not sure - I wasn't aware of vim-codefmt until now. I'll take a look at 
it tonight and see about providing hooks into it.

On Wednesday, February 4, 2015 at 2:51:37 PM UTC-8, Magnus Therning wrote:

 On Wed, Feb 04, 2015 at 09:07:34AM -0800, W. David Jarvis wrote: 
  Today I'm open sourcing vim-cljfmt 
  (https://github.com/venantius/vim-cljfmt). As the name implies, it's a 
 vim 
  plugin for weavejester's cljfmt, intended to fit into the vim 
 developer's 
  workflow much as gofmt does, with a BufWritePre hook to format your code 
 on 
  write. It leverages Fireplace.vim's quasi-REPL to do the formatting, so 
 it 
  doesn't cause Vim to hang while waiting for Lein to run, either (the 
  initial `require` of the cljfmt namespace into the REPL will take a sec, 
 of 
  course, but you'll only have to do it once). 

 Is it already possible to hook cljfmt to vim-codefmt[1]? 

 /M 

 [1]: https://github.com/google/vim-codefmt 

 -- 
 Magnus Therning  OpenPGP: 0xAB4DFBA4 
 email: mag...@therning.org javascript:   jabber: mag...@therning.org 
 javascript: 
 twitter: magthe   http://therning.org/magnus 

 I invented the term Object-Oriented, and I can tell you I did not have 
 C++ in mind. 
  -- Alan Kay 


-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.