GNU bug report logs - #50839
28.0.50; Odd things in comp-ctxt doc string

Previous Next

Full log

Message #13 received at control <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, 50839 <at> debbugs.gnu.org
Cc: Andrea Corallo <akrl <at> sdf.org>
Subject: Re: bug#50839: 28.0.50; Odd things in comp-ctxt doc string
Date: Mon, 27 Sep 2021 02:51:09 -0700

tags 50839 fixed
close 50839 28.1
thanks

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> But looking at the actual help buffer, I get the stuff below.
>>
>> It looks like bits of the doc strings have been replaced with...  odd
>> things?  "lambdas" is now "lamcomp-func.dbdas".  And also the
>> "byte-funCL-X.ction" thing.  I haven't debugged any further; perhaps
>> it's obvious to someone what's going on.  (I've added Andrea to the CCs.)
>
> Oh, and this started happening after Stefan K's long-doc-string warning
> enablement in lambda, so perhaps it's related to that (or perhaps that
> just makes the problem more obvious).  (So I've added him to the CCs, too.)

Thanks, this is now fixed on master in commit 3d2d7e8ea2.

This was caused by trying to fill an entire paragraph as if it were a
single line.  Here, I really wish we could use `cl-assert' in subr.el,
to do something like this in `internal--format-docstring-line':

    (cl-assert (not (string-match "\n" string)))

Do we have anything like that, or do we just do something like this
instead?

    (and (string-match "\n" string)
         (error "Contains newline: %s" string))

Maybe this is okay as this should pretty much only be called from
macros?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.