From: Michal Nazarewicz <mina86@mina86.com>
To: Eli Zaretskii <eliz@gnu.org>, Stephen Berman <stephen.berman@gmx.net>
Cc: 26274@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#26274: 26.0.50; completion regression
Date: Thu, 30 Mar 2017 15:38:57 +0200 [thread overview]
Message-ID: <xa1tinmqkhou.fsf@mina86.com> (raw)
In-Reply-To: <83wpb75w99.fsf@gnu.org>
On Thu, Mar 30 2017, Eli Zaretskii wrote:
>> 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.)
You can do ‘git show --format=fuller 5ec3a58462e99533ea520’ to see
commit date but even that can be rather misleading.
> 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?
Strangely I cannot reproduce it. I’ve run ‘emacs -Q’, executed
(custom-set-variables
'(completion-category-overrides
(quote ((buffer (styles substring))
(file (styles substring)))))
'(read-buffer-completion-ignore-case t)
'(read-file-name-completion-ignore-case t))
and with atest, Atest, ätest, Ätest, testä and testÄ files in the
directory I get the following completions:
| Typed | Completions |
|-------+-------------------------------------|
| test | atest Atest ätest Ätest testä testÄ |
|-------+-------------------------------------|
| atest | atest Atest |
| Atest | atest Atest |
| ätest | ätest Ätest |
| Ätest | ätest Ätest |
|-------+-------------------------------------|
| testa | NOTHING |
| testA | NOTHING |
| testä | testä testÄ |
| testÄ | testä testÄ |
which is what is expected.
GNU Emacs 26.0.50 (build 3, x86_64-pc-linux-gnu) of 2017-03-21 build
from ffbb4684999 (I think) + patchset (I think). I’ll rebase and try
again with fresher version.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
next prev parent reply other threads:[~2017-03-30 13:38 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
2017-03-30 13:38 ` Michal Nazarewicz [this message]
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=xa1tinmqkhou.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=26274@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).