unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 63310@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#63310: 29.0.90; Blacklisting docstrings and docstrings-non-ascii-quotes from byte-compile-warnings do not prevent all docstring warnings
Date: Sat, 06 May 2023 12:36:19 +0300	[thread overview]
Message-ID: <83a5yhhkdo.fsf@gnu.org> (raw)
In-Reply-To: <m28re2yfyv.fsf@MobileCat.localdomain> (message from Jimmy Yuen Ho Wong on Fri, 05 May 2023 16:07:20 +0100)

> From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
> Date: Fri, 05 May 2023 16:07:20 +0100
> 
> 
> Reproduction:
> 
> 1. `(custom-set-variables '(byte-compile-warnings '(not docstrings
> docstrings-non-ascii-quotes)))`
> 2. M-x package-install RET move-dup
> 3. M-x package-install RET monky
> 4. Observe in the *Compile-Log* buffer the `custom-declare-variable
> ... docstring has wrong usage of unescaped single quotes (use \= or different quoting)` and `docstring wider than ... characters` mesages
> 
> Expectation:
> 
> Blacklisting docstrings and docstrings-non-ascii-quotes should not result
> in any docstring warnings being emitted during byte compilation.

I don't see any warnings when compiling the latest version of
move-dup.

As for monkey: it explicitly sets the value of byte-compile-warnings
in file-local variables:

  ;; Local Variables:
  ;; byte-compile-warnings: (not cl-functions)
  ;; End:

So this overrides your customization when byte-compiling this file.

I see no bug here.





  reply	other threads:[~2023-05-06  9:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 15:07 bug#63310: 29.0.90; Blacklisting docstrings and docstrings-non-ascii-quotes from byte-compile-warnings do not prevent all docstring warnings Jimmy Yuen Ho Wong
2023-05-06  9:36 ` Eli Zaretskii [this message]
2023-05-06 16:39   ` Jimmy Yuen Ho Wong
2023-05-06 16:55     ` Eli Zaretskii
2023-05-13 14:03       ` Eli Zaretskii
2023-05-06 18:41     ` 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=83a5yhhkdo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63310@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=wyuenho@gmail.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 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).