-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
68 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
# v0.2.2 | ||
|
||
## Fix | ||
- 修复了因内存提前释放导致的日志文件名出错 | ||
- 修复了一些特殊场景下对已提交文字的判断错误 | ||
|
||
## Feat | ||
- 升级 `tower-lsp` 到 `0.19.0` 版本以支持 LSP 3.17.0 | ||
- 支持 LSP 3.17.0 的 `label_details` 特性,用于显示每一个候选项的 comment | ||
- 默认选中第一个候选项 | ||
|
||
# v0.2.1 | ||
|
||
## Breaking Changes | ||
- 启动时不再自动更新用户词频,改为完全手动操作 | ||
|
||
## Fix | ||
- 修复了因状态判断出错导致的删除输入后同一位置无法继续输入的问题 | ||
- 修复了进入「方案选单」后必须选择才能退出的问题 | ||
|
||
# v0.2.0 | ||
|
||
## Breaking Changes | ||
- 配置项 `max_candidates` 不再生效,改为遵从 Rime 配置的每页候选项个数 | ||
|
||
## Feat | ||
- 与 Rime 的 API 保持同步,不再是只获取候选项 | ||
- 支持将通过数字选择的候选项提交给 Rime,从而影响用户词频 | ||
- 支持长句子的分多次选择 | ||
- 支持 Rime 的「方案选单」功能 | ||
- 可能有理论上的性能提升 (不再每次打字都创建 session,未验证效果) | ||
|
||
# v0.1.3 | ||
|
||
## Fix | ||
- 更好的错误处理 | ||
- 修复了几处从 rust 传指针给 C 时的典型内存泄漏 | ||
|
||
## Feat | ||
- 配置项的路径现在支持展开波浪线 `~` 为家目录 | ||
- 支持通过 TCP 远程使用 (明文传输,不安全,需要配合加密的 TCP 信道) | ||
- 可能有理论上的性能提升 (未验证) | ||
|
||
# v0.1.2 | ||
|
||
## Breaking Changes | ||
- `execute_command` 所支持的命令的名称都增加了 `rime-ls.` 的前缀 | ||
|
||
## Fix | ||
- 修复了因更新位置在边界处导致的 LSP server 不能同步更新文档内容的问题 | ||
|
||
## Feat | ||
- 现在可以通过命令手动触发用户目录同步 | ||
- 执行 `rime-ls.toggle-rime` 命令后会返回执行后的当前状态 | ||
|
||
# v0.1.1 | ||
|
||
## Fix | ||
- 全局模式下,补全时会删掉拼音前未提交的标点符号 | ||
|
||
## Feat | ||
- 触发模式下,光标前有非英文字符时可以自动触发补全继续输入 | ||
|
||
# v0.1.0 | ||
|
||
第一个基本可用版本 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters