On 05/05/2020 10:30 a.m., Martin Maechler wrote:
Matthew Young
on Mon, 4 May 2020 09:09:55 + writes:
> I progressively chopped bits out of the vignette till the
> error stopped to identify the error. It was being caused
> by inline latex, where I had two %% marks. I'm
> Matthew Young
> on Mon, 4 May 2020 09:09:55 + writes:
> I progressively chopped bits out of the vignette till the
> error stopped to identify the error. It was being caused
> by inline latex, where I had two %% marks. I'm not really
> sure why this broke
I progressively chopped bits out of the vignette till the error stopped to
identify the error. It was being caused by inline latex, where I had two %%
marks. I'm not really sure why this broke things, but removing it fixed it.
Thanks,
Matthew
On 02/05/2020, 16:54, "Uwe Ligges" wrote:
My wild guess is that 'r ' indicates there is an invisible char after
the r that is not representable in the chosen encoding.
Best,
Uwe Ligges
On 02.05.2020 01:12, Matthew Young wrote:
I’ve tried both ways (with and without a space after the backtick) and get the
same error.
From: Max
I’ve tried both ways (with and without a space after the backtick) and get the
same error.
From: Max Turgeon
Date: Friday, 1 May 2020 at 20:39
To: Matthew Young , "r-package-devel@r-project.org"
Subject: Re: Rmarkdown vignette yields r inline warning on windows build [EXT]
Since you're
