unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: check-parens
Date: Wed, 04 Sep 2019 01:19:24 +1000	[thread overview]
Message-ID: <m2ftld9zlv.fsf@wakeman.localnet> (raw)
In-Reply-To: jwvtv9tfr2y.fsf-monnier+emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> the following snippet errors:
>>
>> (member CHAR (list ?r ?))
>
> Of course, a paren is missing.
>
>> but check-parens doesn't signal it.
>
> Indeed, but the byte-compiler does:
>
>     foo.el:5:1:Warning: unescaped character literals `?)' detected,
>         `?\)' expected!
>
>> Worth a bug-report?
>
> Probably not: it's a known problem.

Would be nice for the cgit/emacs.git webpage to have a section listing
vintage bugs and bugs on low hanging fruit with notes collected from
visitors.

-- 
© 2019 VanL
gpg using EEF2 37E9 3840 0D5D 9183  251E 9830 384E 9683 B835
          'If the bug bites don't fight it.' - Nancy S. Steinhardt




  reply	other threads:[~2019-09-03 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  6:55 check-parens Andreas Röhler
2019-09-03 13:32 ` check-parens Stefan Monnier
2019-09-03 15:19   ` VanL [this message]
2019-09-03 18:19     ` check-parens Stefan Kangas
2019-09-03 16:58   ` check-parens Michael Heerdegen

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=m2ftld9zlv.fsf@wakeman.localnet \
    --to=van@scratch.space \
    --cc=help-gnu-emacs@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.
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).