RE: doc strings that are too long

[Drew Adams]

That produces an OK result, but the filling would need to be done by each
function that displays the doc string.

Since that could include user-defined functions, it would be better if the
filling were done before adding the doc string as the function, variable,
etc. property.

I'm not familiar with how (fn...) works, however. Is it feasible to do this
ahead of time, and store the resulting (filled) doc string?

 - Drew


    -----Original Message-----
    From: John Paul Wallington [mailto:address@hidden
    Sent: Monday, November 21, 2005 11:44 AM
    To: Drew Adams
    Cc: address@hidden
    Subject: Re: doc strings that are too long


    "Drew Adams" <address@hidden> writes:

    > In other cases, such as quail-define-package, the (fn ...) at
    the end is
    > just too wide (232 columns wide! in the case of quail-define-package)

    In those cases how about just filling the arglist ?  That seems to
    give okay results.

    2005-11-21  John Paul Wallington  <address@hidden>

        * help-fns.el (describe-function-1): Fill arglist.

    --- help-fns.el     31 Oct 2005 17:06:00 +0000      1.79
    +++ help-fns.el     21 Nov 2005 19:39:16 +0000
    @@ -436,7 +436,9 @@
                              (format "\nMacro: %s" (format-kbd-macro def)))
                             (t "[Missing arglist.  Please make a
    bug report.]")))
                      (high (help-highlight-arguments use doc)))
    -            (insert (car high) "\n")
    +            (let ((fill-begin (point)))
    +         (insert (car high) "\n")
    +         (fill-region fill-begin (point)))
                 (setq doc (cdr high))))
             (let ((obsolete (and
                              ;; function might be a lambda construct.