From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>,
Michal Nazarewicz <mina86@mina86.com>
Cc: 26274@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#26274: 26.0.50; completion regression
Date: Thu, 30 Mar 2017 05:33:22 +0300 [thread overview]
Message-ID: <83wpb75w99.fsf@gnu.org> (raw)
In-Reply-To: <878tnnzwdg.fsf@rosalinde> (message from Stephen Berman on Wed, 29 Mar 2017 22:00:27 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 26274@debbugs.gnu.org
> Date: Wed, 29 Mar 2017 22:00:27 +0200
>
> > Starting from a fresh checkout like Eli suggested is the safest way,
> > but I guess you should be able to get around this error by deleting
> > 'Makefile', and regenerating it by running ./configure again.
>
> Thanks, I went this route, and it worked (and still took almost an hour
> to go through eight iterations). Git bisect in fact pinpointed this
> commit:
>
> 5ec3a58462e99533ea5200de356302181d634d0b is the first bad commit
> commit 5ec3a58462e99533ea5200de356302181d634d0b
> Author: Michal Nazarewicz <mina86@mina86.com>
> Date: Mon Sep 19 00:23:40 2016 +0200
>
> Generate upcase and downcase tables from Unicode data (bug#24603)
>
> Use Unicode data to generate case tables instead of mostly repeating
> them in lisp code. Do that in a way which maps ‘Dz’ (and similar)
> digraph to ‘dz’ when down- and ‘DZ’ when upcasing.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?msg=89;bug=24603 lists all
> changes to syntax table and case tables introduced by this commit.
>
> * lisp/international/characters.el: Remove case-pairs defined with
> explicit Lisp code and instead use Unicode character properties.
>
> * test/src/casefiddle-tests.el (casefiddle-tests--characters,
> casefiddle-tests-casing): Update test cases which are now working
> as they should.
>
> (When Eli listed this as a candidate, I doubted it because of the date,
> since my build from February 8 of this year does not have the problem.
> I guess that date is not the commit date. Confusing when looking at the
> commit log.)
The commit date is Feb 15. This commit came from a feature branch, so
the date you see in the log I show is the original commit date on that
branch.
Michal, could you please take a look at this?
next prev parent reply other threads:[~2017-03-30 2:33 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
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 [this message]
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=83wpb75w99.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26274@debbugs.gnu.org \
--cc=mina86@mina86.com \
--cc=npostavs@users.sourceforge.net \
--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).