unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42777@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#42777: 28.0.50; Obsolete eldoc-message function used in CEDET
Date: Tue, 01 Sep 2020 19:22:19 +0100	[thread overview]
Message-ID: <87zh69pdb8.fsf@gmail.com> (raw)
In-Reply-To: <87wo1dd1p3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 01 Sep 2020 16:14:00 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:
> João Távora <joaotavora@gmail.com> writes:
>
>> That's true.  But look, the real underlying problem we have in our code
>> that there is code in CEDET's idle.el that needlessly duplicates and
>> uses implementation detail of the ElDoc infrastructure.  The real fix to
>> this bug is _integration_, and integration is hard and takes time. 
> Indeed.  And meanwhile the warning should stay.

We agree then.

>> In parallel, in my opinion, there is little point in having 0 warnings
>> globally.  Maybe that is the policy in the Emacs repo, but in my opinion
>> I'd rather investigate "positive deltas" in warning count.
>
> No, that's not the policy, as far as I know: Warnings stay in until the
> problem is fixed, one way or another.

That's my view as well.  So what's missing perhaps is that we close this
bug and open another bug, as was Stefan Kangas' suggestion, to track the
integration work.  WDYT?  Or maybe we should just leave this bug as that
record, since it's where all the investigation done so far is
registered anyway.

Joãp





  reply	other threads:[~2020-09-01 18:22 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
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 [this message]
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=87zh69pdb8.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=42777@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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).