* Byte-compilation warnings after merging eldoc changes
@ 2020-07-08 14:33 Eli Zaretskii
2020-07-08 14:38 ` João Távora
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2020-07-08 14:33 UTC (permalink / raw)
To: João Távora; +Cc: emacs-devel
Like this:
In cfengine3-mode:
progmodes/cfengine.el:1400:41: Warning: `eldoc-documentation-function' is an
obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
instead.
progmodes/cfengine.el:1399:52: Warning: `eldoc-documentation-function' is an
obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
instead.
In python-mode:
progmodes/python.el:5556:13: Warning: `eldoc-documentation-function' is an
obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
instead.
progmodes/python.el:5562:43: Warning: `eldoc-documentation-function' is an
obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
instead.
Can these be fixed, please?
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Byte-compilation warnings after merging eldoc changes
2020-07-08 14:33 Byte-compilation warnings after merging eldoc changes Eli Zaretskii
@ 2020-07-08 14:38 ` João Távora
2020-07-08 14:48 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: João Távora @ 2020-07-08 14:38 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel
Eli Zaretskii <eliz@gnu.org> writes:
> Like this:
>
> In cfengine3-mode:
> progmodes/cfengine.el:1400:41: Warning: `eldoc-documentation-function' is an
> obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
> instead.
> progmodes/cfengine.el:1399:52: Warning: `eldoc-documentation-function' is an
> obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
> instead.
>
> In python-mode:
> progmodes/python.el:5556:13: Warning: `eldoc-documentation-function' is an
> obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
> instead.
> progmodes/python.el:5562:43: Warning: `eldoc-documentation-function' is an
> obsolete variable (as of eldoc-1.1.0); use `eldoc-documentation-strategy'
> instead.
>
> Can these be fixed, please?
Yes. I'm working on it, shouldn't take long.
João
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Byte-compilation warnings after merging eldoc changes
2020-07-08 14:38 ` João Távora
@ 2020-07-08 14:48 ` Eli Zaretskii
2020-07-08 15:23 ` João Távora
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2020-07-08 14:48 UTC (permalink / raw)
To: João Távora; +Cc: emacs-devel
> From: João Távora <joaotavora@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 08 Jul 2020 15:38:24 +0100
>
> > Can these be fixed, please?
>
> Yes. I'm working on it, shouldn't take long.
Thank you.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Byte-compilation warnings after merging eldoc changes
2020-07-08 14:48 ` Eli Zaretskii
@ 2020-07-08 15:23 ` João Távora
2020-07-08 16:15 ` Stefan Monnier
0 siblings, 1 reply; 5+ messages in thread
From: João Távora @ 2020-07-08 15:23 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel
After analysing, I've discovered these are due to `if`
branches checking for earlier Emacs versions.
cfengine.el isn't but python.el is distributed in GNU ELPA
as a :core package which promises to support Emacs 24.1.
So while I would just delete the branch in the cfengine.el
case, I wonder what to do in the python.el case. Can I
shoosh the byte-compiler warning of a particular type for
a particular file?
Thanks,
João
On Wed, Jul 8, 2020 at 3:48 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: João Távora <joaotavora@gmail.com>
> > Cc: emacs-devel@gnu.org
> > Date: Wed, 08 Jul 2020 15:38:24 +0100
> >
> > > Can these be fixed, please?
> >
> > Yes. I'm working on it, shouldn't take long.
>
> Thank you.
--
João Távora
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Byte-compilation warnings after merging eldoc changes
2020-07-08 15:23 ` João Távora
@ 2020-07-08 16:15 ` Stefan Monnier
0 siblings, 0 replies; 5+ messages in thread
From: Stefan Monnier @ 2020-07-08 16:15 UTC (permalink / raw)
To: João Távora; +Cc: Eli Zaretskii, emacs-devel
> So while I would just delete the branch in the cfengine.el
> case, I wonder what to do in the python.el case. Can I
> shoosh the byte-compiler warning of a particular type for
> a particular file?
You can use `with-no-warnings` (with more recent versions, you can be
more specific thanks to `with-suppressed-warnings`).
Stefan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-07-08 16:15 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-08 14:33 Byte-compilation warnings after merging eldoc changes Eli Zaretskii
2020-07-08 14:38 ` João Távora
2020-07-08 14:48 ` Eli Zaretskii
2020-07-08 15:23 ` João Távora
2020-07-08 16:15 ` Stefan Monnier
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).