From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#43609: 28.0.50; eldoc-documentation-function [vs new eldoc-display-functions] Date: Tue, 27 Oct 2020 19:05:37 +0100 Message-ID: <64831acc-996e-51d7-ce6f-b667a6334e3c@gmx.at> References: <2e610c3f-6e5f-c7dd-af2e-aeb5e20d8664@gmx.at> <87r1qjjppu.fsf@gmail.com> <3fa6b315-7fc0-06ee-81e9-b68d164aec1b@gmx.at> <87a6x7jf9a.fsf@gmail.com> <874knbi0jc.fsf_-_@gmail.com> <87362tggvl.fsf@gmail.com> <87d01vem7z.fsf@gmail.com> <17da3e99-d4fc-a603-baa3-4180d612af41@gmx.at> <878scie5ti.fsf@gmail.com> <87tuujr6sd.fsf@gmail.com> <803c87c2-7d60-5997-2247-85d3e62e3d2c@gmx.at> <87a6w7puuz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3804"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , 43609@debbugs.gnu.org To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 27 19:06:52 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kXTMy-0000sW-1Q for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 27 Oct 2020 19:06:52 +0100 Original-Received: from localhost ([::1]:59216 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kXTMw-0004X5-SR for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 27 Oct 2020 14:06:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53378) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kXTMB-0004WU-1u for bug-gnu-emacs@gnu.org; Tue, 27 Oct 2020 14:06:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34201) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kXTMA-0000Jz-MW for bug-gnu-emacs@gnu.org; Tue, 27 Oct 2020 14:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kXTMA-0003KY-I0 for bug-gnu-emacs@gnu.org; Tue, 27 Oct 2020 14:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 27 Oct 2020 18:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43609 X-GNU-PR-Package: emacs Original-Received: via spool by 43609-submit@debbugs.gnu.org id=B43609.160382194612777 (code B ref 43609); Tue, 27 Oct 2020 18:06:02 +0000 Original-Received: (at 43609) by debbugs.gnu.org; 27 Oct 2020 18:05:46 +0000 Original-Received: from localhost ([127.0.0.1]:45747 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kXTLu-0003K1-DQ for submit@debbugs.gnu.org; Tue, 27 Oct 2020 14:05:46 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:55343) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kXTLt-0003Jm-49 for 43609@debbugs.gnu.org; Tue, 27 Oct 2020 14:05:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1603821938; bh=PLUWSVmXQ/ysTBaTbgA6j+MlsrYCAeGOrxJjANfVneo=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=LHj98u9DlQZeXdJDAkaW+nPNumSm72y3+6GxPxC2wuxYQw5zgjyfagjm5V63iGk7J XBuStbCU2vfaPR6Gb6YpEtqBYW3w0HT5odX/ewdSCMjPpzrmf/YlMzvdh7Z5LsxSA8 LJTZ1n/iykHMkG83Pl0G3rOFVF7S+P7o9qjkLEhY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.102] ([212.95.5.139]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MtOKc-1kFPKu2oL0-00upel; Tue, 27 Oct 2020 19:05:38 +0100 In-Reply-To: <87a6w7puuz.fsf@gmail.com> Content-Language: en-US X-Provags-ID: V03:K1:UNxRWrrxEBrYZhE4+n0GlPF6/iGa6hKP8DwDgu1if7QKhLZ+6ge bbZW78mefeJDQC7L47D9eHf3JGZlK/rUhEjVGPaCGGDr3KQhbt22K8Lro9yee1T/rcj26Hd M5JLKJFmYQRq0YHyxopia83FyxNp6Eh0ETskgC6tkWao37T3Oo2V6hJveZAQ+VDMji3i8vx 0nRDF0JlGXDJUuJUx6RKg== X-UI-Out-Filterresults: notjunk:1;V03:K0:j9jrfER/UDE=:p1IvK5U0ptvnUtTzJ2w/at d2lm0sKaBYFSm0rfrfr6LjSRlV0uIkpHJGSYIGEZhMqZRgRY1cH7AeT4uXspGoRbsI1TSL54A vrKj2SkLl/T7wWUmfJ3XAUwg2sRyRAKMCGQ1+CU718dkJXlS1uUanQ2iHfdEFw1r+jK+R0kh0 ItheS56iF/xtmXDLwTtiVdeV9RBYu2METUhJriQx7Se1RWRdd4Gz1nprw3pBAdPJotQznKftp xwtGba3zvHPT+aQ8K6IcULtl1K+pMV5IAoG032IYHzAvKoFvWZkWVVngctHktGMzQ1y3HptNY P8Ebwc614FDB8lg7nscoutW5iEADEpsjY/OfqRR7qB2Y4dpOomAZdcdsF9dy1GEBoPlhExOOv mH/neh+cAstlKCqMMuZU8tqe5w0y5qrIj+nCMw8YUclQroWa6a46GMPWmk+y2l/XioJDI5gpt TsUmkgJ2LUVrM+qTqF91Z1yxCsyy7a/RRqjTu2mt9eeQNr0T+F9mB+PcqxaqYkSYqGb6yq8+n BTNeLzKm0Xk2PvwgPsag+KBeHyBhmeHyIQ5nWfmWadXjQJe8ydl6lMi9X7FyfX//xfa+de8UJ ytCBWjXsQAjzK2MQv5mQt9hKrYj2A1U6RFdFV6Y8zJTq62xX+KjPDYX/cozmb6cTXGJGn570Y huVuCo/fAnqdDqNttWtj94abWvFJgtkEefWbupAj7/8DQPu4x0+m2xrbx2CJAi/JviXNDli0l N+CgZdzn2dPlxdYLsTNGSGPcRV81BblklT1KGOfmwztNrHRH9uKTC5KLs5lJfI/OKiiT76Ic X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:191754 Archived-At: > I'd like to help you, but I don't understand: are you updating Emacs t= o > master in all 50 of those drives? Do you do this 50 times? By hand? > Why can't you update your eldoc-tooltip.el in the process? Every year I experience around two or three crashes among my machines which run various operating systems ranging from Windows XP to Windows 10 and old stable to unstable Debian. When a HD drive crashes, I try to recreate the prior state by plugging in an older disk or copy the contents of that older disk into a new one. Thereafter, I usually update my Emacs repositories reusing my older libraries. If I also have to update my libraries, I'm ending up in Augean stables. > I don't understand how this can work: it's essential that ElDoc calls > eldoc-documentation-functions _through_ eldoc-documentation-function: > that's the only way it can deal with both old-style libraries that set= > the latter and new-style library that set the former. That's the key = to > backward compatibility, and it's working correctly for many old and ne= w > packages. Furthermore, this link between the two variables _precedes_= > my code (see SHA c0fcbd2c119b8418855f0931aceefbef717c5e53): I just add= ed > the async support. Then I fail to understand why my old code stopped working after your changes. On the version of master I'm currently using here it's even documented in the Elisp manual as =E2=80=98eldoc-documentation-function=E2=80=99 This variable holds the function which is used to retrieve documentation for the item at point from the functions in the hook =E2=80=98eldoc-documentation-functions=E2=80=99. By default, =E2=80=98eldoc-documentation-function=E2=80=99 returns the first do= cumentation string produced by the =E2=80=98eldoc-documentation-functions=E2=80= =99 hook. > If "function definitions" were at stake, I would certainly agree with > you. But they're not. Here 'elisp-eldoc-documentation-function' is a function defined in elisp-mode.el. IIUC this function has gone now. > If you are going to update Emacs to master in N servers, you might as > well update your library in those N servers. If you're updating it by > hand, then this doesn't seem like a tremendous extra effort to expend.= > If you're using a script, just put the library update in that script. = I > personally use Git to good effect for this: push once, pull many times= =2E This is not something I do once to be done for ever. It's something that I usually have to do in a troublesome situation where I have to recover from a previous crash and I'm trying to make some system run again. I can't afford to plug in all sorts of hard disk drives in order to make them future-proof. > Alternatively, and perhaps even better, you're invited to contribute > your library to Emacs (or GNU ELPA). Then you'll just have to update > Emacs, using your preferred method. I'd still have to update each of my .emacs and install the respective calls for each version of Emacs I might use there. martin