[ANN] avi 0.1.8

2016-01-07 Thread Jason Felice 
This release is about WORDS!

Motions implemented:
w, W, e, E, b, B, ge, gE (all motions work with d).

Fixes:
* Fix wrong cursor position after J
* {count} works correctly on t,T,f,F
* dl at end of line deletes character
*  cancels command-line
* Command-line cleared after  or  in position 0
* {count}dk and {count}dj with large {count} delete until BOF or EOF

ALSO, a blog post: Avi is a Spec, First



https://github.com/maitria/avi

avi

A lively vi.
Vision

We love vim. We want more! Test coverage. Flexibilty. Live REPLs!
Guiding Principles

   - Test driven. All functionality covered by tests.
   - Don't defeat vim muscle memory.
   - Code is for people. Be expressive as hell.
   - Be friendly. Especially to noobs.

Contributing

We track upcoming work on a Trello board .
This board has many small things that are easy to pick up, and we'd love to
see you.

I (Jason Felice) would love to walk through the code with you pretty much
any time during the US Eastern work day. Ping me any time on Twitter - I'm
@eraserhd  - or gchat.
Status

Our intention is for the unit tests to provide friendly documention of
what's been implemented so far. To run the unit tests with verbose output,
use

$ lein midje :print-facts

Installing

   - Works with Leiningen 2.3.4
   - On Linux, ncurses-dev or curses-dev or equivalent must be installed.

$ git clone https://github.com/maitria/avi.git
$ cd avi
$ lein install /usr/local

On Linux, you'll likely not have access to /usr/local. In that case you'll
need to use sudo lein install instead or specify a different installation
directory.
License

Copyright 2014 Maitria

You have permission to use this in any way you like (modify it, sell it,
republish it), provided you agree to all the following conditions:

   - you don't mislead anyone about it
   - you don't interfere with our ability to use it
   - you release us from any claims of liability if it causes problems for
   you

-- 
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] prone-pedestal 0.1.1 - Prone for Pedestal

2016-01-07 Thread Eunmin Kim 
Dear Clojurians,

I just released a pedestal interceptor of 
Prone(https://github.com/magnars/prone).

See: https://github.com/eunmin/prone-pedestal

Clojars/Leiningen dependency:

[prone-pedestal "0.1.1"]

-- 
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: Pattern for service with multiple clients using two-way channels?

2016-01-07 Thread William la Forge 
So use a mixed approach.

Queries are likely best handled by including a return channel with the
request.

Updates are likely best handled with a flow approach.

Complex queries may involve passing a return channel deeper into the
process. Especially notification requests.

No one answer is best for all, as usual. But keep simple things simple.

Bill

On Thu, Jan 7, 2016 at 11:16 AM, Vic Putz  wrote:

> Thanks to both of you!
>
> On Wednesday, January 6, 2016 at 10:11:39 PM UTC, tbc++ wrote:
>>
>> Most would perhaps start with the classic approach of having each request
>> contain a :reply-to channel that the responses go into, but I think this is
>> a mistake.
>>
>> IMO, there are two main ways of building systems with core.async 1)
>> request/response. 2) dataflow graphs.
>>
>
> I like the dataflow-graph approach, because I don't like the idea of
> conflating routing with messages that a "sender" or "reply-to" within the
> message requires (though William, I hadn't thought of just putting the
> channel itself as reply-to... great idea if I go that route and much
> simpler than dropping into pub/sub).  So I'd rather the service just
> have "in" and "out" channels and have the wiring be done externally
> (probably through initialization via "component").
>
> And if the components were wired together 1-to-1, that would be dead
> easy.  I'm just not sure how to deal with a component/service which should
> be able to handle multiple in-out connections ... my naïve approach would
> probably just be for services to have a vector of in/out connection pairs
> that got wired up at initialization and maybe go-loops over all of them,
> which would probably work but seems mildly inelegant somehow.
>
> (again, using the toy application of a jukebox service and three
> clients... the clients can't request a song until they know what songs are
> available, so bidirectional communication seems necessary somehow; I can't
> see how to design a wiring diagram without it)
>
> --
> 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/_8fHJ3J-MYg/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.

Re: org-mode Clojure babel

2016-01-07 Thread Johannes Brauer 
now my profiles.clj looks like
{:repl {:plugins [[cider/cider-nrepl "0.11.0-SNAPSHOT"]
  [lein-pprint "1.1.2"]]
:dependencies [[org.clojure/tools.nrepl "0.2.12"]]}}

 But repl complains:
; CIDER 0.11.0snapshot (package: 20160104.1114) (Java 1.8.0_25, Clojure 1.6.0, 
nREPL 0.2.6)
WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
WARNING: The following required nREPL ops are not supported:
  apropos classpath complete eldoc format-code format-edn info inspect-pop 
inspect-push inspect-refresh macroexpand ns-list ns-vars ns-path refresh 
resource stacktrace toggle-trace-var toggle-trace-ns undef
  Please, install (or update) cider-nrepl 0.11.0-SNAPSHOT and restart CIDER
user>

Is anything wrong with my profiles.clj?

Johannes
Am 07.01.2016 um 17:58 schrieb Johannes Brauer 
>:

okay, that I could have figured out myself, sorry. But now I get another 
exception:
error in process sentinel: Could not start nREPL server: 
java.lang.IllegalArgumentException: No value supplied for key: .
 at clojure.lang.PersistentHashMap.create (PersistentHashMap.java:77)
leiningen.core.project$dependency_map.invoke (project.clj:77)
leiningen.core.project$dep_key.invoke (project.clj:228)
leiningen.core.project$reduce_dep_step.invoke (project.clj:232)
clojure.lang.ArrayChunk.reduce (ArrayChunk.java:58)
…
???
Johannes
Am 06.01.2016 um 23:22 schrieb Reid McKenzie 
>:

"0.11.0-SNAPSHOT". It's case sensitive.

Reid

On 01/06/2016 02:23 PM, Johannes Brauer wrote:
I tried this before. But with
{:repl {:plugins [[cider/cider-nrepl " 0.11.0-snapshot"]]}}
in my profiles.clj and cider-jack-in I get a Java exception:
Starting nREPL server via lein repl :headless...
error in process sentinel: Could not start nREPL server: 
java.lang.IllegalArgumentException: Bad artifact coordinates 
cider:cider-nrepl:jar: 0.11.0-snapshot, expected format is 
:[:[:]]:
 at org.sonatype.aether.util.artifact.DefaultArtifact. 
(DefaultArtifact.java:73)
org.sonatype.aether.util.artifact.DefaultArtifact. 
(DefaultArtifact.java:56)
cemerick.pomegranate.aether$artifact.invoke (aether.clj:222)
cemerick.pomegranate.aether$dependency.invoke (aether.clj:230)
cemerick.pomegranate.aether$resolve_dependencies_STAR_$fn__190.invoke 
(aether.clj:708)
…


Am 06.01.2016 um 13:11 schrieb Martin Clausen 
>:

If you update to cider/cider-nrepl 0.11.0-snapshot in your .lein/profiles.clj 
that should fix the problem.

On Wed, Jan 6, 2016 at 1:02 PM Johannes 
> wrote:
BUT!!!

With cider-nrepl set to 0.10.0 and cider set to 0.11.0-snapshot emacs complains:
WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
WARNING: CIDER's version (0.11.0-snapshot) does not match cider-nrepl's version 
(0.10.1). Things will break!

That's not an org-bable problem, but perhaps there is a tip what to do.

Johannes

Am Dienstag, 29. Dezember 2015 13:01:30 UTC+1 schrieb Johannes:
thanks for the hint; indeed it works
Am 21.12.2015 um 16:12 schrieb martin_clausen 
<martin.clau...@gmail.com>:

I found that

Org-mode version 8.3.2 and CIDER 0.11.0 snapshot (package: 20151212.1044)

works great and can be easily be installed from repos.

On Sunday, December 20, 2015 at 6:16:15 PM UTC+1, Johannes wrote:
Thanks, for the explanations. I hope for the best, that there will be an 
working org-babel version in the future. In the mean time I will continue using 
lentilc.

Johannes
Am 10.12.2015 um 16:24 schrieb Matching Socks 
>:

The latest stable Org Babel stopped working with the introduction of Cider 
0.10.0.

You can either go back to Cider 0.9.1, or
(1) get Org 8.3.2,
(2) git-clone Org's repo, and
(3) back-port to 8.3.2 the change in ob-clojure.el that accommodates the latest 
Cider.

The breakage was raised at  
https://github.com/clojure-emacs/cider/issues/1302 and closed with a comment, 
"I don't have nor the time nor the energy to sync up with everyone maintaining 
a 3rd party extension. I just hope they're following the development and will 
do the necessary changes when needed."

But three considerations, which are not Cider's fault, argue for a kinder 
accommodation.  First, Org freezes for bundling into a major Emacs release only 
a few times a century, and the resulting Emacs release then enjoys wide 
distribution for many years.  Second, the bundled Org is unusually significant 
because overriding it with another version is not always fool-proof.  Third, 
Org with Clojure snippets is dynamite!  Therefore, I hope Org will get advice 
from Cider about a more durable technique, so the next Emacs+Org release might 
be useful even on the glacial Emacs time

Re: org-mode Clojure babel

2016-01-07 Thread Martin Clausen 
Have you tried updating leiningen?

On Thu, Jan 7, 2016 at 9:02 PM Johannes Brauer 
wrote:

> now my profiles.clj looks like
> {:repl {:plugins [[cider/cider-nrepl "0.11.0-SNAPSHOT"]
>   [lein-pprint "1.1.2"]]
> :dependencies [[org.clojure/tools.nrepl "0.2.12"]]}}
>
>  But repl complains:
> ; CIDER 0.11.0snapshot (package: 20160104.1114) (Java 1.8.0_25, Clojure
> 1.6.0, nREPL 0.2.6)
> WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
> WARNING: The following required nREPL ops are not supported:
>   apropos classpath complete eldoc format-code format-edn info inspect-pop
> inspect-push inspect-refresh macroexpand ns-list ns-vars ns-path refresh
> resource stacktrace toggle-trace-var toggle-trace-ns undef
>   Please, install (or update) cider-nrepl 0.11.0-SNAPSHOT and restart CIDER
> user>
>
> Is anything wrong with my profiles.clj?
>
> Johannes
>
> Am 07.01.2016 um 17:58 schrieb Johannes Brauer :
>
> okay, that I could have figured out myself, sorry. But now I get another
> exception:
> error in process sentinel: Could not start nREPL server:
> java.lang.IllegalArgumentException: No value supplied for key: .
>  at clojure.lang.PersistentHashMap.create (PersistentHashMap.java:77)
> leiningen.core.project$dependency_map.invoke (project.clj:77)
> leiningen.core.project$dep_key.invoke (project.clj:228)
> leiningen.core.project$reduce_dep_step.invoke (project.clj:232)
> clojure.lang.ArrayChunk.reduce (ArrayChunk.java:58)
> …
> ???
> Johannes
>
> Am 06.01.2016 um 23:22 schrieb Reid McKenzie :
>
> "0.11.0-SNAPSHOT". It's case sensitive.
>
> Reid
>
> On 01/06/2016 02:23 PM, Johannes Brauer wrote:
>
> I tried this before. But with
> {:repl {:plugins [[cider/cider-nrepl " 0.11.0-snapshot"]]}}
> in my profiles.clj and cider-jack-in I get a Java exception:
> Starting nREPL server via lein repl :headless...
> error in process sentinel: Could not start nREPL server:
> java.lang.IllegalArgumentException: Bad artifact coordinates
> cider:cider-nrepl:jar: 0.11.0-snapshot, expected format is
> :[:[:]]:
>  at org.sonatype.aether.util.artifact.DefaultArtifact.
> (DefaultArtifact.java:73)
> org.sonatype.aether.util.artifact.DefaultArtifact.
> (DefaultArtifact.java:56)
> cemerick.pomegranate.aether$artifact.invoke (aether.clj:222)
> cemerick.pomegranate.aether$dependency.invoke (aether.clj:230)
> cemerick.pomegranate.aether$resolve_dependencies_STAR_$fn__190.invoke
> (aether.clj:708)
> …
>
>
> Am 06.01.2016 um 13:11 schrieb Martin Clausen :
>
> If you update to cider/cider-nrepl 0.11.0-snapshot in your
> .lein/profiles.clj that should fix the problem.
>
> On Wed, Jan 6, 2016 at 1:02 PM Johannes  wrote:
>
>> BUT!!!
>>
>> With cider-nrepl set to 0.10.0 and cider set to 0.11.0-snapshot emacs
>> complains:
>> WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
>> WARNING: CIDER's version (0.11.0-snapshot) does not match cider-nrepl's
>> version (0.10.1). Things will break!
>>
>> That's not an org-bable problem, but perhaps there is a tip what to do.
>>
>> Johannes
>>
>> Am Dienstag, 29. Dezember 2015 13:01:30 UTC+1 schrieb Johannes:
>>>
>>> thanks for the hint; indeed it works
>>>
>>> Am 21.12.2015 um 16:12 schrieb martin_clausen <
>>> martin.clau...@gmail.com>:
>>>
>>> I found that
>>>
>>> Org-mode version 8.3.2 and CIDER 0.11.0 snapshot (package:
>>> 20151212.1044)
>>>
>>> works great and can be easily be installed from repos.
>>>
>>> On Sunday, December 20, 2015 at 6:16:15 PM UTC+1, Johannes wrote:

 Thanks, for the explanations. I hope for the best, that there will be
 an working org-babel version in the future. In the mean time I will
 continue using lentilc.

 Johannes

 Am 10.12.2015 um 16:24 schrieb Matching Socks :

 The latest stable Org Babel stopped working with the introduction of
 Cider 0.10.0.

 You can either go back to Cider 0.9.1, or
 (1) get Org 8.3.2,
 (2) git-clone Org's repo, and
 (3) back-port to 8.3.2 the change in ob-clojure.el that accommodates
 the latest Cider.

 The breakage was raised at
 
 https://github.com/clojure-emacs/cider/issues/1302 and closed with a
 comment, "I don't have nor the time nor the energy to sync up with everyone
 maintaining a 3rd party extension. I just hope they're following the
 development and will do the necessary changes when needed."

 But three considerations, which are not Cider's fault, argue for a
 kinder accommodation.  First, Org freezes for bundling into a major Emacs
 release only a few times a century, and the resulting Emacs release then
 enjoys wide distribution for many years.  Second, the bundled Org is
 unusually significant because overriding

Re: org-mode Clojure babel

2016-01-07 Thread Johannes Brauer 
thanks a lot,Martin, upgrading leiningen from 2.5.1 to 2.5.3 solves the problem

Johannes
Am 07.01.2016 um 21:05 schrieb Martin Clausen 
>:

Have you tried updating leiningen?

On Thu, Jan 7, 2016 at 9:02 PM Johannes Brauer 
> wrote:
now my profiles.clj looks like
{:repl {:plugins [[cider/cider-nrepl "0.11.0-SNAPSHOT"]
  [lein-pprint "1.1.2"]]
:dependencies [[org.clojure/tools.nrepl "0.2.12"]]}}

 But repl complains:
; CIDER 0.11.0snapshot (package: 20160104.1114) (Java 1.8.0_25, Clojure 1.6.0, 
nREPL 0.2.6)
WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
WARNING: The following required nREPL ops are not supported:
  apropos classpath complete eldoc format-code format-edn info inspect-pop 
inspect-push inspect-refresh macroexpand ns-list ns-vars ns-path refresh 
resource stacktrace toggle-trace-var toggle-trace-ns undef
  Please, install (or update) cider-nrepl 0.11.0-SNAPSHOT and restart CIDER
user>

Is anything wrong with my profiles.clj?

Johannes
Am 07.01.2016 um 17:58 schrieb Johannes Brauer 
>:

okay, that I could have figured out myself, sorry. But now I get another 
exception:
error in process sentinel: Could not start nREPL server: 
java.lang.IllegalArgumentException: No value supplied for key: .
 at clojure.lang.PersistentHashMap.create (PersistentHashMap.java:77)
leiningen.core.project$dependency_map.invoke (project.clj:77)
leiningen.core.project$dep_key.invoke (project.clj:228)
leiningen.core.project$reduce_dep_step.invoke (project.clj:232)
clojure.lang.ArrayChunk.reduce (ArrayChunk.java:58)
…
???
Johannes
Am 06.01.2016 um 23:22 schrieb Reid McKenzie 
>:

"0.11.0-SNAPSHOT". It's case sensitive.

Reid

On 01/06/2016 02:23 PM, Johannes Brauer wrote:
I tried this before. But with
{:repl {:plugins [[cider/cider-nrepl " 0.11.0-snapshot"]]}}
in my profiles.clj and cider-jack-in I get a Java exception:
Starting nREPL server via lein repl :headless...
error in process sentinel: Could not start nREPL server: 
java.lang.IllegalArgumentException: Bad artifact coordinates 
cider:cider-nrepl:jar: 0.11.0-snapshot, expected format is 
:[:[:]]:
 at org.sonatype.aether.util.artifact.DefaultArtifact. 
(DefaultArtifact.java:73)
org.sonatype.aether.util.artifact.DefaultArtifact. 
(DefaultArtifact.java:56)
cemerick.pomegranate.aether$artifact.invoke (aether.clj:222)
cemerick.pomegranate.aether$dependency.invoke (aether.clj:230)
cemerick.pomegranate.aether$resolve_dependencies_STAR_$fn__190.invoke 
(aether.clj:708)
…


Am 06.01.2016 um 13:11 schrieb Martin Clausen 
>:

If you update to cider/cider-nrepl 0.11.0-snapshot in your .lein/profiles.clj 
that should fix the problem.

On Wed, Jan 6, 2016 at 1:02 PM Johannes 
> wrote:
BUT!!!

With cider-nrepl set to 0.10.0 and cider set to 0.11.0-snapshot emacs complains:
WARNING: CIDER requires nREPL 0.2.12 (or newer) to work properly
WARNING: CIDER's version (0.11.0-snapshot) does not match cider-nrepl's version 
(0.10.1). Things will break!

That's not an org-bable problem, but perhaps there is a tip what to do.

Johannes

Am Dienstag, 29. Dezember 2015 13:01:30 UTC+1 schrieb Johannes:
thanks for the hint; indeed it works
Am 21.12.2015 um 16:12 schrieb martin_clausen 
<martin.clau...@gmail.com>:

I found that

Org-mode version 8.3.2 and CIDER 0.11.0 snapshot (package: 20151212.1044)

works great and can be easily be installed from repos.

On Sunday, December 20, 2015 at 6:16:15 PM UTC+1, Johannes wrote:
Thanks, for the explanations. I hope for the best, that there will be an 
working org-babel version in the future. In the mean time I will continue using 
lentilc.

Johannes
Am 10.12.2015 um 16:24 schrieb Matching Socks 
>:

The latest stable Org Babel stopped working with the introduction of Cider 
0.10.0.

You can either go back to Cider 0.9.1, or
(1) get Org 8.3.2,
(2) git-clone Org's repo, and
(3) back-port to 8.3.2 the change in ob-clojure.el that accommodates the latest 
Cider.

The breakage was raised at  
https://github.com/clojure-emacs/cider/issues/1302 and closed with a comment, 
"I don't have nor the time nor the energy to sync up with everyone maintaining 
a 3rd party extension. I just hope they're following the development and will 
do the necessary changes when needed."

But three considerations, which are not Cider's fault, argue for a kinder 
accommodation.  First, Org freezes for bundling into a major Emacs release only 
a few times a century, and the resulting Emacs release then enjoys wide 
distribution