Alexis writes:
> Colin Yates writes:
>
>> I used it a few years back
>
> [snip]
>
>> [and] even after man-months spent tinkering, hunting down the right version
>> on MELPA or MARMALADE (or whatever it is called)
>
> i basically only use MELPA and GNU ELPA. In terms of the ~200 packages i've
> i
Ha! Genius.
On 30 March 2015 at 19:47, danle...@gmail.com wrote:
> http://www.scribd.com/doc/30605092/Saturn-v-Flight-Manual
>
> I have tracked down the flight manual of the Saturn-V rocket so we can
> objectively decide whether emacs is more, or less, difficult.
>
> --
> You received this messa
Yes, exactly this.
The camel breaking straw for me was yet another iteration of 'come on,
let's tame this beast, find package X to scratch itch Y, update and
watch something break. Spend hours numptying and googling around, give
up, fresh re-install, do some paid work'. Rinse and repeat.
Cursive
This. I am amazed it isn't more widely shouted about.
On Sunday, 29 March 2015 12:34:23 UTC+1, Jony Hudson wrote:
>
> First, let me shamelessly plug Gorilla REPL http://gorilla-repl.org .
> It's a notebook type REPL, which I think works well as an environment for
> the sort exploratory programmi
Thanks for sharing James! I'll have a look.
As a side note, I see in the example code that you are dissoc-ing on the
component. This can lead to unexpected behaviour as I have
experienced (mostly in repl cases), as this will return a map instead of a
record when the field is not part of the record
Thanks Jeroen - I'd not spotted that! Yes, definitely a better idea -
will update the examples.
James
On 31/03/15 12:49, Jeroen van Dijk wrote:
Thanks for sharing James! I'll have a look.
As a side note, I see in the example code that you are dissoc-ing on
the component. This can lead to une
Joseph Guhlin wrote:
> Incanter gets your pretty far, especially when combined with Gorilla
> REPL, but all the tools and features aren't quite there yet, but progress
> is being made.
Incanter is undergoing major change with the migration to core.matrix, and a
break in the API.
Has anybody o
Colin Yates writes:
> The camel breaking straw for me was yet another iteration of 'come on,
> let's tame this beast, find package X to scratch itch Y, update and
> watch something break. Spend hours numptying and googling around, give
> up, fresh re-install, do some paid work'. Rinse and repeat.
Fluid Dynamics writes:
>> That's nonsense. As soon as you have made yourself acquainted with the
>> basic Emacs terminology and concepts, getting started with Clojure
>> development is a piece of cake. Of course,
>
>
> the devil is in the details. Including the implementation details that lea
You also might want to check out this talk http://youtu.be/YHctJMUG8bI
In part of the talk, he describes how they generate symbols deterministically
to use in query fragments that can be predictably combined into Datomic
queries. Different application, but mostly the same requirements as you st
Mikera writes:
>> I would say, lack of numpy or equivalent. And nice tools to link between
>> Clojure and the many C/Fortran numeric libraries. Python and R do this
>> natively.
>>
>
> core.matrix is effectively the equivalent of NumPy
>
> In some ways it is much more versatile, because it wor
ReadyForZero (YC S2010) is hiring all types of Clojure engineers, or those
who desire to learn it in Los Angeles (relocation available).
We've been using Clojure since 2011. We've been a little quiet about our
use of it and haven't released much OSS because we were a heads-down,
unprofitable st
The related acq announcement:
http://blog.readyforzero.com/positive-readyforzero/
(I'm not moving to LA, but I think RFZ is great and wish the best.)
On Mar 31, 2015 9:00 AM, "Ignacio Thayer" wrote:
> ReadyForZero (YC S2010) is hiring all types of Clojure engineers, or those
> who desire to lear
Clojure 1.7.0-alpha6 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-alpha6/
- Leiningen: [org.clojure/clojure "1.7.0-alpha6"]
Regression fixes from previous alphas (and one from 1.6):
1) CLJ-1544 was rolled back and will be investigated for a fu
In case anyone is curious about the path from here to a final release, the
remaining items on the 1.7 list can always be found here:
http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10519
The main "feature" things to be done before a beta are optimized range and
the so
On similar lines as Ben suggested (but different use case), here's
what I've been doing to rewrite expressions:
(defmacro rewrite-v2
[src & body]
(let [[a x y] (repeatedly gensym)]
`(let [~(with-meta a {:tag "doubles"}) ~src
~x (aget ~a 0)
~y (aget ~a 1)]
~@(po
Hi,
The fancy printing of exceptions is not working for me.
Ubuntu 14.04.2 LTS
java version "1.8.0_40"
plain clojure jar or lein 2.5.1
gnome terminal
Regards,
Geraldo
On Tuesday, March 31, 2015 at 1:51:13 PM UTC-3, Alex Miller wrote:
>
> Clojure 1.7.0-alpha6 is now available.
>
> Try it via
>
This is exciting! Thanks Alex et al! Been using alpha5 w/o problems in
several projects (and w/ noticeable improvements when I started using
transducers) and will switch to alpha6 asap.
On 31 March 2015 at 18:29, Alex Miller wrote:
> In case anyone is curious about the path from here to a final r
As I mentioned in the change log, the current repl chooses to continue
printing exceptions with no change. But if you print an exception yourself
with, for example, (println *e), you should see it. Currently you'll see
that printed without any pretty-printing - there will likely still be some
c
Looks like a great set of updates!
Unfortunately, as several of us found out today, the change to the StringReader
invoke() signature breaks Instaparse so I’m blocked from testing the World
Singles code base with alpha6 (or master) at the moment. Is that just a hazard
of relying on the internal
I've proposed a patch to instaparse to fix this, I realize it's not the
most elegant version check ever, but it should fix the problem
https://github.com/Engelberg/instaparse/pull/94
On Tue, Mar 31, 2015 at 3:21 PM Sean Corfield wrote:
> Looks like a great set of updates!
>
> Unfortunately, as s
>From my perspective, Instaparse is reaching pretty far into the guts there.
>I'll talk to Rich about it 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 me
I can push a new version of instaparse incorporating Michael Blume's pull
request by the end of the day.
On Tue, Mar 31, 2015 at 3:57 PM, Alex Miller wrote:
> From my perspective, Instaparse is reaching pretty far into the guts
> there. I'll talk to Rich about it though.
>
> --
> You received th
On Mar 31, 2015, at 3:57 PM, Alex Miller wrote:
> From my perspective, Instaparse is reaching pretty far into the guts there.
> I'll talk to Rich about it though.
Thanks. I know we've had several discussions about what should be considered
"API" around some of the Java code that implements Cloj
On Mar 31, 2015, at 4:00 PM, Mark Engelberg wrote:
> I can push a new version of instaparse incorporating Michael Blume's pull
> request by the end of the day.
That would be great, Mark! Thank you!
Sean Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"Perfection is the e
The reason instaparse uses Clojure's string reader is to make sure that
strings inside the context-free grammar DSL are handled consistently with
Clojure's logic for interpreting strings.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
Included Michael Blume's pull request in version 1.3.6.
On Tue, Mar 31, 2015 at 4:11 PM, Mark Engelberg
wrote:
> The reason instaparse uses Clojure's string reader is to make sure that
> strings inside the context-free grammar DSL are handled consistently with
> Clojure's logic for interpreting
This patch is great! It's much needed for my development workflow. One
question: how do I enable conditional reading by default in the REPL? Do I
set certain system properties in the command line like "cond_read=true" ?
--
You received this message because you are subscribed to the Google
Group
With instaparse 1.3.6 available, we’ve been able to upgrade our dev stack to
Clojure 1.7.0-alpha6 and all our automated tests pass (and our full build/test
script seems to be running a bit faster although we haven’t actually
benchmarked our application yet). We’ll push alpha6 into QA either late
This looks nice! In particular the fact that it's expression based makes me
jealous.
>From a look at how it works, is it fair to say that this is mostly designed
for debugging a function at a time, i.e. you can't easily step from one
function to another? Or does it instrument multiple functions in
One question - it appears that the new #object and #error forms aren't
readable at the moment. Is this something that's coming, or is the
intention just that people could provide reader functions for these if they
wanted to?
On 1 April 2015 at 14:01, Sean Corfield wrote:
> With instaparse 1.3.6
We do not expect to provide readers for the #object and #error forms
(afaik). It's not possible to actual create a new Object or Throwable form
that would be useful as an instance.
The new tagged-literal function could be used as a fallback reader function
for either though, which would then allow
Ok, thanks - I was looking for a way to access the data, right, I'll try
tagged-literal for this.
On 1 April 2015 at 17:03, Alex Miller wrote:
> We do not expect to provide readers for the #object and #error forms
> (afaik). It's not possible to actual create a new Object or Throwable form
> tha
33 matches
Mail list logo
