Hi all,
I'm happy to announce that a new version of the string manipulation
library, Superstring, is out.
For those of you not already familiar with Superstring, it is a string
manipulation library for Clojure and ClojureScript.
You can read more about the project itself
here:
Some bad code slipped into master for a few minutes but was fixed promptly.
See https://github.com/clojure-emacs/cider/issues/1434 for more details.
Just upgrade CIDER and you should be fine.
On Thursday, November 26, 2015 at 1:16:23 PM UTC+1, Karel Miarka wrote:
>
> I have just installed a new
Font-locking of deprecated vars was just added to CIDER. It's available in
snapshots now, and will be included in 0.10.
On Wednesday, October 14, 2015 at 6:09:21 PM UTC+2, William la Forge wrote:
>
> Going forward, I'd like to deprecate some functions and have a warning
> displayed on first
String manipulation library for clj and
cljs: https://github.com/expez/superstring
On Monday, October 5, 2015 at 9:41:11 PM UTC+2, James Reeves wrote:
>
> If you've written or know about a Clojure or ClojureScript library, and
> it's not already on clojure-toolbox.com
You can see it if you read:
user=> (read-string "(= (list {'a 42}) '({'a 42}))")
;;=> (= (list {(quote a) 42}) (quote ({(quote a) 42})))
If you remove it:
user=> (= (list {'a 42}) '({a 42}))
;;=> true
On Saturday, September 26, 2015 at 3:12:44 PM UTC+2, Chris Cornelison wrote:
>
> Anyone
It relies on kibit, eastwood and core.typed to provide warnings and errors.
This means support for other dialects will be available when those projects
add support.
On Saturday, September 26, 2015 at 12:19:03 AM UTC+2, JvJ wrote:
>
> Lars, thanks for telling me about squiggly-clojure. It seems
Something like this doesn't exist in CIDER, so you have to write some elisp
yourself, if you want it.
While not exactly what you've envisioned, I think the best solution is
this: https://github.com/clojure-emacs/squiggly-clojure
On Thursday, September 24, 2015 at 10:36:07 PM UTC+2, JvJ wrote:
I'm happy announce the release of version 2.0.0 of
https://github.com/expez/superstring, a string manipulation library.
The most notable change in 2.0.0 is the addition of clojurescript support.
To read about the other changes check out:
I'm happy to announce the release of version 1.1.0 of
https://github.com/expez/superstring
This was meant as a bugfix release, but I couldn't help myself and added
two functions as well before I got around to cutting the release.
You can read about the specifics here:
refactor-nrepl, which is the brain behind refactoring libraries like
clj-refactor and clj-light-refactor uses:
1. find/find-namespaces-in-jarfile
2. file/clojure-file?
3. find/find-clojure-sources-in-dir
4. parse/read-ns-decl
And finally, dependency, file and track are used together to get a
, but that could be
replaced with a hardcoded regexp solution for CLJS...
Thanks!
On 21 June 2015 at 13:45, Lars Andersen ex...@expez.com javascript:
wrote:
I'm happy to announce the first release of superstring, a string
manipulation library for clojure.
Read more about why I
I'm happy to announce the first release of superstring, a string
manipulation library for clojure.
Read more about why I wrote superstring here:
https://github.com/expez/superstring
Or check out the api docs for a quick overview of what's provided:
I'm not sure I agree that it would make sense, in general, for WEISS and
weiß to be considered equal when ignoring case. I don't write any
german, so I might be wrong on that, though. Thankfully I didn't have to
write my own case-insensitive string comparison code because Oracle already
I actually wish this was how the if-let macro in core worked. Once in a
blue moon I end up writing nested if-let statements or an if-let with a
nested let. Both of these cases look so ridiculous I often re-write the
the code just avoid it.
On Tuesday, June 9, 2015 at 2:00:53 PM UTC+2,
The roadmap for Pedestal has been saying for a while that the focus going
forward is on various forms of documentation, yet most of the files in the
documentation folder haven't been touched for quite some time. When I last
wanted to take a closer look at Pedestal this put me off, because I
A while back I wrote some code for clj-refactor to help out when adding a
new project dependency. When you call this function, in emacs, you get a
completing read of an artifact id, a completing read of available versions,
and it then updates your project.clj and hotloads the new dependency
Cool package!
--
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
11, 2015 at 3:09:28 AM UTC-7, Lars Andersen wrote:
https://github.com/expez/edn.el
is a library for reading an writing edn from emacs lisp.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
https://github.com/expez/edn.el
is a library for reading an writing edn from emacs lisp.
--
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 -
I'd love a module system solving the following problems:
1. Dependency isolation
2. Being able to export vars without having to think about namespace layout
in the project
1. Is a serious problem where transitive dependencies on the classpath put
consumers in jar hell and force library and
, 2015 at 4:05 AM, Lars Andersen ex...@expez.com
javascript: wrote:
I'd love a module system solving the following problems:
1. Dependency isolation
2. Being able to export vars without having to think about namespace
layout in the project
1. Is a serious problem where transitive
your namespace
layout, so I'm not really looking to get rid of the thinking part. :)
On Thursday, April 2, 2015 at 6:05:25 AM UTC-5, Lars Andersen wrote:
I'd love a module system solving the following problems:
1. Dependency isolation
2. Being able to export vars without having to think
My view on this is very much along the line of discussions about
whitespace. While I have opinions about these matters, for the most part I
don't want to think about it--I have more pressing concerns. What's
important to me is consistency within a code base. Just like with
whitespace, I
While creating a bug report for the clojure-fill-paragaph function in Emacs
I also brought up the topic of changing how alignment works. In short, I
would like to be consistent with how data enclosed in #{ }, { } and [ ] is
indented: We indent the new line so the symbols align with the
24 matches
Mail list logo
