unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 49007@debbugs.gnu.org
Subject: bug#49007: 28.0.50; "docstring wider than 80" misfire
Date: Sun, 13 Jun 2021 13:47:27 -0400	[thread overview]
Message-ID: <jwvsg1ly7v4.fsf@iro.umontreal.ca> (raw)

Package: Emacs
Version: 28.0.50


Byte-compiling the declaration below complains that

    defalias `rudel-connect' docstring wider than 80 characters

even though it stays within the 80 columns limit.


        Stefan


(cl-defgeneric rudel-connect ((this rudel-protocol-backend) transport
			      info info-callback
			      &optional progress-callback)
  "Create a new connection through TRANSPORT according to the data in INFO.
TRANSPORT has to be an object of a class derived from `rudel-transport'.
INFO has to be a property list.
INFO-CALLBACK has to be a function of two arguments which will be
bound to THIS and INFO.  When called, INFO-CALLBACK should return
a modified version of the INFO argument in which no information
is missing.
When non-nil, PROGRESS-CALLBACK has to be a function that may be
called repeatedly while the connection is established.

Implementations can rely on the fact that the property :session
in INFO contains the `rudel-session' object to which the new
connection will be associated.")






             reply	other threads:[~2021-06-13 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 17:47 Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-06-14 13:47 ` bug#49007: 28.0.50; "docstring wider than 80" misfire Lars Ingebrigtsen
2021-06-14 14:47   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-15 13:34     ` Lars Ingebrigtsen
2021-06-15 15:54       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvsg1ly7v4.fsf@iro.umontreal.ca \
    --to=bug-gnu-emacs@gnu.org \
    --cc=49007@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).