From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: 63302@debbugs.gnu.org
Subject: bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings
Date: Fri, 05 May 2023 12:51:47 +0100 [thread overview]
Message-ID: <m28re3atd8.fsf@MobileCat.localdomain> (raw)
`byte-compile-warnings` is commonly set to to remove `docstring` so
spurious `docstring wider than 80 characters` are removed. When it is
set to such a way, normal byte compilation of a el file with a docstring
longer than 80 characters will not result in the above warning, but
natively compiling the same file will.
The expectation should be that nativecomp respects this variable at the
very least, or that the linting capabilities is moved out of byte
compilation into a seperate package ala elisp-lint. A compiler should
compile any program that is valid without producing any warnings except
obsolete/deprecations.
next reply other threads:[~2023-05-05 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 11:51 Jimmy Yuen Ho Wong [this message]
2023-05-05 13:22 ` bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings Eli Zaretskii
2023-05-06 16:52 ` Jimmy Yuen Ho Wong
2023-05-10 11:53 ` Andrea Corallo
2023-05-14 21:57 ` Jimmy Wong
2023-05-17 7:49 ` Andrea Corallo
2023-05-17 11:05 ` Eli Zaretskii
2023-05-17 13:14 ` Andrea Corallo
2023-05-10 9:57 ` Andrea Corallo
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=m28re3atd8.fsf@MobileCat.localdomain \
--to=wyuenho@gmail.com \
--cc=63302@debbugs.gnu.org \
/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).