Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

将控制台的消息日志保存到文件里 #1844

Closed
NoMathExpectation opened this issue Jan 21, 2022 · 5 comments · Fixed by #1874
Closed

将控制台的消息日志保存到文件里 #1844

NoMathExpectation opened this issue Jan 21, 2022 · 5 comments · Fixed by #1874
Labels
N 优先级: 一般 s:console 子系统: mirai-console t:enhancement 类型: 现有功能上的优化 t:problem 类型: 不容易归类为特性或 bug 的综合问题
Milestone

Comments

@NoMathExpectation
Copy link
Contributor

翻Mirai console的文件夹并没有看见控制台的消息日志,只有一个好像和网络有关的日志。希望能把控制台的日志也写进文件里,这样遇到紧急的bug需要立即关闭机器人,也可以之后看文件里的日志,分析发生了什么问题了

@NoMathExpectation NoMathExpectation added the t:feature 类型: 新特性 label Jan 21, 2022
@Karlatemp Karlatemp added N 优先级: 一般 s:console 子系统: mirai-console t:problem 类型: 不容易归类为特性或 bug 的综合问题 t:enhancement 类型: 现有功能上的优化 labels Jan 21, 2022
@Him188 Him188 removed the t:feature 类型: 新特性 label Jan 21, 2022
@Him188 Him188 added this to the Backlog milestone Jan 21, 2022
@Karlatemp Karlatemp modified the milestones: Backlog, 2.11 Feb 6, 2022
@Him188 Him188 modified the milestones: 2.11, 2.11.0-RC Feb 10, 2022
@Him188 Him188 modified the milestones: 2.11.0-RC, 2.11.0-M1 Mar 8, 2022
@NoMathExpectation
Copy link
Contributor Author

我把版本更新了,还是没看到什么日志文件啊,放在哪里了

@Him188
Copy link
Member

Him188 commented Mar 10, 2022

@NoMathExpectation logs/log-0.log

@NoMathExpectation
Copy link
Contributor Author

为什么会有乱码呢
image

@Him188
Copy link
Member

Him188 commented Mar 10, 2022

那是颜色控制符

@NoMathExpectation
Copy link
Contributor Author

emmm感觉可以写进文件时把这些控制符什么的过滤掉,美观一些

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
N 优先级: 一般 s:console 子系统: mirai-console t:enhancement 类型: 现有功能上的优化 t:problem 类型: 不容易归类为特性或 bug 的综合问题
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants