[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings
From: |
Jimmy Yuen Ho Wong |
Subject: |
bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings |
Date: |
Fri, 05 May 2023 12:51:47 +0100 |
`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.
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings,
Jimmy Yuen Ho Wong <=
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Eli Zaretskii, 2023/05/05
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Jimmy Yuen Ho Wong, 2023/05/06
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Andrea Corallo, 2023/05/10
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Jimmy Wong, 2023/05/14
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Andrea Corallo, 2023/05/17
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Eli Zaretskii, 2023/05/17
- bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Andrea Corallo, 2023/05/17
bug#63302: 29.0.90; Native comp does not respect byte-compile-warnings, Andrea Corallo, 2023/05/10