Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Triple-colon ligature in ss07 has odd cursor placement in specific scenarios

未关闭
#216 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
vscode
领域
design

调研方向

首先,在 VS Code v1.100 或 v1.101 中复现 triple-colon ss07 ligature,并在其右侧添加红色波浪线,然后将光标行为与禁用 ss07、v1.000 和 Fira Code 时进行比较。完成的标准是:即使存在波浪线,光标移动和视觉位置在整个连字范围内仍保持一致。

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

描述

In vscode, the interaction between the triple-colon ligature from ss07 (:::) and red squigglies seems to cause issues with cursor placement. Under certain circumstances, the triple-colon ligature renders correctly, but the cursor treats it as two 1.5-wide colon characters and a single 0-width colon.

I've observed this issue in v1.100 and v1.101, but not in v1.000.

In this screenshot, the cursor is logically placed between the 1st and 2nd colon from the left, but visually appears in the middle of the 2nd colon:

329493627-04b163af-7411-4df0-9cef-1e8a3ad1a0a5

Moving the cursor right by 1 character places it at the end of the :::, and moving it right again doesn't visually move the cursor.

After moving it right once:

image

And again (no visual change):

image

It's also worth noting that this only seems to happen when red squigglies are involved on the right side of the triple-colon ligature:

image

This is with ss07 disabled:

image

This is from v1.000, which doesn't appear to have the ligature:

329494799-dcef3275-d021-462a-8184-03bcf93fad8f

Also, this seems to only happen with Monaspace's triple-colon ligature. Here's an example of how it looks with Fira Code and its ligatures enabled:

329495443-6578aaf9-1d8a-484f-8470-42c74dd309f5

(I had originally posted about this in the Nerd Fonts repo related to a different issue I had come across, but this appears to be Monaspace.)

主要语言
Shell
星标
19.7k
派生
325
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

githubnext/monaspace 的其他 Issue

查看 githubnext/monaspace 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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