[Feature] 运行日志缓冲淘汰会把用户正在查看的历史日志刷掉，需要快照/固顶能力
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- desktop
Research direction
Start by inspecting run.store.ts, especially MAXIMUM_OUTPUT_CHARACTERS, and trace how the Editor displays and searches buffered output on Windows. Compare the proposed snapshot/read-only copy and adjustable buffer approaches, then define the UI/UX entry point and acceptance behavior for preserving logs while new output continues. Done should include a documented, testable way to keep viewed historical output available.
Written by the indexing model from the issue text.
Description
Problem to solve / 要解决的问题
环境（Windows v0.5.3+，Java 服务持续输出）；现象（关闭“滚动到末尾”查看旧行时，输出超过 50 万字符环形上限后该行被淘汰，位置 run.store.ts 的 MAXIMUM_OUTPUT_CHARACTERS）；期望（查看中的历史日志可长期保留）；
Proposed solution / 建议方案
①右键菜单「快照当前输出」（冻结只读副本+可搜索）②设置可调缓冲上限，二者互补；备选：行固定（成本高）。标签 UI/UX + Windows（+ 跨平台的话加 macOS）。
Target platform / 目标平台
windows
Area / 模块
Editor / 编辑器
Priority / 优先级
P0 / 立即处理：已严重影响使用体验，核心流程受阻或无法正常使用
Alternatives considered / 已考虑的替代方案
No response
Additional context / 补充信息
No response
Checklist / 提交前检查
- I searched existing issues for duplicates. / 我已搜索现有 Issue，确认没有重复建议。
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 151
- Avg merge
- 7h 51m
- Merged PRs (30d)
- 351
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 1lck/Lithe-IDEA
-
area:editor bug P0 platform:macos review: low
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
1lck/Lithe-IDEA#1118 · 2 comments ·
Maintainers usually reply within 1 day
-
area:editor issue-form:feature P1 platform:windows review: low
Difficulty 3/5 1-2 days Newbie friendliness 52/100
1lck/Lithe-IDEA#1129 ·
Maintainers usually reply within 1 day
-
area:editor issue-form:feature P1 platform:windows review: low
Difficulty 4/5 3-5 days Newbie friendliness 48/100
1lck/Lithe-IDEA#1128 ·
Maintainers usually reply within 1 day
-
[Feature] 修复commit区按钮、弹窗、下拉框样式Possibly taken @arkleselect claimed this today. Openarea:ui enhancement issue-form:feature P1 platform:macos review: medium
1lck/Lithe-IDEA#1125 · 1 assignee ·
Maintainers usually reply within 1 day
-
[Bug] Windows 版本对比重复显示相同内容Possibly taken @puppyben1 claimed this today. Openarea:git bug P0 platform:windows review: low
Difficulty 3/5 1-2 days Newbie friendliness 38/100
1lck/Lithe-IDEA#1123 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
answerLoops/answerLoops#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
siyuan-note/siyuan#20313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LanternOps/breeze#8254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
gofish-graphics/gofish-graphics#1084 ·
Maintainers usually reply within 1 day