comment on

> in your example SHORT EXPLANATION IN ONE-LINE, in the minibuffer (as Eldoc usually does).

This could probably be of interest for you, it redirects the help message from the minibuffer to a tooltip at point.

Probably not the best lisp style, I hacked it about ten years ago, but it never failed me.

It's basically monkey-patching cperl-describe-perl-symbol with an around-function to show the tooltip at the point of the cursor.

I think pos-tip.el needs to be installed first.

(require 'pos-tip)
(require 'cl)

(add-hook 'cperl-mode-hook
      (lambda ()
;;        (cperl-toggle-autohelp)
        (setq cperl-lazy-help-time 2)


        (defadvice cperl-describe-perl-symbol (around cperl-describe-p
+erl-symbol-tooltip activate)
          "redirect message to tooltip"
          (flet ((message (fmt &rest args)
                          (pos-tip-show (apply 'format fmt args))))
            ad-do-it))


        ))
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

In reply to Re^2: Which IDE's show tooltips for Perl builtins? by LanX
in thread Which IDE's show tooltips for Perl builtins? by LanX

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks