From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Byte-compilation warning in eldoc.el
Date: Fri, 10 Jul 2020 10:41:47 -0400 [thread overview]
Message-ID: <jwv4kqfbfo6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874kqfg7ju.fsf@gmail.com> ("João Távora"'s message of "Fri, 10 Jul 2020 08:20:37 +0100")
> Thanks, fixed. But curiously it doesn't. You can call it (and I always
> do call it) with one argument, as one does in CL.
Technically, you can call it with one argument.
But in 99% of the cases it's a really bad idea.
> By the way, the only reason I had to do this (I rarely use this outside
> interactive contexts)
Exactly: it might make sense occasionally while debugging, but is
usually an error in code.
[ Using it with a second argument is quite different, because then it
usually corresponds to a simple `remhash`. ]
> When defining the obsolete variable alias for old
> eldoc-documentation-function (which now points to the newer
> eldoc-documentation-strategy),
Which reminds me: I think it'd be better not to make it an alias.
> Separately, I also noticed that calling `package-install` for Eldoc in
> Emacs 26.3, will _not_ load eldoc, and neither will `require`.
Not sure what you mean with the "_not_ load" part, but as for `require`,
it's normal because it's preloaded.
Stefan
next prev parent reply other threads:[~2020-07-10 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 6:53 Byte-compilation warning in eldoc.el Eli Zaretskii
2020-07-10 7:20 ` João Távora
2020-07-10 7:43 ` Eli Zaretskii
2020-07-10 9:36 ` Noam Postavsky
2020-07-10 14:41 ` Stefan Monnier [this message]
2020-07-10 15:05 ` Drew Adams
2020-07-10 15:31 ` João Távora
2020-07-10 21:29 ` Stefan Monnier
2020-07-10 21:48 ` João Távora
2020-07-10 22:08 ` Stefan Monnier
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=jwv4kqfbfo6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
/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.