unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Peder O. Klingenberg" <pok@netfonds.no>
Cc: "Charles A. Roelli" <charles@aurox.ch>, 27230@debbugs.gnu.org
Subject: bug#27230: eldoc doc
Date: Thu, 14 Sep 2017 15:02:11 +0300	[thread overview]
Message-ID: <1f39b877-4cbf-96d8-a318-7edf95f10406@yandex.ru> (raw)
In-Reply-To: <ksy3pha4ds.fsf@luna.netfonds.no>

On 9/14/17 2:47 PM, Peder O. Klingenberg wrote:

> As I discovered today, when I updated my tree, there are callers outside
> emacs core that do call eldoc-message with more than one argument.
> slime-autodoc.el is one such package, which I use.

Thanks for letting us know.

> The slime project has an open issue on this, with a patch, but it hasn't
> been applied yet, after sitting in the discussion for 17 days.

I've commented on it: https://github.com/slime/slime/issues/400

For one thing, third-party packages should *not* use eldoc-message.

> IMO commit 7ef0b5f611c2d56ac2edb8de287190f04c4b8f32 was an ill-advised
> change.  The code worked fine before, the cleanup afforded by breaking
> the api was negligible.  I think it should be reverted.

Aside from breaking the "obviously wrong" callers like explained above, 
the code had a subtle bug where calling it with no format arguments, and 
then with some arguments, wouldn't update the message area.

> (Slime would benefit from cleaing up their callers as well, no doubt,
> but not every slime user should be forced to do that on their own.

Of course, the project maintainers should do it.

All the best,
Dmitry.





  reply	other threads:[~2017-09-14 12:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 10:38 bug#27230: eldoc doc Charles A. Roelli
2017-06-05 22:08 ` Dmitry Gutov
2017-06-06 18:33   ` Charles A. Roelli
2017-06-06 20:19     ` Dmitry Gutov
2017-06-25  9:14       ` Charles A. Roelli
2017-06-25 14:26         ` Eli Zaretskii
2017-06-25 19:47           ` Charles A. Roelli
2017-06-26  1:04             ` Dmitry Gutov
2017-06-27 19:51               ` Charles A. Roelli
2017-06-27 23:50                 ` Dmitry Gutov
2017-06-28 19:16                   ` Charles A. Roelli
2017-07-22  8:11                     ` Eli Zaretskii
2017-09-14 11:47               ` Peder O. Klingenberg
2017-09-14 12:02                 ` Dmitry Gutov [this message]
2017-09-14 19:39                   ` Charles A. Roelli
2017-09-14 22:03                     ` Dmitry Gutov
2017-09-19 20:02                       ` Charles A. Roelli
2017-09-20 18:12                         ` Charles A. Roelli
2017-09-21 14:23                           ` Dmitry Gutov
2017-09-21 18:33                             ` Charles A. Roelli
2017-09-21 23:05                               ` Dmitry Gutov
2017-09-25 23:26                               ` Dmitry Gutov

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=1f39b877-4cbf-96d8-a318-7edf95f10406@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=27230@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=pok@netfonds.no \
    /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).