all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 35663@debbugs.gnu.org
Subject: bug#35663: 27.0.50; Eldoc support for apply
Date: Thu, 27 Aug 2020 15:07:14 +0200	[thread overview]
Message-ID: <87tuwow83h.fsf@gnus.org> (raw)
In-Reply-To: <CALDnm51ctpU4EeLbmJtEyHxbyumRXCH+JQNfG2Ct_Egsm15fjw@mail.gmail.com> ("João Távora"'s message of "Wed, 26 Aug 2020 12:11:52 +0100")

João Távora <joaotavora@gmail.com> writes:

> I think this makes sense. SLY/SLIME for CL do something similar
> with #'make-instance, for instance.  As soon as you type the function name
> or class name and the autodoc system recognizes it, it switches to the 
> showing you the args for that function instead.
>
> The patch shouldn't be terribly difficult to adapt, since I've not
> significantly touched the client-side logic (as in clients of eldoc).

I had a very brief look at adapting the patch to the new eldoc setup --
I guess the code should go into elisp-eldoc-funcall?

However, the parameters have changed somewhat, and I'm not familiar with
this code at all, so I think it would be preferable if somebody else
took a look at it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-08-27 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  0:11 bug#35663: 27.0.50; Eldoc support for apply Michael Heerdegen
2019-05-10  0:58 ` Noam Postavsky
2019-05-10 10:24   ` Michael Heerdegen
2019-05-10 10:28     ` Noam Postavsky
2019-05-10 11:41       ` Michael Heerdegen
2020-08-26 10:32 ` Lars Ingebrigtsen
2020-08-26 11:11   ` João Távora
2020-08-27 13:07     ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tuwow83h.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=35663@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=michael_heerdegen@web.de \
    /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.