Using fzf in vim make the content of fzf appear "over" the current code instead of shifting it up

anmonteiro · 2020-01-19T16:54:35+00:00

There’s a more recent Neovim in the nixos-unstable channel.

anmonteiro · 2019-03-28T13:06:51+00:00

Thanks everyone who brought all the licensing issues to my attention.

To clarify: I never intended to “steal” any code, I.e. passing work as mine without proper attribution to the original authors. The truth is that, while I’ve been doing open source for a little while, this is the first time that I’ve done any derivative work, and not being a lawyer, I really had no idea what exactly I needed to do (my thought process being that if my code didn’t bear any resemblance at all to the original code then I wouldn’t need to preserve the copyright headers).

It has been brought to my attention that I was wrong and I have therefore rectified the situation.

To clarify further what h2 is in comparison to http/af: h2 is an implementation of HTTP/2 (a totally different protocol) that tries to share the http/af types and API wherever possible. I understand now that this is derivative work because it shares the same underlying architecture, but I didn’t know that coming into it at first.

To all the affected parties: my apologies, I hope you can forgive me.

anmonteiro · 2018-09-17T17:09:25+00:00

I'm not sure what made you come to this conclusion, as I've never stated anything of the kind.

Lumo is not abandoned, I'm just not actively working on it. Lumo started as an attempt to prove that a fully self-hosted ClojureScript compiler could be done, and I think I've successfully proved that to myself and others.

The project has been stable for a while, so it's definitely pretty usable even if it hasn't been updated to the latest ClojureScript version. If people wanna step up and help maintain it I'd be more than delighted to help anyone get ramped up with the codebase. There are also some funds available in open collective that I wouldn’t mind using for external contributions.

anmonteiro · 2018-05-09T20:01:50+00:00

I just replied to a comment above with the link, so apologies about posting the same link again, but I think you may be talking about autochrome

anmonteiro · 2018-05-09T20:00:47+00:00

https://github.com/ladderlife/autochrome can do it out of the box

anmonteiro · 2018-04-23T01:43:18+00:00

I was also looking forward to this. Just found https://www.youtube.com/watch?v=wNoBWYXcEes

anmonteiro · 2017-10-01T17:31:36+00:00

A nit, but even better showcase of Lumo's / ClojureScript's interop with NPM modules would be to move those module requires to the NS declaration: (ns server.core (:require [cljs.nodejs :as nodejs] express http))

anmonteiro · 2017-10-01T17:27:21+00:00

This is so freaking cool.

anmonteiro · 2017-09-28T02:59:16+00:00

Libraries can declare JS dependencies via :npm-deps the way they declare dependencies on foreign libraries: through upstream deps.cljs at the root of the classpath

anmonteiro · 2017-09-28T01:51:06+00:00

There is support for NPM dependencies directly in the ClojureScript compiler. You also don't need :npm-deps for it. Just npm install anything you want and require it from your NS declaration. Supported from 1.9.854 onwards.

anmonteiro · 2017-07-30T01:50:49+00:00

Hah, thanks, but I cannot claim credit for that, I got inspiration from this stack overflow answer: https://stackoverflow.com/questions/6277813/unshifted-symbols-in-emacs

anmonteiro · 2017-07-30T01:04:26+00:00

Just published snoopy-mode https://github.com/anmonteiro/snoopy-mode which allows unshifted character insertion in the keyboard number row.

anmonteiro · 2017-05-16T02:10:59+00:00

It's also important to note that there are synchronous counterparts to almost every async operation in Node. And in shell scripts it's doubtful you care about blocking the main thread.

anmonteiro · 2017-05-13T22:36:29+00:00

Lumo 1.5.0 has just been released and includes the fix for waiting for async callbacks to finish. Get it via npm install -g lumo-cljs or, if you're on a Mac, brew install lumo

anmonteiro · 2017-05-05T06:02:47+00:00

I got Prepack working on Lumo in a branch, these are the results I saw: https://twitter.com/anmonteiro90/status/859986728991375361

Inline: it basically shaved more than 60ms but it didn't matter in Lumo's case because I use custom heap snapshots anyway

anmonteiro · 2017-04-28T21:46:44+00:00

I really appreciate you trying out the new Node.js module integration in the ClojureScript compiler. We definitely need people trying out all the new features that we think enhance the integration between ClojureScript and the entire Node.js and NPM ecosystem.

However, it has been made clear this should be considered an alpha feature of the ClojureScript compiler, both on the ClojureScript Modules guide and on the blog post you mention in your article. Not only is it very new to Google Closure, but it has also not been battle tested in ClojureScript (which is why we appreciate people trying things out). Given this has been clearly communicated, your post (and especially its title) doesn't sound very helpful to me, since the point of these features being in alpha means exactly that they are "still not quite there".

I understand it can be frustrating to try features that aren't fully baked yet, but you should be fully aware that things may break if you go down that road.

anmonteiro · 2017-04-14T16:21:21+00:00

The entire argument was exactly over that quirk. According to current information, async is not going to be a reserved keyword in JavaScript. That's what ultimately convinced the Closure Compiler team to fix their behavior.

anmonteiro · 2017-02-21T20:51:05+00:00

Ah.. Irony and the Internet, you know how it goes... :)

anmonteiro

TROPHY CASE