unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	 "T.V Raman" <raman@google.com>,
	Thierry Volpiatto <thievol@posteo.net>,
	 emacs-devel@gnu.org
Subject: Re: How to disable warnings about single quotes in emacs-29
Date: Wed, 08 Jun 2022 14:52:18 +0200	[thread overview]
Message-ID: <87bkv39v25.fsf@gnus.org> (raw)
In-Reply-To: <87sfofqqh5.fsf@yahoo.com> (Po Lu's message of "Wed, 08 Jun 2022 20:39:18 +0800")

Po Lu <luangruo@yahoo.com> writes:

> But the byte compiler compiles Emacs Lisp, not doc strings.

The byte compiler compiles .el files, and the doc strings are part of
that.

> I think we should move everything related to doc string markup into
> checkdoc, and then resolve the TODO about integrating that with the
> byte compiler, perhaps by adding a new warning type `checkdoc' for
> warnings from checkdoc.

Checkdoc is about stylistic issues, which is something else than this
warning.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-06-08 12:52 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
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 [this message]
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

  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=87bkv39v25.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=psainty@orcon.net.nz \
    --cc=raman@google.com \
    --cc=thievol@posteo.net \
    /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).