From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 38458-done@debbugs.gnu.org
Subject: bug#38458: 27.0.50; case-insensitive substring completion
Date: Tue, 03 Dec 2019 18:01:42 +0100 [thread overview]
Message-ID: <87k17dwdft.fsf@gmx.net> (raw)
In-Reply-To: <jwvsgm1a2mz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 03 Dec 2019 09:47:18 -0500")
On Tue, 03 Dec 2019 09:47:18 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> If those changes caused this issue, then I think there was already a
>> bug in the substring completion style, which was just exposed by those
>> changes.
>
> Indeed. I just pushed a fix to `master`. Thank you.
FTR, I confirm that fixes the issue I reported, thanks.
While I was testing cases for the bug report, I noticed that,
independent of case, the placement of point in substring completion is
sometimes suboptimal. E.g. if there two files (or buffers) file1test
and file2test and you enter `fi TAB' then it completes to `file' with
point after the `e', which is fine for further input; but if you enter
`te TAB' then it completes to `test' with point after the second `t', so
you have to move point to complete the name. It would be nice if in
such cases point were placed at the start rather than the end of the
partial match. Should I make a feature request?
Steve Berman
next prev parent reply other threads:[~2019-12-03 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 18:56 bug#38458: 27.0.50; case-insensitive substring completion Stephen Berman
2019-12-02 20:45 ` Eli Zaretskii
2019-12-02 21:37 ` Stephen Berman
2019-12-03 14:47 ` Stefan Monnier
2019-12-03 15:51 ` Eli Zaretskii
2019-12-03 17:01 ` Stephen Berman [this message]
2019-12-03 18:03 ` Stefan Monnier
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=87k17dwdft.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=38458-done@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).