From: Eason Huang <aqua0210@foxmail.com>
To: 60556@debbugs.gnu.org
Cc: "Eli Zaretskii" <eliz@gnu.org>, "João Távora" <joaotavora@gmail.com>
Subject: bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10
Date: Sun, 22 Jan 2023 14:34:23 +0800 [thread overview]
Message-ID: <tencent_E8F1D7D03647E4105E9C4B86909237A2C009@qq.com> (raw)
In-Reply-To: <tencent_0F5F384A2091B63656C183D61E37E7E5D209@qq.com> (Eason Huang's message of "Sun, 22 Jan 2023 12:30:36 +0800")
Eason Huang <aqua0210@foxmail.com> writes:
> Eason Huang <aqua0210@foxmail.com> writes:
>
>> Hi emacs,
>>
>> When I editing my ~/.config/emacs/init.el file, Emacs will raise a fatal
>> error frequenly when flymake-mode enabled.
>>
>> With a few hours debug, I found that it's related to flymake-mode and
>> Borg( A package manager writed by Jonas Bernoulli).
>>
>> Borg repos: https://github.com/emacscollective/borg
>>
>>
>> This issue can be fixed by disable flymake-mode or without Borg, just
>> use package.el to install packages.
>>
>> It would be nice if I can use Borg with flymake-mode. I am not sure this
>> bug if from Borg or flymake-mode or Emacs itself, so I report it here.
>>
>
> I also reported an issue to Borg. See more infomation by the link bellow:
> https://github.com/emacscollective/borg/issues/140
>
> I guess the issue is cause by the implementation of UI displaying on
> MS-Windows.
>
> JoJoão and Eli, do you have any advice on how to debug with this issue?
>
> Thanks in advance.
Now I can reproduce the issue with `emacs -Q`. So now I can confirm that
the isse is not related to Borg.
We need to use a larger buffer for reproduce.
for example, I use the flmake.el instead of a simple test file.
Steps to reproduce:
1. Start Emacs 29 with emacs -Q
2. C-c C-f ~/test.el to open a test buffer.
3. Copy all the content of flymake.el to ~/test.el
4. Enable flymake-mode with M-x flymake-mode
5. Try to add some blank lines and then C-x C-s to save buffer
6. Repeat step 5 many times, you will get the fatal error pos up.
See the picture by this link:
https://github.com/emacscollective/borg/issues/140#issuecomment-1399414074
--
Eason Huang
next prev parent reply other threads:[~2023-01-22 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:44 bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10 Eason Huang
2023-01-22 4:30 ` Eason Huang
2023-01-22 6:34 ` Eason Huang [this message]
2023-01-23 18:26 ` João Távora
2023-01-23 19:00 ` Eli Zaretskii
2023-01-24 12:50 ` Eason Huang
2023-01-22 11:03 ` Eli Zaretskii
2023-01-22 11:22 ` Eason Huang
2023-01-22 11:55 ` Eli Zaretskii
2023-01-22 12:11 ` Eason Huang
2023-01-22 13:05 ` Eli Zaretskii
2023-01-22 13:27 ` Eason Huang
2023-01-22 14:03 ` Eli Zaretskii
2023-01-22 14:39 ` Eason Huang
2023-01-22 14:40 ` 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
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=tencent_E8F1D7D03647E4105E9C4B86909237A2C009@qq.com \
--to=aqua0210@foxmail.com \
--cc=60556@debbugs.gnu.org \
--cc=eliz@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 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).