Arya McCarthy

On mobile, the magnifying glass of the search bar gets forced to the next row for me.

Is the BibTeX generation handling special characters properly? This entry has weird quotation marks in the abstract. This one has weird things going on in the title field.

> > Is the BibTeX generation handling special characters properly? > > Fixed by [[6bbc5a1](https://github.com/acl-org/acl-anthology/commit/6bbc5a1f4f35744f609f384e866a95bf6cc8f021)] I'm seeing "CoNLL–SIGMORPHON" in macOS Safari, instead of "CoNLL–SIGMORPHON". Does the build script need to...

Unclear whether this is a parsing error or a data error: [this BibTeX](http://aclweb.org/anthology/papers/D/D13/D13-1088.bib) has no article title.

Another question of is-it-the-data-or-the-site: SIGMORPHON has workshops listed [through 2014](http://aclweb.org/anthology/sigs/sigmorphon/), but one of the 2014 ones is really 2016: W16-20. On top, [their 2018 workshop](http://aclweb.org/anthology/events/ws-2018/#w18-58) isn't listed on their page.

Hi, @hackebrot! Thanks for writing. Yes, that's the one I'm referring to. [This StackOverflow discussion](http://stackoverflow.com/questions/8976452/h-in-python) explains that simply importing the `readline` package alters how `input()` works. I have sloppy fingers,...

Hmm. Is there a `click`-compatible way to improve this functionality?

Perhaps `DEFINE_path` can happen by these holidays? :-)

Bumping because this is super useful.

I agree that supporting the `# gazelle:default_visibility` directive would be ideal. (I mentioned that in #1681.) Until that's implemented (and I would have to learn Go to do it), this...