Occasionally, the wrong REPL type is selected.
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- clojure, emacs, emacs-lisp
调研方向
从 inf-clojure.el 中第 297 行附近的 inf-clojure--detect-repl-type 开始,检查 inf-clojure--process-response 和 inf-clojure--process-reponse-match-p 如何处理空结果。在本地重置 inf-clojure-repl-type 后,通过 process-activity logging 重现该问题,然后验证检测不会选择错误的 REPL 类型,并验证 eldoc 输出正确使用所选类型。
由索引模型根据 Issue 内容生成。
描述
Occasionally, inf-clojure will select the wrong REPL type. The problem appears to start here at inf-clojure--detect-repl-type: https://github.com/clojure-emacs/inf-clojure/blob/master/inf-clojure.el#L297
I added debug messages around inf-clojure--process-reponse-match-p ( https://github.com/clojure-emacs/inf-clojure/blob/master/inf-clojure.el#L1277) and it looks like what is happening is that one of the calls to inf-clojure--process-response, to check if a certain namespace, like planck.repl, is available, will return a blank string, and then the corresponding type will be selected because it isn't nil.
The most obvious symptom of this issue is that the eldoc output will either be absent or show part of an error message. I added a message to print out the type as soon as it was selected, but you can also see it calling the wrong functions if you follow the instructions for logging process activity here: https://github.com/clojure-emacs/inf-clojure#log-process-activity.
To test this, I had to M-: (setq-local inf-clojure-repl-type nil) RET in the buffer that I was testing in order for inf-clojure to reattempt to determine the REPL type.
Initially, I thought I could reproduce the problem by evaluating the buffer after the REPL starts, but before triggering eldoc (by moving the cursor inside an expression), but I haven't been able to trigger the issue consistently (only about 3 out of 25 attempts).
- 主要语言
- Emacs Lisp
- 星标
- 260
- 派生
- 43
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
clojure-emacs/inf-clojure 的其他 Issue
-
bug
难度 3/5 1-2 天 新手友好度 45/100
clojure-emacs/inf-clojure#216 · 4 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
clojure-emacs/inf-clojure#121 · 6 条评论 ·
-
Multiple repls未关闭
难度 4/5 3-5 天 新手友好度 35/100
clojure-emacs/inf-clojure#118 · 5 条评论 ·
-
Implement ANSI filtering in process responses可能重新可做 @charignon 于 2859 天前认领,目前没有进行中的 PR。 未关闭help wanted
难度 3/5 1-2 天 新手友好度 35/100
clojure-emacs/inf-clojure#91 · 4 条评论 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 25/100
clojure-emacs/inf-clojure#47 · 6 条评论 ·
查看 clojure-emacs/inf-clojure 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
py-econometrics/pyfixest#2114 ·
维护者通常 1 天内回复
-
Verify the Linux Python quick start from a fresh Ubuntu checkout可能已有人在做 @romanv9 今天认领。 未关闭documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 62/100
R0Y00/Xbox2Windows#652 · 1 条评论 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 72/100
Haseeb-MernStack/commune#138 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 70/100
clojure-emacs/cider#4235 ·
维护者通常 1 天内回复