From: Felician Nemeth <felician.nemeth@gmail.com>
To: 42532@debbugs.gnu.org
Cc: "João Távora" <joaotavora@gmail.com>
Subject: bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive?
Date: Sat, 25 Jul 2020 20:17:34 +0200 [thread overview]
Message-ID: <87mu3nihmp.fsf@betli.tmit.bme.hu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
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.
[-- Attachment #2: bug.el --]
[-- Type: #("application/emacs-lisp" 0 22 (face iswitchb-current-match)), Size: 624 bytes --]
(defvar my-asdf-asdf-sdf-asdf-asdf-asdf-asdf-sdf-asdf-asdf-asdf-asdfasdf-asdf-sdf-asdf-asdf-asdf-asdfasdf-asdf 1
"START asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf asdf END")
(switch-to-buffer-other-window "*eldoc*")
(window-resize (get-buffer-window) (- window-min-height (window-height)))
(other-window 1)
(find-file "bug.el")
(goto-char 14)
(setq eldoc-prefer-doc-buffer t)
(setq eldoc-documentation-functions '(elisp-eldoc-var-docstring elisp-eldoc-funcall t))
next reply other threads:[~2020-07-25 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 18:17 Felician Nemeth [this message]
2020-09-07 8:38 ` bug#42532: 28.0.50; Can eldoc-prefer-doc-buffer be more aggressive? 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
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=87mu3nihmp.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=42532@debbugs.gnu.org \
--cc=joaotavora@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).