unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 42777@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#42777: 28.0.50; Obsolete eldoc-message function used in CEDET
Date: Sun, 30 Aug 2020 15:46:51 +0200	[thread overview]
Message-ID: <87wo1gs0tw.fsf@gnus.org> (raw)
In-Reply-To: <87sgc69zaz.fsf@gmail.com> ("João Távora"'s message of "Fri, 28 Aug 2020 23:32:36 +0100")

João Távora <joaotavora@gmail.com> writes:

>>> In semantic-idle-summary-refresh-echo-area:
>>> cedet/semantic/idle.el:802:13: Warning: ‘eldoc-message’ is an obsolete
>>>     function (as of eldoc-1.1.0); use
>>> ‘eldoc-documentation-functions’ instead.
>>>
>>> I guess this is the result of João's changes in July?  I had a quick
>>> peek at how to fix it, but it wasn't immediately obvious to me.
>>
>> Copying in João Távora in the hope that the fix will be immediately
>> obvious to him.
>
> Lars, you want to fix the compilation warning or something else?  The
> function is obsolete, but it leep working.  The only "fix" is to follow
> the advice in the warning message.

If the function is obsolete, all in-tree callers should be fixed.  I'm
not familiar enough with eldoc to do so, though.

> I don't know why this particular compilation warning didn't pop up
> earlier, I don't recall it.

It's been there ever since you obsoleted eldoc-message, of course.  :-)

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





  reply	other threads:[~2020-08-30 13:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 15:23 bug#42777: 28.0.50; Obsolete eldoc-message function used in CEDET Lars Ingebrigtsen
2020-08-28 17:55 ` Stefan Kangas
2020-08-28 22:32   ` João Távora
2020-08-30 13:46     ` Lars Ingebrigtsen [this message]
2020-08-30 13:54       ` João Távora
2020-08-30 13:58         ` Lars Ingebrigtsen
2020-08-30 14:10           ` João Távora
2020-08-30 14:23           ` João Távora
2020-08-30 14:56             ` Stefan Kangas
2020-08-30 15:46             ` Lars Ingebrigtsen
2020-08-30 16:00               ` João Távora
2020-08-30 16:01                 ` Lars Ingebrigtsen
2020-08-30 19:22                   ` João Távora
2020-09-01 14:14                     ` Lars Ingebrigtsen
2020-09-01 18:22                       ` João Távora
2020-09-01 18:57                         ` Stefan Kangas
2020-09-01 23:43                           ` João Távora
2020-09-02 13:38                             ` Lars Ingebrigtsen
2020-09-02 18:46                               ` João Távora
2020-09-04  2:23                                 ` Lars Ingebrigtsen
2021-07-06 15:21                                   ` Lars Ingebrigtsen
2020-08-30 14:27           ` Eli Zaretskii

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=87wo1gs0tw.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=42777@debbugs.gnu.org \
    --cc=joaotavora@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 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).