From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: philipk@posteo.net, emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: Getting ready to land native-compilation on master
Date: Wed, 14 Apr 2021 20:10:42 +0300 [thread overview]
Message-ID: <83blagzt9p.fsf@gnu.org> (raw)
In-Reply-To: <62f2407a-fb7b-05b7-32ea-6cbda2eed1a7@yandex.ru> (message from Dmitry Gutov on Wed, 14 Apr 2021 17:48:11 +0300)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 14 Apr 2021 17:48:11 +0300
> Cc: akrl@sdf.org, emacs-devel@gnu.org
>
> On 14.04.2021 17:37, Eli Zaretskii wrote:
> > Ah, overlong lines in_docstrings_... Yes, that's known, but why not
> > fix this issue in the first place? I get the same warning when
> > byte-compiling with Emacs 28, so this is not new with the
> > native-compile branch.
>
> I guess the issue is that native compilation happens after the package
> is installed, so the warnings come basically out of the blue.
I was originally annoyed by this, but eventually concluded that it's
all part of the automatic background compilation, something we didn't
have before. I think with time people will get used to it, and the
surprise will go away. And if someone is really annoyed, they can
always disable automatic background compilation altogether.
I tend to think that turning warnings off is not a good idea, for the
same reasons we don't by default turn off byte-compilation warnings.
But we will cross this bridge when we come to it.
next prev parent reply other threads:[~2021-04-14 17:10 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 14:02 Getting ready to land native-compilation on master Eli Zaretskii
2021-04-09 14:27 ` tomas
2021-04-09 14:33 ` Stefan Kangas
2021-04-09 14:39 ` T.V Raman
2021-04-09 16:17 ` Pip Cet
2021-04-09 16:35 ` Thierry Volpiatto
2021-04-09 18:57 ` Eli Zaretskii
2021-04-10 5:39 ` Thierry Volpiatto
2021-04-09 17:12 ` Jens C. Jensen
2021-04-09 18:53 ` Stefan Monnier
2021-04-09 18:59 ` Jens C. Jensen
2021-04-09 22:43 ` Stefan Monnier
2021-04-10 8:45 ` Jens C. Jensen
2021-04-10 13:10 ` Stefan Monnier
2021-04-09 19:08 ` Andrea Corallo via Emacs development discussions.
2021-04-09 19:14 ` Eli Zaretskii
2021-04-10 0:07 ` Andy Moreton
2021-04-10 7:23 ` Eli Zaretskii
2021-04-10 11:40 ` Andy Moreton
2021-04-09 18:09 ` Sujith Manoharan
2021-04-09 18:50 ` Eli Zaretskii
2021-04-09 18:27 ` Alex Bennée
2021-04-09 18:48 ` Andrea Corallo via Emacs development discussions.
2021-04-14 4:39 ` Pankaj Jangid
2021-04-14 6:31 ` Eli Zaretskii
2021-04-14 9:45 ` Philip Kaludercic
2021-04-14 10:14 ` Andrea Corallo via Emacs development discussions.
2021-04-14 10:35 ` Philip Kaludercic
2021-04-14 10:45 ` Eli Zaretskii
2021-04-14 10:49 ` Eli Zaretskii
2021-04-14 12:57 ` Philip Kaludercic
2021-04-14 13:10 ` Eli Zaretskii
2021-04-14 14:00 ` Philip Kaludercic
2021-04-14 14:35 ` Stefan Kangas
2021-04-14 14:42 ` Philip Kaludercic
2021-04-14 14:50 ` Stefan Monnier
2021-04-14 15:02 ` Eli Zaretskii
2021-04-14 14:37 ` Eli Zaretskii
2021-04-14 14:48 ` Dmitry Gutov
2021-04-14 17:10 ` Eli Zaretskii [this message]
2021-04-14 10:48 ` Andrea Corallo via Emacs development discussions.
2021-04-14 15:53 ` wilde
2021-04-14 17:02 ` Eli Zaretskii
2021-04-14 17:28 ` Alex Bennée
2021-04-14 17:41 ` Eli Zaretskii
2021-04-15 11:15 ` Alex Bennée
2021-04-14 18:07 ` Andrea Corallo via Emacs development discussions.
2021-04-14 20:23 ` Stefan Kangas
2021-04-14 22:01 ` Andrea Corallo via Emacs development discussions.
2021-04-15 9:25 ` wilde
2021-04-15 11:19 ` wilde
2021-04-15 16:23 ` Andrea Corallo via Emacs development discussions.
2021-04-27 16:25 ` wilde
2021-04-28 3:06 ` Corwin Brust
2021-04-28 17:52 ` Jose E. Marchesi
2021-04-29 8:20 ` Arthur Miller
2021-04-22 10:09 ` wilde
2021-04-22 11:14 ` Eli Zaretskii
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=83blagzt9p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.