From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive? Date: Mon, 7 Sep 2020 09:38:16 +0100 Message-ID: References: <87mu3nihmp.fsf@betli.tmit.bme.hu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000077332505aeb52421" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25468"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 42532@debbugs.gnu.org To: Felician Nemeth , Yuan Fu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 07 10:39:31 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 1kFCgU-0006VA-Io for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 07 Sep 2020 10:39:30 +0200 Original-Received: from localhost ([::1]:52590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kFCgT-0006ym-Ly for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 07 Sep 2020 04:39:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53444) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kFCg2-0006e0-Id for bug-gnu-emacs@gnu.org; Mon, 07 Sep 2020 04:39:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36471) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kFCg2-00067b-8l for bug-gnu-emacs@gnu.org; Mon, 07 Sep 2020 04:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kFCg2-0005D3-6c for bug-gnu-emacs@gnu.org; Mon, 07 Sep 2020 04:39:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 07 Sep 2020 08:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 42532 X-GNU-PR-Package: emacs Original-Received: via spool by 42532-submit@debbugs.gnu.org id=B42532.159946791419985 (code B ref 42532); Mon, 07 Sep 2020 08:39:02 +0000 Original-Received: (at 42532) by debbugs.gnu.org; 7 Sep 2020 08:38:34 +0000 Original-Received: from localhost ([127.0.0.1]:48017 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kFCfa-0005CH-DV for submit@debbugs.gnu.org; Mon, 07 Sep 2020 04:38:34 -0400 Original-Received: from mail-io1-f48.google.com ([209.85.166.48]:43730) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kFCfZ-0005C4-LL for 42532@debbugs.gnu.org; Mon, 07 Sep 2020 04:38:34 -0400 Original-Received: by mail-io1-f48.google.com with SMTP id z25so13170688iol.10 for <42532@debbugs.gnu.org>; Mon, 07 Sep 2020 01:38:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MSGE7MOKyF6goi5ZVVAComZ7lqYrzFAMWE+I2o+L+fE=; b=hz7T4pZBsyeNhr7HGRlvJA0W/3x6MuezHhMxd9ow3fdPRrV3y/6uqnzrkKVGjBwh4H 95q7YvjjkvWY0UQA0kLoP2Hg7vBRJ70H/KQNHfXJ4XQ41sWKlxp6mYFCFVpeZJ75Y0y9 dnJ/SS7NlmGYEOIrmoblYJPSO65IyTHOUSb9pSr7nZYwKaBUZIur7sjEXkTlIG9RB6z/ V60ZdtKYVYIAAB4HT6kufdHtd26Gi5v5J6ZclKY1G9IFmxhptlRbJ09gk0/7ExOfSdxu IGihF8V2elYN/pxKRJ+rfaggNeZCwCO8iqBPb9I/7l3x8L1MKe8fpIaK5Z9roz3UpFg8 GSIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MSGE7MOKyF6goi5ZVVAComZ7lqYrzFAMWE+I2o+L+fE=; b=MyUbF+yrIr/MulU9vxTNg3awNTEv73Ka9rNmBGR7c1iNvlfhe5c9k1ip4poopkFAdn h6DpRk/TEbw9Bl9CRmfoKYHyLkDQv5FTR0DcuvFm8LS2XyHEEH2HcbmC5jhu+vOJU4AQ u0VYLQnIa1GCVASR/A/KtI2uDS77cVl4r1IwoWNmV/OhbKt7YuXCb+oY5FLoceTqwIyr Ux0TXOakhNR6b02GGlEIv8NUUBMWxVRhMvOIzH1vbYp286Kugih8EjJcxtpjPBLtFNiN s3fyBe1cUAlpaf8ewUpeSkzex+SSiy51rm57NHpnQh9ghm2OMJ4pjMI6z9jwq2LaHaLD p6zQ== X-Gm-Message-State: AOAM530L7OT3eLwbVO5wqgQ+3b7ca8qHL85jw9AtXxh5TjhtBabacMms ViHf0xtbmXEkrisq2dPtih9Ri4D/NKVoPCTv12c= X-Google-Smtp-Source: ABdhPJybobGMK3ifxtPt6ukNztwt7Y67LtFAP5VJZIuSuLr8RhUilhpXFuFvXluIXXZ8wwFPFlDwfFO6D4GKfRWAUKI= X-Received: by 2002:a6b:7c0d:: with SMTP id m13mr16400331iok.57.1599467907656; Mon, 07 Sep 2020 01:38:27 -0700 (PDT) In-Reply-To: <87mu3nihmp.fsf@betli.tmit.bme.hu> 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:187414 Archived-At: --00000000000077332505aeb52421 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Felician, Sorry for the late reply. I'm working, and am very close to publishing, the promised introduction of eldoc-display-functions to help users (and third-party devs) better control the display of eldoc documentation. Regardless, I think it's reasonable to add a third possible value for eldoc-prefer-doc-buffer (which should really be renamed eldoc-echo-area-prefer-doc-buffer). The value could be the symbol 'aggressive or 'aggressively. Then it would behave as you propose: if the ElDoc doc buffer is showing, the echo area display code is a noop. What do you think? Jo=C3=A3o On Sat, Jul 25, 2020 at 7:18 PM Felician Nemeth wrote: > With the attached file, start emacs as: > > emacs -Q --load bug.el > > and then move the point left or right. Originally I started to write > this file as demonstration to bug#42421, but you fixed the bug faster > than I could find time to finish it. Now, I think everything works as > documented, but with the help of this recipe, I'd like to argue that > eldoc-prefer-doc-buffer is a bit annoying in this case. Its > documentation says: > > Prefer ElDoc=E2=80=99s documentation buffer if it is showing in some f= rame. > If this variable=E2=80=99s value is t and a piece of documentation nee= ds to > be truncated to fit in the echo area, do so if ElDoc=E2=80=99s documen= tation > buffer is not already showing, since the buffer always holds the full > documentation. > > I think it would be better to show the documentation only in the *eldoc* > buffer and not in the echo area even if the documentation doesn't need > to be truncated but the echo are needs to be resized to display the full > documentation. > > (bug.el changes eldoc-documentation-function to circumvent bug#42531, > which I reported few minutes ago, but changing the order of the hooks in > eldoc--eval-expression-setup, doesn't seem to fix bug#42531) > > Thank you, Jo=C3=A3o, for your work on eldoc. > > --=20 Jo=C3=A3o T=C3=A1vora --00000000000077332505aeb52421 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Felician,

Sorry for the l= ate reply. I'm working, and am very close to publishing,
the = promised introduction of eldoc-display-functions to help users (and
third-party devs) better control the display of eldoc documentation.

Regardless, I think it's reasonable to add a thir= d possible value
for eldoc-prefer-doc-buffer (which should r= eally be renamed
eldoc-echo-area-prefer-doc-buffer).=C2=A0 T= he value could be the symbol
'aggressive or 'aggressively= .=C2=A0 Then it would behave as you propose:
if the ElDoc doc buf= fer is showing, the echo area display code is
a noop.
<= div>
What do you think?

Jo=C3=A3o

On Sat, Jul 25, 2020 at 7:18 PM Felician Nemeth <felician.nemeth@gmail.com> wrote:
With the attached fil= e, start emacs as:

=C2=A0 emacs -Q --load bug.el

and then move the point left or right.=C2=A0 Originally I started to write<= br> this file as demonstration to bug#42421, but you fixed the bug faster
than I could find time to finish it.=C2=A0 Now, I think everything works as=
documented, but with the help of this recipe, I'd like to argue that eldoc-prefer-doc-buffer is a bit annoying in this case.=C2=A0 Its
documentation says:

=C2=A0 =C2=A0Prefer ElDoc=E2=80=99s documentation buffer if it is showing i= n some frame.
=C2=A0 =C2=A0If this variable=E2=80=99s value is t and a piece of documenta= tion needs to
=C2=A0 =C2=A0be truncated to fit in the echo area, do so if ElDoc=E2=80=99s= documentation
=C2=A0 =C2=A0buffer is not already showing, since the buffer always holds t= he full
=C2=A0 =C2=A0documentation.

I think it would be better to show the documentation only in the *eldoc* buffer and not in the echo area even if the documentation doesn't need<= br> to be truncated but the echo are needs to be resized to display the full documentation.

(bug.el changes eldoc-documentation-function to circumvent bug#42531,
which I reported few minutes ago, but changing the order of the hooks in eldoc--eval-expression-setup, doesn't seem to fix bug#42531)

Thank you, Jo=C3=A3o, for your work on eldoc.



--
Jo=C3=A3o T=C3=A1vora
--00000000000077332505aeb52421--