all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Antoine Kalmbach <ane@iki.fi>, Phil Sainty <psainty@orcon.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: docstring has wrong usage of unescaped single quotes (use \= or different quoting)
Date: Fri, 22 Jul 2022 15:12:14 +0100	[thread overview]
Message-ID: <87mtd1nsn5.fsf@gmail.com> (raw)
In-Reply-To: <lybkth49d3.fsf@iki.fi> (Antoine Kalmbach's message of "Fri, 22 Jul 2022 15:31:20 +0300")

Antoine Kalmbach <ane@iki.fi> writes:

> I believe the syntax to get a docstring to show "Blah blah 'foo" to show
> correctly you'd have to write "Blah blah \\='foo".

Thanks Phil and Antoine, I'll try that.

> Interestingly, such errors are not reported by checkdoc, but as you
> mentioned, byte-compilation reports them.

Yep.  Maybe the idea is to be more "aggressive" so that these docstring
issues are addressed sooner.  That's because more people run the byte
compiler than run checkdoc (which is extremely picky and has lots of
"false positives").  So I think I can understand that this is a good
intention.

But, IMHO, introducing such a new warning that has little to do with
byte-compilation is a drag on people working with existing packages and
looking for byte-compilation issues.  Maybe there is a flag to turn off
or demote this warning, and maybe that flag could be used in
elisp-flymake-byte-compile.

João

PS: I'm with the non-fancy/ASCII quote crowd, but I don't oppose
allowing or recommending such fancy quotes in docstrings.  I just don't
want that to hinder my normal workflow when maintaining old packages.



  reply	other threads:[~2022-07-22 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 10:24 docstring has wrong usage of unescaped single quotes (use \= or different quoting) João Távora
2022-07-22 12:27 ` Phil Sainty
2022-07-22 12:31 ` Antoine Kalmbach
2022-07-22 14:12   ` João Távora [this message]
2022-07-22 14:38     ` Lars Ingebrigtsen
2022-07-22 15:23       ` João Távora
2022-07-22 20:08         ` Lars Ingebrigtsen

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=87mtd1nsn5.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=ane@iki.fi \
    --cc=emacs-devel@gnu.org \
    --cc=psainty@orcon.net.nz \
    /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.