On Fri, Aug 30, 2013 at 5:28 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
> Fixed.
Confirmed.
Scott
Scott Kostyshak wrote:
> A bisect suggests this commit introduced the behavior:
>
> commit 84971fb27ebd9f178a0147b06fa195e49cd75797
> Author: Jürgen Spitzmüller
> Date: Fri Mar 9 09:05:13 2012 +
Fixed.
Jürgen
On Sat, Aug 24, 2013 at 4:48 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
>> This problem does not happen for me on 2.0.x.
>> This happens for me on master since at least 1 May 2012. I have
>> trouble compiling earlier versions (no CMake and Automake version
>> issues).
>
> Same here. M
Scott Kostyshak wrote:
> This problem does not happen for me on 2.0.x.
> This happens for me on master since at least 1 May 2012. I have
> trouble compiling earlier versions (no CMake and Automake version
> issues).
Same here. Maybe someone with an older automake version can help bisecting.
Jürg
On Mon, Jul 22, 2013 at 4:29 PM, Scott Kostyshak wrote:
> See the attached MWE. It should be compilable on master (with platex
> via dvipdfmx). Now remove the space after the period, that is, after
> the string <>. If you have the Source Pane open, you should
> see the following warning appear:
>
See the attached MWE. It should be compilable on master (with platex
via dvipdfmx). Now remove the space after the period, that is, after
the string <>. If you have the Source Pane open, you should
see the following warning appear:
Because of this, the document is no longer compilable.
This pr
