all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eason Huang <aqua0210@foxmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 60556@debbugs.gnu.org
Subject: bug#60556: 29.0.60; Fatal error accurred when editing init.el with flymake enabled on Windows 10
Date: Mon, 23 Jan 2023 18:26:14 +0000	[thread overview]
Message-ID: <CALDnm52QzvOuORhruSw2_gqNxfXWTozEXqYTvdj40_iu75BFXw@mail.gmail.com> (raw)
In-Reply-To: <tencent_0F5F384A2091B63656C183D61E37E7E5D209@qq.com>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

> 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?

From my part, not really.

From what I read in the attached issue, it seems Borg does things
with the load path that interferes with Emacs's ability to invoke
itself as a sub-process.

João

[-- Attachment #2: Type: text/html, Size: 691 bytes --]

  parent reply	other threads:[~2023-01-23 18:26 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
2023-01-23 18:26   ` João Távora [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALDnm52QzvOuORhruSw2_gqNxfXWTozEXqYTvdj40_iu75BFXw@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=60556@debbugs.gnu.org \
    --cc=aqua0210@foxmail.com \
    --cc=eliz@gnu.org \
    /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.