From: Ken Brown <kbrown@cornell.edu>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 32318@debbugs.gnu.org
Subject: bug#32318: wdired-test-bug32173-02 fails
Date: Tue, 31 Jul 2018 08:35:27 -0400 [thread overview]
Message-ID: <71cf872f-5ca0-d5a1-8ff0-20299af89b29@cornell.edu> (raw)
In-Reply-To: <87sh40uya0.fsf@gmx.net>
On 7/30/2018 6:57 PM, Stephen Berman wrote:
> I think I've fixed this now, simply by requiring wdired (in emacs-26
> 951c5a1).
That fixes it for me. Thanks.
Ken
next prev parent reply other threads:[~2018-07-31 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 18:02 bug#32318: wdired-test-bug32173-02 fails Glenn Morris
2018-07-30 18:46 ` Ken Brown
2018-07-30 22:57 ` Stephen Berman
2018-07-31 12:35 ` Ken Brown [this message]
2018-07-31 12:40 ` Stephen Berman
2018-08-08 10:06 ` Stephen Berman
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=71cf872f-5ca0-d5a1-8ff0-20299af89b29@cornell.edu \
--to=kbrown@cornell.edu \
--cc=32318@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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).