all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org, Oleh Krehel <ohwoeowho@gmail.com>
Subject: Re: bytecomp: doc string wider than 80 spurious warnings are back
Date: Wed, 27 Sep 2023 04:22:16 -0700	[thread overview]
Message-ID: <CADwFkm=QjHOK_+SqhsAquw4KJ-++8MTBwpdsRbzgGtG2MAP6xg@mail.gmail.com> (raw)
In-Reply-To: <p915y3x3uhu.fsf@google.com>

"T.V Raman" <raman@google.com> writes:

> Here are some examples:
>
> Warning:
> emacspeak-muggles.el:327:2: Warning: docstring wider than 80 characters
> https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-muggles.el#L327
>
> Hope this helps.

Thanks, it does.

It seems like this is caused by the `defhydra' macro, which creates
defuns with overly long docstrings.  Thus, I don't think we can fix it
on our end, and this should be reported to the hydra maintainers
instead.  I've Cc:ed the hydra maintainer Oleh Krehel.



  reply	other threads:[~2023-09-27 11:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 23:11 bytecomp: doc string wider than 80 spurious warnings are back T.V Raman
2023-09-26  1:55 ` Stefan Kangas
2023-09-26 13:59   ` T.V Raman
2023-09-27 11:22     ` Stefan Kangas [this message]
2023-09-27 15:38       ` T.V Raman
2023-09-27 16:16         ` Emanuel Berg
2023-09-27 19:56           ` T.V Raman
2023-09-27 20:16             ` Emanuel Berg
2023-09-28  7:47             ` Stefan Kangas
2023-09-28 14:18               ` T.V Raman
2023-09-28 23:04                 ` Michael Heerdegen
2023-09-29  2:20                   ` T.V Raman
2023-09-29 13:52             ` Eli Zaretskii
2023-09-29 14:16               ` Stefan Kangas
2023-09-29 14:26                 ` T.V Raman
2023-09-29 16:06                   ` Emanuel Berg
2023-09-29 16:16                 ` Eli Zaretskii
2023-09-28  7:38         ` Stefan Kangas
2023-09-28 14:16           ` T.V Raman

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

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

  git send-email \
    --in-reply-to='CADwFkm=QjHOK_+SqhsAquw4KJ-++8MTBwpdsRbzgGtG2MAP6xg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ohwoeowho@gmail.com \
    --cc=raman@google.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.