From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Johannes Neyer <johannes.neyer@gmail.com>, 48596@debbugs.gnu.org
Subject: bug#48596: CC Mode 5.34.1 (C/*l); Typing `(` des not trigger eldoc
Date: Fri, 15 Jul 2022 18:50:48 +0000 [thread overview]
Message-ID: <YtG3CGGumfxEKR4p@ACM> (raw)
In-Reply-To: <87mtdan0cj.fsf@gnus.org>
Hello, Lars and Johannes.
On Fri, Jul 15, 2022 at 12:20:44 +0200, Lars Ingebrigtsen wrote:
> Johannes Neyer <johannes.neyer@gmail.com> writes:
> > `(` is bound to `c-electric-paren` which does not trigger eldoc by
> > default.
This is true.
> Most modes have`(` bound to `self-insert-command`.
This is also true.
There seems to be a suggestion that if CC Mode's ( were bound to
self-insert-command, suddenly eldoc facilities would become available.
This is sadly not true.
Doing a quick grep through lisp/progmodes, it seems that those languages
which use eldoc do not have compile-time type checking. This makes it
far easier to write the whole argument sequence of a function into the
limited space of the echo area.
The languages using eldoc seem to be in a minority - Lisp, Python, Perl,
Octave. I do not know if the eldoc infrastructure handles languages
with compile-time type annotations.
> > See https://github.com/joaotavora/eglot/issues/696 for reference.
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
> Perhaps Alan has some comments here; added to the CCs.
I think that to add an eldoc facility to CC Mode would be quite a lot of
work. Patches are welcome!
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2022-07-15 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70aa74c8-956b-c09e-8b1d-11fdbe1d76d8@gmail.com>
2022-07-15 10:20 ` bug#48596: CC Mode 5.34.1 (C/*l); Typing `(` des not trigger eldoc Lars Ingebrigtsen
2022-07-15 18:50 ` Alan Mackenzie [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=YtG3CGGumfxEKR4p@ACM \
--to=acm@muc.de \
--cc=48596@debbugs.gnu.org \
--cc=johannes.neyer@gmail.com \
--cc=larsi@gnus.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).