Re: Need help with eldoc:

["T.V Raman" <raman@google.com>]

thanks for reaching out and replying!

So let me step back and explain what I want and I'm sure you'll know
the answer.

I use and maintain emacspeak (https://emacspeak.sf.net --- code is on
github under https://github.com/tvraman/emacspeak

Eldoc is extremely useful to the blind software engineer, perhaps even
more so than to someone who can glance at the docs in another
window. But eldoc spopping up and speaking based on an idel timer is
suboptimal.

So what I had implemented a few years ago was:

1. Turn off global eldoc mode.

   2. Advice the eldoc-message machinery to cache the displayed
      message somewhre
      3. Added an interactive command that spoke that cached value

         Result: a blind user could avoid the constant interruption
         from eldoc but ask for the documentation when needed with a
         single keystroke.

         Your explanation around how async updates works now explains
         my older solution broke, and   I was naively trying to call
         what seemed to the closest equivalent which was clearly
         wrong.

         So to cut to the chase; could you provide me a simple
         mechanism that I could call from emacspeak (via a keybinding
         bound to an interactive command I write) where that command
         calls into the eldoc machinery and gets back the help that
         eldoc displays?

         

João Távora writes:
 > >
 > > Could the current maintainer of eldoc give some pointers on what might
 > >    be breaking?
 > >
 > 
 > Hello Raman,
 > 
 > I'm not formally the maintainer of Eldoc (I think) but I have worked on it
 > recently (read more than one year ago).  The changes I introduced make it
 > so that the documentation-generating functions in
 > eldoc-documentation-functions
 > (plural!) can now be asynchronous (i.e. not return doc results immediately).
 > 
 > eldoc-documentation-default should not be called directly from elisp
 > libraries other
 > than eldoc.el itself, which handles this possible asynchronicity.  It is a
 > function value to
 > be put into eldoc-documentation-function which is then called by the
 > eldoc.el machinery
 > (such as M-x eldoc) that gives it context.
 > 
 > So can you tell me what are you trying to accomplish?  Maybe I can help.
 > 
 > João

-- 

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  🦮