From: Adam Connor <adamc55@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ruijie@netyu.xyz, 61589-done@debbugs.gnu.org
Subject: bug#61589: 28.2; Triple-Quote causes emacs 28 to free in Python-mode
Date: Mon, 20 Feb 2023 11:34:53 -0600 [thread overview]
Message-ID: <CAC_vAoG9Diy86G_0-=b9q_dq=--XsizYdmfFy=_1iK24Qo0JLQ@mail.gmail.com> (raw)
In-Reply-To: <835ybwuvie.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
No way could I wait a few months for a working Python environment...
that's the day job, and this was a huge bug for that. I would have had to
switch to VSCode or something.
But I found a way to build for 29.
On Mon, Feb 20, 2023 at 10:55 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Adam Connor <adamc55@gmail.com>
> > Date: Mon, 20 Feb 2023 09:36:20 -0600
> > Cc: Ruijie Yu <ruijie@netyu.xyz>, 61589-done@debbugs.gnu.org
> >
> > This is frustrating, as emacs 29 is not available on MacOS except via
> compilation. Oh well. On linux,
> > building it is fairly easy, but looks more involved on M1 macs.
>
> Emacs 29 will be released in a few (hopefully a small number of)
> months, so you will be able to have it.
>
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
prev parent reply other threads:[~2023-02-20 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 0:12 bug#61589: 28.2; Triple-Quote causes emacs 28 to free in Python-mode Adam Connor
2023-02-18 3:18 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 3:29 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 7:22 ` Eli Zaretskii
2023-02-20 15:36 ` Adam Connor
2023-02-20 16:18 ` Adam Connor
2023-02-20 16:55 ` Eli Zaretskii
2023-02-20 17:34 ` Adam Connor [this message]
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='CAC_vAoG9Diy86G_0-=b9q_dq=--XsizYdmfFy=_1iK24Qo0JLQ@mail.gmail.com' \
--to=adamc55@gmail.com \
--cc=61589-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ruijie@netyu.xyz \
/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.