使用Vim进行Lisp开发 [英] Using Vim for Lisp development

查看:202
本文介绍了使用Vim进行Lisp开发的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在使用Lisp一段时间,但我开始更加认真地在Lisp中做一些真正的工作。我是一个巨大的Vim粉丝,并且想知道如何使用Vim作为我的Lisp开发编辑器来提高效率。插件,工作流程建议等都是受欢迎的。



请不要说使用emacs,因为我已经加入了Vim而且我真的很喜欢享受它作为编辑。

解决方案

Limp旨在成为Vim的全功能Common Lisp IDE。它默认为SBCL,但可以更改为支持大多数其他实现,在文件/usr/local/limp/latest/bin/lisp.sh中替换sbcl为您喜爱的lisp,

这些天讨论Lisp时,通常认为是Common Lisp,ANSI X3J13标准化的语言(参见)使用GNU Clisp,SBCL等实现的HyperSpec Practical Common Lisp 获得优秀教科书CMUCL,AllegroCL等等。



返回Limp。还有其他更轻量级的解决方案,或尝试做其他事情,但我相信提供的环境可以为您提供支架匹配,突出显示,文档查找等功能,即尽可能使其成为交钥匙解决方案。



Limp存储库中,你将会找到SlimVim项目以前的一些工作,即ECL(Embeddable Common Lisp)接口,与后来的版本合并(7.1); Simon还制作了7.2补丁,但尚未合并。 if_ecl.txt 中记录了ECL界面。 。



短期工作是说与7.2合并并向vim_dev提交补丁以将其合并到官方Vim树中。



这引出了我们的长期计划:直接在Vim中使用Lisp将使开始在SWANK前端(在Lisp中运行的SLIME的一部分,使用粘液)方便。 el是在编辑器中运行的部分 - 前端)。



介于两者之间,可能所有的Limp都将使用ECL在Common Lisp中重写界面,使Limp更容易维护(VimScript不是我的最爱),并且用户更容易定制。



官方Limp网站不时下降,但正如所指出的,在Vim.org下载应始终有效,支持小组 limp-devel limp-user 由Google网上论坛托管。如果您觉得需要回答问题,或者甚至想参与开发,请不要犹豫加入。大多数讨论都发生在limp-devel列表中。如果你进入IRC,我在irc.freenode.net上的#limp为'tic'。



祝你好运!


I've been using Lisp on and off for a while but I'm starting to get more serious about doing some "real" work in Lisp. I'm a huge Vim fan and was wondering how I can be most productive using Vim as my editor for Lisp development. Plugins, work flow suggestions, etc. are all welcome.

Please don't say "use emacs" as I've already ramped up on Vim and I'm really enjoying it as an editor.

解决方案

Limp aims to be a fully featured Common Lisp IDE for Vim. It defaults to SBCL, but can be changed to support most other implementations by replacing "sbcl" for your favourite lisp, in the file /usr/local/limp/latest/bin/lisp.sh

When discussing Lisp these days, it is commonly assumed to be Common Lisp, the language standardized by ANSI X3J13 (see the HyperSpec, and Practical Common Lisp for a good textbook) with implementations such as GNU Clisp, SBCL, CMUCL, AllegroCL, and many others.

Back to Limp. There are other solutions that are more light-weight, or try to do other things, but I believe in providing an environment that gives you things like bracket matching, highlighting, documentation lookup, i.e. making it a turn-key solution as much as possible.

In the Limp repository you'll find some of the previous work of the SlimVim project, namely the ECL (Embeddable Common Lisp) interface, merged with later releases (7.1); Simon has also made patches to 7.2 available yet to be merged. The ECL interface is documented in if_ecl.txt.

Short-term work is to do said merging with 7.2 and submit a patch to vim_dev to get it merged into the official Vim tree.

Which leads us to the long-term plans: having Lisp directly in Vim will make it convenient to start working on a SWANK front-end (the part of SLIME that runs in your Lisp, with slime.el being the part that runs in the editor - the frontend).

And somewhere in between, it is likely that all of Limp will be rewritten in Common Lisp using the ECL interface, making Limp easier to maintain (VimScript isn't my favourite) and being easier for users to customize.

The official Limp site goes down from time to time, but as pointed out, the download at Vim.org should always work, and the support groups limp-devel and limp-user are hosted with Google Groups. Don't hesitate to join if you feel you need a question answered, or perhaps even want to join in on development. Most of the discussion takes place on the limp-devel list. If you're into IRC, I'm in #limp on irc.freenode.net as 'tic'.

Good luck!

这篇关于使用Vim进行Lisp开发的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆