unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Felician Nemeth <felician.nemeth@gmail.com>, Yuan Fu <casouri@gmail.com>
Cc: 42532@debbugs.gnu.org
Subject: bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive?
Date: Mon, 7 Sep 2020 09:38:16 +0100	[thread overview]
Message-ID: <CALDnm51UYaypggCRNWNPd8VAG9Fm4Xvb-mLmW-MMbPtFn=XkVg@mail.gmail.com> (raw)
In-Reply-To: <87mu3nihmp.fsf@betli.tmit.bme.hu>

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

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ão

On Sat, Jul 25, 2020 at 7:18 PM Felician Nemeth <felician.nemeth@gmail.com>
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’s documentation buffer if it is showing in some frame.
>    If this variable’s value is t and a piece of documentation needs to
>    be truncated to fit in the echo area, do so if ElDoc’s documentation
>    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ão, for your work on eldoc.
>
>

-- 
João Távora

[-- Attachment #2: Type: text/html, Size: 2647 bytes --]

  reply	other threads:[~2020-09-07  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 18:17 bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive? Felician Nemeth
2020-09-07  8:38 ` João Távora [this message]
2020-09-07 10:11   ` João Távora
2020-09-26 12:58     ` Felician Nemeth
2020-10-03 19:18       ` João Távora
2021-01-15 18:00         ` Felician Nemeth
2021-01-15 18:01           ` João Távora

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='CALDnm51UYaypggCRNWNPd8VAG9Fm4Xvb-mLmW-MMbPtFn=XkVg@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=42532@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=felician.nemeth@gmail.com \
    /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).