From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: alex.branham@gmail.com, 30990@debbugs.gnu.org
Subject: bug#30990: Should the byte compiler warn about :type mismatches?
Date: Sat, 28 Sep 2019 22:21:55 +0300 [thread overview]
Message-ID: <838sq8grak.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkX10O5AkX418LASg+LZVb2ZgHart3zEmz3VDzTcbttCw@mail.gmail.com> (message from Stefan Kangas on Sat, 28 Sep 2019 21:00:22 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 28 Sep 2019 21:00:22 +0200
> Cc: Alex Branham <alex.branham@gmail.com>, 30990@debbugs.gnu.org
>
> The following options might have problems:
> sql-password-wallet
> tramp-default-host-alist
> display-fill-column-indicator-character
> bibtex-string-file-path
> js-jsx-indent-level
> bibtex-file-path
> sql-use-indent-support
> sql-postgres-login-params
> winner-boring-buffers-regexp
> add-log-dont-create-changelog-file
> nnir-notmuch-filter-group-names-function
> flymake-cc-command
>
> Since we're getting closer to the release of Emacs 27.1, perhaps we
> should sort these out.
We should, but bugs like this can be fixed even after the emacs-27
branch is cut.
next prev parent reply other threads:[~2019-09-28 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 16:55 bug#30990: Should the byte compiler warn about :type mismatches? Alex Branham
2018-03-29 17:11 ` Glenn Morris
2020-09-25 12:44 ` Lars Ingebrigtsen
2019-09-28 19:00 ` Stefan Kangas
2019-09-28 19:21 ` Eli Zaretskii [this message]
2019-09-30 11:49 ` Robert Pluim
2019-09-30 15:45 ` Lars Ingebrigtsen
2019-10-09 13:34 ` Robert Pluim
2019-10-09 17:57 ` Lars Ingebrigtsen
2019-10-09 20:05 ` Lars Ingebrigtsen
2019-10-10 13:11 ` Robert Pluim
2019-10-11 5:54 ` Lars Ingebrigtsen
2020-09-25 13:18 ` Lars Ingebrigtsen
2020-09-25 13:36 ` Lars Ingebrigtsen
2020-09-25 13:43 ` Lars Ingebrigtsen
2019-10-09 18:44 ` Mattias Engdegård
2019-10-11 9:31 ` Robert Pluim
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=838sq8grak.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30990@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=stefan@marxist.se \
/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.