Mention writeLines() in ?print_linter (#2997)

Co-authored-by: Hugo Gruson <[email protected]>

Author: MichaelChirico

R/print_linter.R

@@ -2,9 +2,10 @@
 #'
 #' The default print method for character vectors is appropriate for interactively inspecting objects,
 #'   not for logging messages. Thus checked-in usage like `print(paste('Data has', nrow(DF), 'rows.'))`
-#'   is better served by using [cat()], e.g. `cat(sprintf('Data has %d rows.\n', nrow(DF)))` (noting that
-#'   using `cat()` entails supplying your own line returns, and that [glue::glue()] might be preferable
-#'   to [sprintf()] for constructing templated strings). Lastly, note that [message()] differs slightly
+#'   is better served by using [cat()], e.g. `cat(sprintf('Data has %d rows.\n', nrow(DF)))`. Note that
+#'   using `cat()` entails supplying your own line returns; [glue::glue()] might be preferable
+#'   to [sprintf()] for constructing templated strings. Alternatively, [writeLines()] can be used to
+#'   print character vectors with their own line returns. Lastly, note that [message()] differs slightly
 #'   from `cat()` in that it prints to `stderr` by default, not `stdout`, but is still a good option
 #'   to consider for logging purposes.
 #'