From: "T.V Raman" <raman@google.com>
To: joaotavora@gmail.com
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: Need help with eldoc:
Date: Thu, 24 Mar 2022 19:21:32 -0700 [thread overview]
Message-ID: <25149.10028.97873.940861@google.com> (raw)
In-Reply-To: <87ee2qevjs.fsf@gmail.com>
So this was very easy to get working, I'd like you to take a look.
I discovered custom option
'(eldoc-echo-area-prefer-doc-buffer t)
--- this i good for the emacspeak user who can see a little since
they can look at the buffer -- and it doesn't disturb or distract the
totally blind user.
I then went ahead and implemented the function as you suggested -- see
https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-advice.el
-- search for "eldoc" to jump to the relevant portion.
I'd like some feedback for the following:
0. I cloned your display in a buffer function
1. changed it to use with-temp-buffer
3. rendered the doc there and asked it to speak it.
4. if called non-interactively I just play a short sound to say
something is available
5. And then bound eldoc to a key
This all works, but it could well be simpler now that the above
works.
If I could be ensured of the eldoc always being in a buffer I could
eliminate most of the above, but I am also afraid that that will
recreate the earlier async problem which is why I didn't go there.
So modulo not yet having figured out the empty doc-string case, this
works well for me for now.
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-03-25 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:21 Need help with eldoc: T.V Raman
2022-03-24 23:28 ` João Távora
2022-03-24 23:39 ` T.V Raman
2022-03-25 0:16 ` João Távora
2022-03-25 2:21 ` T.V Raman [this message]
2022-03-25 10:03 ` João Távora
2022-03-25 14:03 ` T.V Raman
2022-03-25 22:52 ` João Távora
2022-03-25 14:27 ` T.V Raman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25149.10028.97873.940861@google.com \
--to=raman@google.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.