-
Notifications
You must be signed in to change notification settings - Fork 5
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
Spacing in math mode of the new release #11
Comments
The code was not changed in that area and both versions should render that snippet in the same way. If you happen to still have the older version installed, you can maybe check that (otherwise, do not bother reinstalling it). I suspect something got corrupted in your user's preference folder, in which case deleting the folder in C:\Users\yourusername\AppData\Roaming\TeXmacs should revert to normal spacings. If you have customized your setup (with e.g. shortcuts, macros, etc) rename the folder instead of deleting it, for recovering your customized files. Let me know if that solves the issue. |
I tried deleting the folder but still have the issue. I use custom styles and keyboard shortcuts but I don't think I changed anything relevant. Guess I'll just use the previous release then. |
Okay. That's already strange because I can't reproduce your issue when typing that equation in the new version, with a blank user profile. |
I did some testing and see some really strange behavior. It seems that my style files are not relevant at all.
At this point, the equation looks normal. Then we close the file. |
Ah yes, I can reproduce it now, thanks. Indeed, the problem arises in the new version when loading saved files. I'll have to bissect to find when the problem was introduced; it may take some time... |
I've determined the bug started at SVN rev. 13970, and it's related to the content of the |
Hi, I just updated to the newest release. I found that the spacing between symbols with an invisible multiplication
*
is too small.Old version:
New version:
The text was updated successfully, but these errors were encountered: