-
Notifications
You must be signed in to change notification settings - Fork 204
Issue with palette for latex referencing #414
Comments
Update - this problem, I think, is at the latex-tool side. I tried couple of other themes, and similar things happen. So, I have opened the issue there. I will update this thread once there is more info. Thanks! |
There have been many changes in Atom |
I have a similar problem and opened this issue |
@silvestreh - a clarification. This issue is persisting only in material theme. I tried reproducing this issue in other themes, and they are working as expected. |
I have the same issue as @werunom. Encountered it both in atom 1.16 and 1.17. With both versions it's only happening in material theme. Definitely not reproducible with other themes, I'm afraid. |
Any updates on this? This is still present in atom 1.24.1 with atom-material-ui 2.1.3 and indeed seems to be an issue with atom-material-ui, see #430. It works just fine with other themes. I really like this theme but I'm afraid it's unusable for me if this bug remains... |
Okay, I guess I was wrong... I found that there are two classes that cause this issue: <atom-panel class="modal overlay from-top">
<div class="select-list overlay from-top label-view" is="space-pen-div"> The classes So this is probably something they changed in one of their updates. I'll go ahead and create an issue for the latexer package. And if this remains for your packages you should create one there too :) |
Updated to 1.17 and also installed the latest update of material-ui theme. After this update, the dropdown palette for atom-latextools package is not working fine. Basically, when I am doing a referencing in latex, the latextools package automatically opens a palette containing relevant reference-keys. After installing these updates, the palette is not working fine.
Other palettes - for ctr+sht+p and ctr+p - are working as expected. I have checked this scenario in other UI-themes and there the reference palette is working fine.
The text was updated successfully, but these errors were encountered: