You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is presumably an error somewhere in my bibliography, since I get Uncaught Token mismatch, expected }, found . This error isn't very informative, since it doesn't include a location and what is found is apparently the empty string.
Ah, figured it out. I had copied a bibliography entry with word wrap off, which gave
@article{silver2017alphazero,
title={Mastering Chess and Shogi by Self-Play with a General Reinforcement Learning Algorithm},
author={Silver, David and Hubert, Thomas and Schrittwieser, Julian and Antonoglou, Ioannis and Lai, Matthew and Guez
journal={arXiv preprint arXiv:1712.01815},
year={2017}
}
The author line was missing a closing }. There are two ways this experience could be improved:
If what is found is EOF, say that instead of found .
In general, give location information in error messages.
Not sure if these are easy to do with the current parsing mechanism.
The text was updated successfully, but these errors were encountered:
There is presumably an error somewhere in my bibliography, since I get
Uncaught Token mismatch, expected }, found
. This error isn't very informative, since it doesn't include a location and what is found is apparently the empty string.Ah, figured it out. I had copied a bibliography entry with word wrap off, which gave
The
author
line was missing a closing}
. There are two ways this experience could be improved:found
.Not sure if these are easy to do with the current parsing mechanism.
The text was updated successfully, but these errors were encountered: