Bug when converting into Latex
Closed this issue · 11 comments
Please see the screen recording
2022-02-24.19-19-03.mp4
Do you know where is this \differentialID
coming from?
I don't know. I just typed the equation in and have no idea why \differentialID
popped up. Could you reproduce the bug?
Unfortunately I am not able to. Is this the only bug?
If you type "t t" into the mathlive box, does your theme change as well?
"t t" causes changing between dark and light theme
That's interesting. Do you mind sharing the whole list of plugins that you currently have installed?
Unfortunately, I am not able to reproduce the bug! Will continue to keep it open as at least one other person is experiencing this.
Strange indeed! 🤔
As I started using the plugin more it's bugging me quite a bit.
The bug seems to be that it registers the keystrokes as if I'm not in editing mode. For example:
If I press c
it put a letter "c" in the Math Editor but will also bring up the Git commit pop up.
t t
will switch light/dark theme
t i
will bring up the changing theme pop up.
and so on with t p
, g j
, etc.
(I think I and another user who had this problem before all use Windows, and I know you use Mac so you may not see this bug ha ha)
@nhan000 Hey thanks for reporting this. Yes, Yuval from the Discord experienced the exact same issue as well. Unfortunately, even the Logseq devs are not able to reproduce this bug. I've had other users on Windows (as well as using my Windows VM) and still not able to do so!
As mentioned above, will keep this open just in case a solution pops up.
Just found out that the bug is from the source https://cortexjs.io/mathlive/demo/. Input the same equation
Good news is the bug of pressing t t
and t i
or any other Logseq shortcuts no longer trigger Logseq's commands.
Just found out that the bug is from the source https://cortexjs.io/mathlive/demo/. Input the same equation dNdt=RA and got the same bug. The weird thing is IIRC, the bug wasn't there when I used it a year ago (but again it was year ago so my memory may not be accurate). I want to file a bug report with them but I don't know where to do that. I'm on Logseq 0.9.2 on Windows 11.
Good news is the bug of pressing
t t
andt i
or any other Logseq shortcuts no longer trigger Logseq's commands.
Apologies, fixed in the latest version.