From: Stephen Berman <stephen.berman@gmx.net>
To: 26274@debbugs.gnu.org
Subject: bug#26274: 26.0.50; completion regression
Date: Wed, 29 Mar 2017 19:00:30 +0200 [thread overview]
Message-ID: <87lgroyq4x.fsf@rosalinde> (raw)
In-Reply-To: <87a886wuyi.fsf@rosalinde> (Stephen Berman's message of "Mon, 27 Mar 2017 18:22:29 +0200")
On Mon, 27 Mar 2017 18:22:29 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
> On Mon, 27 Mar 2017 12:56:19 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
>
>> Substring completion involving non-ascii characters (with or without
>> case-folding) does not work in current master as it had till recently
>> and still does in Emacs 25.2 (my most recent build from master is from
>
> Oops: s/most recent/oldest/
>
>> March 15 and it also shows the problem). To reproduce:
This is commit a3207a383009720bbd89327425e0eb1c9c20c267. I have now
found an older build from master from February 8, commit
e3b659630843de7e459bce483c278af765c644f7, which does not have this
completion problem. However, when I run git bisect on these commits and
then make, it fails as follows:
steve@rosalinde:/data/steve/git/emacs-master> make
cd . && ./autogen.sh autoconf
Checking whether you have the necessary tools...
(Read INSTALL.REPO for more details on building Emacs)
Checking for autoconf (need at least version 2.65) ... ok
Checking for automake (need at least version 1.11) ... ok
Your system has the required tools.
Running 'autoreconf -fi -I m4' ...
/usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No such file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
/usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No such file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
autoreconf: /usr/bin/autoconf failed with exit status: 1
Makefile:450: recipe for target 'configure' failed
make: *** [configure] Error 1
This continues to happen when I repeatedly call `git bisect skip'. Is
there anything I can do to proceed with the bisection?
Steve Berman
next prev parent reply other threads:[~2017-03-29 17:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 10:56 bug#26274: 26.0.50; completion regression Stephen Berman
2017-03-27 16:22 ` Stephen Berman
2017-03-29 17:00 ` Stephen Berman [this message]
2017-03-29 17:27 ` Eli Zaretskii
2017-03-29 18:27 ` Stephen Berman
2017-03-29 18:33 ` Eli Zaretskii
2017-03-29 18:43 ` Stephen Berman
2017-03-29 18:49 ` Noam Postavsky
2017-03-29 20:00 ` Stephen Berman
2017-03-30 2:33 ` Eli Zaretskii
2017-03-30 13:38 ` Michal Nazarewicz
2017-03-30 14:17 ` Michal Nazarewicz
2017-03-30 14:30 ` Michal Nazarewicz
2017-03-30 16:18 ` Michal Nazarewicz
2017-03-30 18:02 ` Stephen Berman
2017-03-30 19:11 ` Michal Nazarewicz
2017-03-30 20:14 ` Stephen Berman
2017-03-30 18:06 ` Eli Zaretskii
2017-04-06 18:58 ` Michal Nazarewicz
2017-04-07 8:37 ` Stephen Berman
2017-03-29 17:28 ` Noam Postavsky
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=87lgroyq4x.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=26274@debbugs.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 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).