[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#41618: 28.0.50; Can't byte-compile an edebugged macro
|
From: |
Philipp Stephani |
|
Subject: |
bug#41618: 28.0.50; Can't byte-compile an edebugged macro |
|
Date: |
Sun, 31 May 2020 19:59:52 +0200 |
Am So., 31. Mai 2020 um 19:56 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > Date: Sun, 31 May 2020 17:41:53 +0000
> > Cc: 41618@debbugs.gnu.org, p.stephani2@gmail.com
> > From: Alan Mackenzie <acm@muc.de>
> >
> > > Thanks, but why to emacs-27? Is this bug a regression from Emacs 26?
> >
> > It was difficult to decide, but emacs-27 seemed right; the bug was
> > almost certainly a regression from Emacs 26, the erroneous commit having
> > been made on 2019-07-27.
>
> Which commit was that? I don't think you mentioned that.
My guess is on 1c8405e33e814a372fa349313521b015c3601605, but I haven't
formally bisected.
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Philipp Stephani, 2020/05/30
- Message not available
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Alan Mackenzie, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Eli Zaretskii, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Alan Mackenzie, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Eli Zaretskii, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro,
Philipp Stephani <=
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Alan Mackenzie, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Eli Zaretskii, 2020/05/31
- bug#41618: 28.0.50; Can't byte-compile an edebugged macro, Philipp Stephani, 2020/05/31