From: "N. Jackson" <njackson@posteo.net>
To: Andrea Corallo <acorallo@gnu.org>, Magnar Sveen <magnars@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 73303@debbugs.gnu.org
Subject: bug#73303: 30.0.91; Native compiler repeatedly interrupts at random moments
Date: Wed, 18 Sep 2024 00:43:10 +0000 [thread overview]
Message-ID: <87r09h94gx.fsf@Phoenix> (raw)
In-Reply-To: <yp1setzflfq.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Mon, 16 Sep 2024 15:27:53 -0400")
Hello Magnar,
In this Emacs Bug thread[1] (about native compiler warnings popping
up at inopportune moments), it was suggested that someone report to
you some specific warnings being caused by your package
expand-region, and I am doing so by including you in this email.
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73303
At 15:27 -0400 on Monday 2024-09-16, Andrea Corallo wrote:
>
>>> From: "N. Jackson" <njackson@posteo.net>
>>> Date: Mon, 16 Sep 2024 18:14:46 +0000
>>>
>>>
>>> Since building Emacs 30.0.91, I have repeatedly been interrupted in
>>> my work by warnings from the native compiler.
>>>
>>> A few examples of the warnings are:
>>>
>>> Warning (native-compiler): ~/.config/emacs/modules/cdlatex.el:1025:26: Warning: the function ‘reftex-what-environment’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:161:10: Warning: the function ‘python-nav-end-of-block’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:138:8: Warning: the function ‘python-util-forward-comment’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:94:4: Warning: the function ‘python-nav-beginning-of-statement’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:92:4: Warning: the function ‘python-nav-end-of-statement’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:62:31: Warning: the function ‘python-syntax-context’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:39:39: Warning: the function ‘python-indent’ is not known to be defined.
>>> Warning (native-compiler): python-el-fgallina-expansions.el:37:40: Warning: the function ‘python-info-ppss-context’ is not known to be defined.
>
> I think the python* warnings should be reported as bugs to
> <https://github.com/magnars/expand-region.el>.
>
> Andrea
Thanks Andrea, that allowed me to track these ones down. I have in
my init file
(custom-set-variables
...
'(package-archives
'(("gnu" . "https://elpa.gnu.org/packages/")))
...
'(package-selected-packages
'(... expand-region ...))
...)
and indeed the offending files (for this particular set of warnings)
are in ~/.config/emacs/elpa/expand-region-1.0.0/.
I don't think I can report this to the author and maintainer of
expand-region on Github because, IIUC, that would require me to run
proprietary JavaScript, but I am including him (Magnar Sveen) in
this email.
N.
next prev parent reply other threads:[~2024-09-18 0:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 18:14 bug#73303: 30.0.91; Native compiler repeatedly interrupts at random moments N. Jackson
2024-09-16 18:42 ` Eli Zaretskii
2024-09-16 19:27 ` Andrea Corallo
2024-09-18 0:43 ` N. Jackson [this message]
[not found] ` <87plp2mhj1.fsf@moondust.awandering>
2024-09-17 15:59 ` Eli Zaretskii
2024-09-17 18:46 ` Philip Kaludercic
2024-09-17 19:09 ` N. Jackson
2024-09-17 20:10 ` Philip Kaludercic
2024-09-24 19:13 ` Andrea Corallo
2024-09-17 19:09 ` Eli Zaretskii
2024-09-17 20:09 ` N. Jackson
2024-09-18 11:29 ` Eli Zaretskii
2024-09-24 19:10 ` Andrea Corallo
2024-09-25 11:15 ` Eli Zaretskii
2024-09-25 18:47 ` Andrea Corallo
2024-10-19 6:58 ` Eli Zaretskii
2024-10-22 16:29 ` Andrea Corallo
2024-10-23 7:04 ` Eli Zaretskii
2024-10-23 7:44 ` Andrea Corallo
2024-09-17 16:01 ` N. Jackson
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=87r09h94gx.fsf@Phoenix \
--to=njackson@posteo.net \
--cc=73303@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=magnars@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).