Feature Request: Optionally use a separate JVM for linting.

未关闭
#41 8 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

@EricGebhart 已经在做这个了。

开始于 2019年8月14日。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
clojure, emacs-lisp

调研方向

首先检查现有的 Flycheck/Eastwood 集成,以及 issue #40 中描述的 JVM 损坏问题。然后研究 Cider 如何管理连接,并确定将用于代码检查的第二个 JVM 设为可选所需的范围。完成的标准是工作 JVM 仍保持隔离,并且在启用独立 JVM 选项时 linting 仍能正常工作。

由索引模型根据 Issue 内容生成。

描述

I was thinking that my problem #40 could possibly not be as much of a problem if flycheck clojure used a second jvm just for it's purposes. Things seem to work reasonably well in #40 if it weren't for the fact that eastwood corrupts my JVM. And it makes no promises that it won't. So who knows what else could happen that might not result in such an obvious failure. As obvious as it is now, it took me a few days to understand that it wasn't my code or something else.

Cider has had nice connection management working for a while. So I'm wondering how hard would it be to create a second JVM and use that for all of the code checking. It should probably be optional since some people might not want to be running two JVMs.

Obviously the load would have to happen twice. But otherwise, using cider's connections should be fairly straight forward. It seems like this could be an easy win given eastwood's experimental status for repl calls and it would also be faster since the working jvm wouldn't be waiting on the code checks.

If I can help in any way, I'm willing. I might be able to make a pull request, but I can't promise that. I've got other things breathing down my neck.

主要语言
Emacs Lisp
星标
203
派生
23
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

clojure-emacs/squiggly-clojure 的其他 Issue

查看 clojure-emacs/squiggly-clojure 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。