From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#6321: 24.0.50; eldoc-documentation-function only called when changing line
Date: Tue, 01 Jun 2010 14:29:20 +0200 [thread overview]
Message-ID: <87sk570wdb.fsf@tux.homenetwork> (raw)
In-Reply-To: <87aargw8uc.fsf@thinkpad.tsdh.de>
See also bug#6265 that is related or the same.
Štěpán Němec <stepnem@gmail.com> writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> In a home-brewn language mode, I use the eldoc facilties.
>>
>> (defun tg-documentation-function ()
>> (message "Called!")
>> (let ((thing (thing-at-point 'sexp)))
>> (if (string= thing tg--last-thing)
>> tg--last-doc
>> (setq tg--last-thing thing)
>> (let ((eid (tg-edge-p))
>> (vid (tg-vertex-p)))
>> (cond
>> ((tg-incidence-list-p)
>> (tg-eldoc-incidence))
>> (eid
>> (tg-eldoc-vertex-or-edge-at-point 'EdgeClass))
>> (vid
>> (tg-eldoc-vertex-or-edge-at-point 'VertexClass))
>> (t
>> (setq tg--last-doc nil))))
>> tg--last-doc)))
>>
>> (defun tg-eldoc-init ()
>> (set (make-local-variable 'eldoc-documentation-function)
>> 'tg-documentation-function)
>> (add-hook 'after-save-hook
>> 'tg-init-schema nil t)
>> (tg-init-schema))
>>
>> This worked very nice some time ago, but now my documentation function
>> is only called if point changes the line, but not on point movement on
>> the current line.
>
> An idea: did you check that `eldoc-message-commands' contains the
> commands after which you expect Eldoc to show the info? Maybe the recent
> bidi changes could affect this (i.e., some commands were renamed IIRC)?
>
>
> Štěpán
>
>
>
>
--
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/
prev parent reply other threads:[~2010-06-01 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 12:31 bug#6321: 24.0.50; eldoc-documentation-function only called when changing line Tassilo Horn
2010-06-01 11:21 ` Štěpán Němec
2010-06-01 12:01 ` Tassilo Horn
2010-06-01 13:28 ` Thierry Volpiatto
2010-06-01 12:29 ` Thierry Volpiatto [this message]
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=87sk570wdb.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
/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).