Lorenz Walthert

Here's all we need to know going forward: https://github.com/yihui/knitr/issues/2112

Right. This was by design because of the following: * in most workflows, it's highly unlikely that you style the same input twice. Because after styling, your output will be...

I see. Let's leave this in a branch for now until we collected further experience with it. Making it optional increases the complexity for the maintainers and users again so...

Hi @IndrajeetPatil. After looking at the product (help file), I decided that I don't actually think it's a good idea to document these functions in the same file. Here's why:...

If you want, you could change this PR to harmonizing the sections in the different help files, but I can also understand if you don't feel like it anymore 😒

ok, thanks @IndrajeetPatil for being kind with me.

@IndrajeetPatil I invited you to be a collaborator of {styler}. We are happy to have you and look forward to your next contributions. I plan to reduce my engagement with...

I do see there is a lot of duplication. Mostly kn the user side though. At source, there is very little due to inheritance and smart use of roxygen. I...

I am happy to keep it if on a separate line. Cn you file a PR?

Let me know how I can help. Most likely the diff for #714 is a good starting point.