unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: The Warnings Beat
Date: Wed, 24 Feb 2021 18:06:46 +0100	[thread overview]
Message-ID: <871rd575uh.fsf@gnus.org> (raw)

After having a clean build for a while, we've had some persistent
warnings that would be nice to have fixed, because it takes time and
effort to reverify that we haven't broken something new.

So here's a list of warnings in the current build:

I think this one is kinda new?

Some part of "/home/larsi/src/emacs/trunk/lisp/leim/quail/indian.el" is broken


So is this one:

Not registering prefix "in" from generic-x.  Affects: ("inf-generic-mode" "ini-generic-mode" "ini-generic-mode-find-file-hook" "inetd-conf-generic-mode")
Not registering prefix "re" from generic-x.  Affects: ("reg-generic-mode" "resolve-conf-generic-mode")


This is due to Eldoc changing its interface:

In semantic-idle-summary-idle-function:
cedet/semantic/idle.el:758:10: Warning: `eldoc-message' is an obsolete
    function (as of eldoc-1.1.0); use `eldoc-documentation-functions' instead.
In semantic-idle-summary-refresh-echo-area:
cedet/semantic/idle.el:789:13: Warning: `eldoc-message' is an obsolete
    function (as of eldoc-1.1.0); use `eldoc-documentation-functions' instead.


And this one has been with us for long time, but only shows up on some
builds:

Grammar in python.el contains 4 shift/reduce conflicts

It normally shows up in "make -j1" builds, but not in "-j16" builds, but
I haven't chased it down any further.

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




             reply	other threads:[~2021-02-24 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 17:06 Lars Ingebrigtsen [this message]
2021-02-24 17:13 ` The Warnings Beat Lars Ingebrigtsen
2021-02-24 17:29 ` Lars Ingebrigtsen
2021-02-24 18:55   ` Stefan Monnier

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=871rd575uh.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@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.
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).