Marius Barth

I also just tried to reproduce and with the provided code, a pdf is knitted that looks just as expected. I tried both with a system installation of Texlive and...

Last time we discussed this matter, we concluded that, at the moment, it is the best solution to add a note regarding the return value, which is what I did...

I've just pushed a draft on branch `add-custom-effect-sizes`. I ran into some obstacles that need further consideration. However, first the good news: I considerably "flattened" our ANOVA processing: I could...

Moving forward with integrating the **effectsize** package, I think it will be the best solution to delegate calculating estimates together with confidence intervals to a specialized function in all possible...

Hi @crsh, I also think that this will be a bigger change that will require some additional thought. However, maybe we could create an additional branch (from the `devel` branch)...

With the newest version of **arm** (1.12-2), we do not depend on **Hmisc** and its imports, anymore :tada:

That's what I also had in mind. Unfortunately, it seems like the `.bib` file with references to R packages is created in a way that is not easily moved to...

Hi @Misch007, model-comparison objects of class `anova` are indeed not supported. However, objects of class `mixed` which are the output of `mixed()` are supported. If you are only testing for...

Hi @Misch007, unfortunately, this is a case where the workaround won't work: You basically compare a model with two main effects and an interaction term with a more complex model...

As can be seen [here](https://stackoverflow.com/questions/68528857/gtsummary-and-papaja-integration-for-kable-tables), adding ``` options(knitr.table.format = 'pipe') ``` to the *setup* chunk allows using {gtsummary} tables in a {papaja} document. Would we have to expect undesired side...