all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Po Lu <luangruo@yahoo.com>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	"T.V Raman" <raman@google.com>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	emacs-devel@gnu.org
Subject: Re: How to disable warnings about single quotes in emacs-29
Date: Wed, 08 Jun 2022 05:12:44 +0000	[thread overview]
Message-ID: <8735gfpwdo.fsf@posteo.net> (raw)
In-Reply-To: <87ilpbsqsj.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]


Po Lu <luangruo@yahoo.com> writes:

> Phil Sainty <psainty@orcon.net.nz> writes:
>
>> I expect you could argue it both ways.
>>
>> `checkdoc' says its purpose is to "check the entire buffer for style
>> errors", but IMO the \\=' issue is more a "bug" than a "style error"
>> (as it will typically be about documented lisp code).
>>
>> I do think such bugs are far more likely to be addressed if they're
>> produced by the byte-compiler, so to me it doesn't seem like a bad
>> thing unless it's prone to false-positives (in which case compilation
>> warnings would be pretty frustrating).
>
> checkdoc was eventually supposed to be integrated into the
> byte-compiler, I think.  Errors in doc strings are not fatal to the
> program either, so I'd call them "style errors".

Checkdoc is nice, but it would be too much work to fix such warnings
with checkdoc one buffer after the other (48 buffers), I had to use a
function that do it all at once without asking.

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  reply	other threads:[~2022-06-08  5:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  7:01 How to disable warnings about single quotes in emacs-29 Thierry Volpiatto
2022-06-07  8:45 ` Philip Kaludercic
2022-06-07  8:48   ` Thierry Volpiatto
2022-06-07  9:12 ` Lars Ingebrigtsen
2022-06-07  9:33   ` Thierry Volpiatto
2022-06-07  9:45     ` Lars Ingebrigtsen
2022-06-07 10:35       ` Thierry Volpiatto
2022-06-07 10:47         ` Lars Ingebrigtsen
2022-06-07 11:06           ` Thierry Volpiatto
2022-06-07 11:31             ` Lars Ingebrigtsen
2022-06-07 12:20               ` Thierry Volpiatto
2022-06-07 17:50                 ` Lars Ingebrigtsen
2022-06-07 18:30                   ` Thierry Volpiatto
2022-06-07 18:49                     ` Stefan Monnier
2022-06-07 19:42                   ` T.V Raman
2022-06-08  0:32                     ` Phil Sainty
2022-06-08  1:14                       ` Po Lu
2022-06-08  3:28                         ` Phil Sainty
2022-06-08  4:49                           ` Po Lu
2022-06-08  5:12                             ` Thierry Volpiatto [this message]
2022-06-08  9:44                               ` Michael Heerdegen
2022-06-08 11:57                             ` Lars Ingebrigtsen
2022-06-08 12:39                               ` Po Lu
2022-06-08 12:52                                 ` Lars Ingebrigtsen
2022-06-08 12:55                                   ` Po Lu
2022-06-08 11:53                     ` Lars Ingebrigtsen
2022-06-07 12:30         ` Stefan Monnier
2022-06-07 14:28           ` Kaushal Modi
2022-06-07 15:06             ` Thierry Volpiatto
2022-06-07 15:08           ` Thierry Volpiatto

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=8735gfpwdo.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=psainty@orcon.net.nz \
    --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.