Chunk that does not produce any output generates two empty lines in LaTeX output

[krlmlr]

The following minimal.Rnw input file

\documentclass{article}
\begin{document}
a
<<q,echo=FALSE,results='hide'>>=
getwd()
@
b
\end{document}

generates on output (using R --no-save <<<"library(knitr); knit('minimal.Rnw')" in a bash shell)

% ... header stripped for brevity
\begin{document}
a


b
\end{document}

That's two empty lines too much for my understanding. Sweave used to leave out these empty lines.

Is this a bug or a (hopefully configurable) feature?

[krlmlr]

There's a workaround that consists of defining a command that gobbles all following empty lines:

http://tex.stackexchange.com/questions/55914/command-that-gobbles-all-following-empty-lines

[yihui]

I do not know if this is a bug, and unfortunately this is not configurable. Why do you want to remove the two empty lines? Because it makes a and b separate paragraphs?

[krlmlr]

Exactly. If I want to back up a written sentence in a report with an R assertion, I want to keep both next to each other.

[yihui]

Fair enough. Can you move the chunk before a or after b? Since you do not want to output anything from the chunk, moving it might not hurt.

[krlmlr]

Yes, I could, but I prefer keeping code and text as close as possible to each other. For now, I use a TeX macro that gobbles all following empty lines to achieve what I want, see the link in one of my former comments.

[yihui]

The main reason that I do not want to change this is due to the concordance feature. It requires a little bit more careful thinking; I will think about it later.

[yihui]

I decided not to change this. Sorry.

[krlmlr]

No problem, I'm fine with the workaround. You might want to list this behavior (and a hint how to work around it) in your documentation somewhere. Please feel free to use the code in the TeX.SX answer.

[yihui]

Thanks!

[github-actions]

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.