From: Andrea Corallo <akrl@sdf.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 40126@debbugs.gnu.org
Subject: bug#40126: Acknowledgement (28.0.50; [feature/native-comp] + Org 9.3.6 org-with-wide-buffer macro is wrongly treated as function)
Date: Tue, 07 Apr 2020 19:27:00 +0000 [thread overview]
Message-ID: <xjf369f9jwb.fsf@sdf.org> (raw)
In-Reply-To: <877dyr4lct.fsf@localhost> (Ihor Radchenko's message of "Tue, 07 Apr 2020 18:54:26 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> Hi Andrea,
>
>> yes but in org-refile.el there are no requires at all :O
>
> That looks strange for me too. Though org-mode somehow manages to
> be compiled with normal byte-compilation...
>
> I suspect that it relies on compiling org.el first with
> (eval-and-compile (require 'org-macs)) forcing Emacs to have all the
> macros defined there to be available (dynamically) during compilation of
> all other org-mode source files.
>
> I have reported this as a bug to org-mode mail-list [1]. Lets see what they
> say.
>
> On the native-compile branch side, it would probably be a good idea to
> throw an error in similar scenarios instead of generating erroneous .eln
> file.
I don't think we should refuse to compile for warnings.
Saying that during deferred compilation we do not compile any file with
a warning we could end-up being unable to compile many files.
We certainly have to signal in a bettere way errors and warning
happening during async compilaiton to the user tho.
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-04-07 19:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 20:38 bug#40126: 28.0.50; [feature/native-comp] + Org 9.3.6 org-with-wide-buffer macro is wrongly treated as function Ihor Radchenko
2020-04-03 21:41 ` Andrea Corallo
2020-04-04 8:28 ` Ihor Radchenko
[not found] ` <handler.40126.B.158456414025437.ack@debbugs.gnu.org>
2020-04-04 8:29 ` bug#40126: Acknowledgement (28.0.50; [feature/native-comp] + Org 9.3.6 org-with-wide-buffer macro is wrongly treated as function) Ihor Radchenko
2020-04-04 8:29 ` Ihor Radchenko
2020-04-04 10:05 ` Andrea Corallo
2020-04-04 10:35 ` Ihor Radchenko
2020-04-06 22:04 ` Andrea Corallo
2020-04-07 7:44 ` Ihor Radchenko
2020-04-07 10:18 ` Andrea Corallo
2020-04-07 10:54 ` Ihor Radchenko
2020-04-07 19:27 ` Andrea Corallo [this message]
2020-04-10 15:56 ` Andrea Corallo
2020-04-18 16:15 ` Ihor Radchenko
2020-04-10 16:06 ` Andrea Corallo
2020-04-07 7:45 ` Andrea Corallo
2020-04-07 12:43 ` bug#40126: Adam Porter
2020-04-07 13:45 ` bug#40126: Andrea Corallo
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=xjf369f9jwb.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=40126@debbugs.gnu.org \
--cc=yantar92@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 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).