https://github.com/tpope/vim-fireplace
https://github.com/guns/vim-sexp
https://github.com/guns/vim-clojure-static
Also, this might be useful:
1,307 karma · joined April 14, 2012
https://github.com/tpope/vim-fireplace
https://github.com/guns/vim-sexp
https://github.com/guns/vim-clojure-static
Also, this might be useful:
Depending on how things play out, it might make sense to try and merge
[with atom.io]. [...]
The main value of LT isn't about being a better standard editor, it's
taking that editor and making it do things that standard ones can't do.
[...]
From the outset, our goal has been to make programming better and I've
honestly come to the conclusion that LT on its own can't do that. [...]
The truth is that I think we can do orders of magnitude better and I have
some evidence of that already, but it's going to take more than a new tool.
It's going to take a different way of thinking about the problem. That is
what I think will end up being the ultimate legacy of Light Table -
a version of programming that is meaningfully designed for humans. You've
heard us mention "Aurora" a number of times now and I think that's the best
description for this crowd of what we're out to accomplish; programming
designed for humans. This often comes as a surprise to people, but
I honestly don't like to program very much - it just happens to be the only
way to create the things I want.
It should have been clear by then that the LT author had lost interest. That's when I decided[2] to concentrate on making Vim/Emacs better instead of trying to find (or make) a "perfect" foundation upon which the already existing Vim/Emacs plugins could be rebuilt. There's a reason why Sublime re-uses Textmate themes; and Java is useful (tons of libraries) even though it's boring; and Linux is widespread even though it's inelegant compared to Hurd or whatever: there's a giant mountain of existing, working boring tools already built--tools that you will not want to rewrite after your perfect platform is done.Neovim popped up around that time and for the above reasons it made sense to me. If the foundation is imperfect, do the dirty work to make the foundation less-imperfect. With 10% of the work[3], I think Neovim can enable 90% of the goodies I (we?) wanted in LT (and 100% of the visual appeal).
[1] https://groups.google.com/d/msg/light-table-discussion/YTuCH...
[2] http://www.reddit.com/r/vim/comments/1ztxgd/why_atom_cant_re...
[3] Remember: don't discount the work of writing plugins.
Actually, you don't need to do that. GitHub provides a special pulls remote "namespace" on the upstream repo, so you can add it as a fetch pattern to your .git/config like so:
[remote "upstream"]
url = https://github.com/neovim/neovim.git
fetch = +refs/heads/*:refs/remotes/upstream/*
fetch = +refs/pull/*/head:refs/pull/upstream/*
Then when you `git fetch --all`, you will have ALL pull requests available in your local repo in the local pull/ namespace. To check out PR #42: git checkout -b foo refs/pull/upstream/42GitHub is painful for non-trivial reviews. Biggest WTFs:
- No comment threading (or at least collapsing). On a PR with 100 comments[1] it is unlikely that those revisiting the thread need to see (and download, and render...) the first bazillion comments.
- Source "annotations" are lost after a force-push (why not keep around a read-only view of old comments? We have lost some valuable discussions on GH pull requests)
Yes, we try to keep PRs small. But they also need to be meaningful, and sometimes they require (many) more reworks than expected.
Actually, it seems the converse is true. Ray Cromwell recently commented[1] regarding Google Inbox:
> It's nothing to do with JS code execution, the problem is in the rendering engine, essentially too much repainting and rendering stalls, and too little GPU accelerated animation paths.
> Javascript is in a very good state these days in terms of cross browser compatibility, and while CSS support has converged between browsers in terms of correctness, CSS support has not converged on performance between browsers. Safari, Chrome Firefox, and IE have wildly different animation performance hazards on the same markup and debugging this often isn't trivial, for example, finding out that the GPU is stalling on texture uploads deep inside of the render loop.
I use it full-time on supported platforms (everything except Windows), but breaking changes will require occasional reconfiguration, recompilation, or remorse.
There's nothing simple about the Vim source, but Neovim has cut it in half, and modularized it. The Neovim strategy is similar in spirit to a microkernel, or shell tools: let the Vim core operate on inputs, and let external tools (GUIs, plugins) operate on the outputs. Like `find . | grep -v foo | sort` involves three self-contained, well-defined tools.
You're not sacrificing any control. I'll speak only of the ones I know: vundle, neobundle, and vim-plug are using very basic Vim mechanisms to save you the hassle. Appending to &runtimepath is the Vim equivalent of modifying your shell $PATH.
And deferred loading, if you choose to use it (I don't), actually gives you more control over plugin behavior.
> You own your vimfiles
This is emacs mentality. I don't want to own (read: maintain) the plugins I use. If I find a bug, I send a PR upstream so others can benefit. If the bug is unforgivable I uninstall the plugin. (You can also pin to a specific SHA).
VAM[1] tries to. That is the only one I am aware of. But the list is managed manually, which in my opinion is always a bad idea.
I think the best hope for a MELPA-like vim plugin source is to use the vimawesome[2] API, but I'm not aware of any plugin manager that does so yet. vimawesome scrapes various sources and looks at publicly-available .vimrc files. This is a technical solution rather than a "human vigilance" solution. People want to post their vimrcs, so take advantage of that rather than trying to curate a massive list. Passive/organic is usually better than active/centralized[3].
[1] https://github.com/MarcWeber/vim-addon-manager
[3] I know some people still have a soft spot for Yahoo directory, but whatever.
http://www.emacswiki.org/emacs-en/GuileEmacs
> As of the end of GoogleSummerOfCode 2014, the Elisp engine of Emacs is fully replaced with that of libguile, and most things Just Work™. Some performance regression of dynamic scoping (lexically scoped code should be fine), and broken corner cases (like crazy Elisp macros that directly output legacy Elisp bytecode) remain.
[1] http://mitpress.mit.edu/books/chapters/0262693143chapm2.pdf
https://github.com/richardhundt/shine
Shine appears to address a similar need as the luv "ray" branch, _without_ libuv, with a modified version of LuaJIT[1]. I wonder if the author plans to patch LuaJIT upstream?
A recent HN discussion[2] left me wondering where to look for a high-quality well-maintained lua "stdlib". luvit appears to be an entire distribution with its own package manager instead of luarocks/moonrocks. I'm now looking at luv and luajit-libuv. shine looks like a very interesting alternative, but the modified LuaJIT makes it problematic for deploying to users who want to use system-provided LuaJIT.
http://neovim.org/doc/build-reports/clang/
Click on any of the "View Report" links to see a line-by-line step-through of each suspected bug.
(Coverity doesn't allow public access to reports AFAIK, so can't link to it.)
I don't think you have much experience with Vim on Windows. I use Vim on Windows every day for years (terminal and gVim) and the experience is the same or better than mac/unix, except for the lack of a good POSIX shell (which is a problem for every Windows text editor).
> you can have your cursor outside the region you are viewing!
That means you're using the scrollbar. It would be nice if Vim added a jumplist entry when the scrollbar was used though...
Doesn't clang (using a frontend like YCM[1]) provide exactly that?
Cool, I was just looking for something like this with "git merge". Turns out "git merge" already supports it, and I need to get better at using the reflog (@{...}).
> "git add <path>" is the same as "git add -A <path>" now.
> The "-q" option to "git diff-files", which does NOT mean "quiet", has been removed
More intuitive.
> The bitmap-index feature from JGit has been ported, which should significantly improve performance when serving objects from a repository that uses it.
Improves clone performance if you're pulling lots of history, but there still doesn't seem to be a way to sparse-checkout without fetching the entire .git repo.
> Arabic speakers are reproducing at a rate that virtually guarantees it.
That's ridiculous. In the 1970s, Chinese birth rate was ~5/woman [1]. It turns out that dynamic systems change with time.
Anyways, to get back on topic: more accessibility will only improve things.