From: Tim Howes via Bug reports for GNU Guix <bug-guix@gnu.org>
To: divoplade <d@divoplade.fr>, 43093@debbugs.gnu.org
Subject: bug#43093: emacs-ess is broken by emacs 27.1
Date: Fri, 4 Sep 2020 11:25:24 -0700 [thread overview]
Message-ID: <1dcca395-324d-d167-836d-31329e2c3fd7@lavabit.com> (raw)
In-Reply-To: <605a30acc9c66c09938147cccfcaafc3b9f8d57e.camel@divoplade.fr>
On 8/28/2020 1:07 PM, divoplade wrote:
> Hello all,
>
> Right now emacs-ess is broken so I cannot upgrade to emacs 27. The
> failing test is "test-ess-roxy-literate".
>
> Thank you anyway, I cannot wait to have emacs 27!
>
> divoplade
>
>
>
>
Hello,
I think, instead of disabling the test or trying to make it work with
emacs 27, I'd like to update emacs-ess to a more recent version. Right
now it's using the latest tagged release (18.10.2), which was from 2018,
but there's been active development on the github repo since then. I can
take the latest commit and give it a version number based on the commit
time, similar to how it's done on melpa (20200903.1516). I'll try making
a patch to update it to that version.
-Tim
next prev parent reply other threads:[~2020-09-04 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 20:07 bug#43093: emacs-ess is broken by emacs 27.1 divoplade
2020-09-04 14:44 ` bug#43093: Is Emacs 27.1 that breaks emacs-ess? zimoun
2020-09-04 15:26 ` divoplade
2020-09-04 17:00 ` Mark H Weaver
2020-09-04 18:09 ` zimoun
2020-09-04 18:25 ` Tim Howes via Bug reports for GNU Guix [this message]
2020-09-07 21:19 ` bug#43093: emacs-ess is broken by emacs 27.1 divoplade
2020-09-07 21:43 ` divoplade
2020-09-07 21:52 ` divoplade
2020-09-08 19:24 ` Tim Howes via Bug reports for GNU Guix
2020-09-04 23:25 ` bug#43093: [PATCH] gnu: emacs-ess: Update to 20200903.1516 Tim Howes via Bug reports for GNU Guix
2020-09-28 3:28 ` Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1dcca395-324d-d167-836d-31329e2c3fd7@lavabit.com \
--to=bug-guix@gnu.org \
--cc=43093@debbugs.gnu.org \
--cc=d@divoplade.fr \
--cc=timhowes@lavabit.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/guix.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).