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>
Cc: Yuan Fu <casouri@gmail.com>, 42532@debbugs.gnu.org
Subject: bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive?
Date: Sat, 03 Oct 2020 20:18:59 +0100	[thread overview]
Message-ID: <87y2knglss.fsf@gmail.com> (raw)
In-Reply-To: <87imc08zkf.fsf@betli.tmit.bme.hu> (Felician Nemeth's message of "Sat, 26 Sep 2020 14:58:24 +0200")

Felician Nemeth <felician.nemeth@gmail.com> writes:

> For example, with the attached file, moving the point right after "emacs
> -Q --load ./bug.el" displays the truncated documentation in the echo
> area, but it shouldn't.

Hello Felicián,

I pushed an alternate version of this patch to the branch
scratch/eldoc-display-functions

To git.sv.gnu.org:/srv/git/emacs.git
 * [new branch]            scratch/eldoc-display-functions -> scratch/eldoc-display-functions

It contains more than just this patch, but notably it passes your test,
I think.  Can you try it out?  A point of mention is that the value `t'
is now what `aggressive' used to be.  This is more straightfoward and
much simplified  docstring writing the docstring.  If you want the old
"only prefer if truncated" behaviour, set it to `maybe' (maybe that name
can be reviewed).

Best regards,
João






  reply	other threads:[~2020-10-03 19:18 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
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 [this message]
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=87y2knglss.fsf@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).