The ‘“The Whitespace Thing” for OCaml‘ is
is an alternative syntax for OCaml that uses indentation to group multi-line expressions
Although I am not to the point where I could like or dislike something like this yet, I wonder how long time OCaml users feel about it?
Most of us WordPress users who are using Feedburner to track our feed subscriptions are using the Feedburner Feedsmith WordPress plugin to make it all work. Unfortuantely that plugin remove the ability for folks to subscribe to RSS tag feeds directly from your blog. In this article, the author explain how to re-enable this feature.
In the function
function ol_feed_redirect()
change this
is_feed() && $feed != 'comments-rss2' && !is_single() &&
to this:
is_feed() && $feed != 'comments-rss2' && !is_single() && !is_tag() &&
Basically you are just telling the plugin that if the URL has a tag argument, it should let WordPress handle the feed rather than Feedburner.
(via the ocamlcore.org team)
Cool can come from what a [thing] is or what it does. But at the core, Cool is about purity of expression, of material objects being infused with human energy, creativity and insight to make them more than just the sum of their parts.
— Mark Hoyer, WHAT IS COOL?, Cycle World 2/2010
I love Mark’s take on cool; from motorcycles to programming languages, it still makes sense. It makes me think about how great it is to be alive, living, in the present. It is a gift.
In this thread the OP discusses implementing Lua on top of Guile as an extension language. It seems that it might be eligible for Google’s SOC sponsorship. While the OP doesn’t mention wanting help, it is interesting, and who knows other folks might like to contribute.
I’ve [Joe Marshall] added `keyword’ objects to MIT Scheme in a way that I hope keeps everyone happy. A keyword is a self-evaluating symbolic token, much like a symbol, but it never needs quoting because it can never mean anything but itself.
The reading and printing of keywords is controlled by the variable *keyword-style*, which can be #f or one of these symbols: cl, dsssl, srfi-88, both
If *keyword-style* is #F (the default), then there is no way to read keywords, and they are printed as #[keyword foo].
If *keyword-style* is ‘cl, then tokens with a leading colon are considered keywords and keywords are printed with a leading colon. Symbols with a leading colon are printed with vertical-bar quotes
and you can create symbols with leading colons by using vertical-bar quotes.
If *keyword-style* is ‘srfi-88, then tokens with a trailing colon are considered keywords and keywords are printed with a trailing colon. Symbols with a trailing colon are printed with vertical-bar quotes and you can create symbols with trailing colons by using vertical-bar quotes.
‘dsssl is a synonym for ‘srfi-88
If *keyword-style* is ‘both, then either syntax is acceptable for reading, but the cl syntax will be used in printing. (Putting a colon on both ends would be weird, so don’t.)
(via MIT-Scheme-devel)
The ‘list-colors-display’ function call displays a list of colors, how they look, and their RGB names in its own window.
(via Got Emacs?)
Here is a link to a post on plt-dev about Russian and Ukrainian localization files for DrScheme.
They live here: russian-string-constants.ss and ukrainian-string-constants.ss.
Here is how to ask Maven to generate Idea project files for you:
mvn idea:idea -DjdkName=1.5
(via Maven)
ParEdit (paredit.el) is a minor mode for performing structured editing of S-expression data. The typical example of this would be Lisp or Scheme source code.
ParEdit helps keep parentheses balanced and adds many keys for moving S-expressions and moving around in S-expressions.
That quote from EmacsWiki really undersells Paredit, though.
Paredit makes it virtually impossible to un-balance parentheses (aka round, square, and curly brackets).
This mode would be especially interesting for folks avoiding Lisp because of the nightmare of balancing parentheses is too much of an obstacle to overcome (in practice of course it really isn’t, even if you don’t use Paredit).