We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to reproduce:
First, create a simple test.tex file with content
test.tex
\documentclass{article} \begin{document} Here is math: $x^2$. \end{document}
M-x xenops-mode
$x^2$
However, the following works as expected
M-x xenops-mode RET
M-x font-lock-update RET
Step 3 can be replaced with many alternatives that indirectly will cause the buffer to be refontified, e.g., saving, editing, etc.
As far as I can tell, this is because during activation, xenops-mode adds some font-lock keywords that should trigger rendering on cursor moving using cursor-sensor-mode, but it doesn't actually cause these new font-lock keywords to be "applied."
xenops-mode
cursor-sensor-mode
I imagine this can be fixed by explicitly calling font-lock-fontify-buffer when mode is activated.
font-lock-fontify-buffer
This is easy enough to work around, but it caused a lot of confusion for me when I followed the tutorial, which at one point suggests that the user open a file, turn on xenops-mode, move the cursor in and out of math, and see a render result.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Steps to reproduce:
First, create a simple
test.tex
file with contenttest.tex
M-x xenops-mode
$x^2$
However, the following works as expected
test.tex
M-x xenops-mode RET
M-x font-lock-update RET
$x^2$
Step 3 can be replaced with many alternatives that indirectly will cause the buffer to be refontified, e.g., saving, editing, etc.
As far as I can tell, this is because during activation,
xenops-mode
adds some font-lock keywords that should trigger rendering on cursor moving usingcursor-sensor-mode
, but it doesn't actually cause these new font-lock keywords to be "applied."I imagine this can be fixed by explicitly calling
font-lock-fontify-buffer
when mode is activated.This is easy enough to work around, but it caused a lot of confusion for me when I followed the tutorial, which at one point suggests that the user open a file, turn on
xenops-mode
, move the cursor in and out of math, and see a render result.The text was updated successfully, but these errors were encountered: