Re: Control characters in doc strings

["Alfred M. Szmidt" <ams@gnu.org>]

   What about these?

   progmodes/verilog-mode.el:12424:2: Warning: docstring contains control char #x0c (position 2845)
   progmodes/verilog-mode.el:12875:2: Warning: docstring contains control char #x0c (position 1187)

I'd think it is fair to consider this specific usage "just wrong;
don't do it" -- if you narrow to a page you will get something that is
not correct and will screw Lisp indentation and all kind of things!

\f
;;; Auto creation:
;;

(defun verilog-auto-arg-ports (sigs message indent-pt)
  "Print a list of ports for AUTOARG.
Takes SIGS list, adds MESSAGE to front and inserts each at INDENT-PT."
[...])

(defun verilog-auto-arg ()
  "Expand AUTOARG statements.
Replace the argument declarations at the beginning of the
module with ones automatically derived from input and output
statements.  This can be dangerous if the module is instantiated
using position-based connections, so use only name-based when
instantiating the resulting module.  Long lines are split based
on the `fill-column', see \\[set-fill-column].

[...]
\f
Where the list of inputs and outputs came from the inst module.
\f
For more information see the \\[verilog-faq] and forums at URL
`https://www.veripool.org'."
  (save-excursion
[...]))