From: "T.V Raman via Emacspeak" <emacspeak@emacspeak.org>
To: joaotavora@gmail.com
Cc: raman@google.com, emacs-devel@gnu.org, emacspeak@emacspeak.org
Subject: Re: eldoc errors in elisp
Date: Sat, 22 Apr 2023 11:13:10 -0700 [thread overview]
Message-ID: <25668.9142.334606.870001@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <CALDnm52Qv-TGOaW6yxtF+v35UsUDurnaRGLtuakfu-7S8bqWgw@mail.gmail.com>
(Copying emacspeak list so it gets archived and found later)
Thanks for the offer to help, I'll take you up on it, see below.
Your guess is correct.
There are two goals for Emacspeak visavis Eldoc
1. If eldoc auto triggers a message, and if emacspeak were to speak it
in every case, it gets annoying fast and you cant do what you're
doing.
The advantage with visually showing the message is that the eye can
choose to ignore it; the ear cannot ignore something
spoken. Emacspeak tries to somewhat ameliorate this by speaking
notifications just on one ear, but it's still too much in the case
of eldoc.
2. Complementary requirement; you want to hear that message because
it does have helpful info; so you want it spoken "on demand".
Solution:
Emacspeak produces a very short auditory icon to
indicate that eldoc is available at point as you move through
the code; the experienced user can then hit a key and here it.
Here is the implementation; it's pretty short, and you might be
able to advice me (no defadvice pun intended)
See function emacspeak-speak-eldoc
at https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-advice.el#L801
--
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 🦮
_______________________________________________
Emacspeak mailing list -- emacspeak@emacspeak.org
To unsubscribe send an email to emacspeak-leave@emacspeak.org
next prev parent reply other threads:[~2023-04-22 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 15:33 eldoc errors in elisp T.V Raman
2023-04-22 16:20 ` João Távora
2023-04-22 16:37 ` T.V Raman
2023-04-22 17:45 ` João Távora
2023-04-22 18:13 ` T.V Raman via Emacspeak [this message]
2023-04-22 21:25 ` João Távora
2023-04-23 2:43 ` T.V Raman via Emacspeak
2023-04-23 10:28 ` João Távora
2023-04-23 12:14 ` João Távora
2023-04-23 14:26 ` T.V Raman via Emacspeak
2023-04-23 14:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25668.9142.334606.870001@retriever.mtv.corp.google.com \
--to=emacspeak@emacspeak.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=raman@google.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.