Thank you for your answers.
Putting \if{html}{\eqn{}} before \mjeqn{}{} works!
Kind regards,
Marc
- Ursprüngliche Mail -
Von: "Viechtbauer, Wolfgang (SP)"
An: "Richard M. Heiberger" , "Marc Scherstjanoi"
CC: r-package-devel@r-project.org
Gesendet: Freitag, 25. Juni 2021 20:30:10
That doesn't seem to work for me (or I am not following this suggestion
properly). But putting \if{html}{\eqn{}} before \mjeqn{}{} does. A bit of a
hackish solution, but if it works, it works.
Not sure why \mjeqn{}{} at the beginning of a paragraph actually leads to a
line break, but it's yet
> One more question. If I use mjeqn at the beginning of a paragraph it
> automatically sets a line break afterwards.
> Any idea what I can do to prevent this?
follow it with
\vspace*{1ex}
to back up one line.
Rich
> On Jun 25, 2021, at 07:51, Marc Scherstjanoi
> wrote:
>
> Hi Wolfgang,
I'm back in civilization for a few days, and have submitted a PR to
Hmisc: https://github.com/harrelfe/Hmisc/pull/143 .
Duncan Murdoch
On 23/06/2021 8:51 a.m., Gilbert Ritschard wrote:
Thanks for this suggestion.
Pushing the investigation a bit further, I found that the error resulted in
Hello,
Thank You. It worked. The package has been submitted to CRAN. Thank You for
your helpful feedback.
On Tue, Jun 22, 2021 at 10:00 PM Oliver Madsen
wrote:
> The problem is solved by either
>
> 1) creating an environment variable within the package namespace (as you
> would a function)
Dirk and Duncan,
thanks. the slight nudge towards =R CMD INSTALL= is a helpful reminder,
and hewing close to the straight-and-narrow is undoubtedly a good thing.
cheers, Greg
__
R-package-devel@r-project.org mailing list
Hi Wolfgang,
thank you for this information.
I will try with \mjtdeqn and stick to the intended latex functions for building
the pdf.
Moreover, we will bring up the more complicated equations in a vignette pdf.
One more question. If I use mjeqn at the beginning of a paragraph it
automatically
On Thu, 24 Jun 2021, Greg Minshall writes:
> hi.
>
> when developing packages, my current work flow is to change the code,
> (re-)build the package, detach/load the package, test (to find the
> N+1'st bug, sigh).
>
> the building step takes tens of seconds.
>
> is there an obvious way to present
On 6/24/21 11:31 PM, Duncan Murdoch wrote:
On 24/06/2021 4:52 p.m., Dirk Eddelbuettel wrote:
On 24 June 2021 at 16:31, Duncan Murdoch wrote:
| This does the full compile again, so it's slow.
ccache fixes that (as it has its own cache). It also works on macOS.
I haven't tried ccache:
