-
Notifications
You must be signed in to change notification settings - Fork 110
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
Font of "Tools output" tab #550
Comments
An option to set tools output panel font would be useful, but not much. Most of time we just check compile warnings and errors in the compiler info panel, and seldom need to align the text in the tools output panel. As for the encoding problem, it seems that there's something wrong in the compiler detection procedure. What's the the output of gcc -v? |
In this case, it is an opportunity to get additional information about errors.
Using built-in specs. |
The encoding problem: There are no good ways to read a stream in mixed encodings. The file names and error messages are much more important, while file content can be easily located in editor window. So Red Panda C++ decodes it with GCC's ACP. I believe it won't be a problem in near future. Since GCC 13, UTF-8 manifest is applied by default, and diagnostic messages are purely UTF-8. After switching to mingw-lite GCC 14, everything will work well. |
The "Tools output" tab (txtToolsOutput widget) requires a monospaced font to position compiler errors correctly.
Otherwise, it turns out like this:
And it should be like this:
If I change to the monospaced font of the entire application, the tab font changes and the offset problem disappears. Maybe it is better to synchronize the font of this tab with the monospaced font of the editor?
PS: In addition, there is clearly a problem with encodings. Probably, it is a matter of converting from editor encoding (UTF-8) to executable file encoding (CP866), and the opposite conversion is needed when outputting compiler messages.
PS2: As it turned out, the problem is not in the reverse translation of the encoding, but in the fact that the contents of the tab contain the correct text in UTF-8 encoding, but it is displayed as CP1251 (System default codepage). This is how "Привет" turned out to be "Привет"
The text was updated successfully, but these errors were encountered: