From: "João Távora" <joaotavora@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 34070@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#34070: 27.0.50; icomplete-mode candidate cycling broken for C-x C-f
Date: Thu, 17 Jan 2019 15:55:27 +0000 [thread overview]
Message-ID: <CALDnm505iA24J2QOyRQK8w3BKm0UNTdnAegL0XBMGoyNKeU-mQ@mail.gmail.com> (raw)
In-Reply-To: <154c946e-28c9-4afa-865a-ac15d2e83bce@default>
On Thu, Jan 17, 2019 at 3:46 PM Drew Adams <drew.adams@oracle.com> wrote:
> I think you're right that the intention of my patch was
> just to respect `completion-ignored-extensions'. That was
> the "new" behavior to be introduced, and not silently.
Right. That was the "declared" new behaviour (for your definition
of "new"). But there was some "undeclared", undiscussed
new behaviour: that was my point.
> (Note too that you are adding to this bug, which was
> purportedly about broken cycling. Is this additional
> change necessary to fix the cycling problem, or should
> it be the subject of a new bug report?)
Right. I put emphasis on this myself, so I don't have to
"note" it. If you believe it should be the subject of a new
bug, go ahead and create it. I don't think it's worth it.
--
João Távora
prev parent reply other threads:[~2019-01-17 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 13:47 bug#34070: 27.0.50; icomplete-mode candidate cycling broken for C-x C-f João Távora
2019-01-14 16:03 ` Eli Zaretskii
2019-01-14 16:25 ` João Távora
2019-01-14 16:40 ` Eli Zaretskii
2019-01-14 17:11 ` João Távora
2019-01-14 17:40 ` Eli Zaretskii
2019-01-14 17:51 ` João Távora
2019-01-14 17:55 ` Drew Adams
2019-01-17 14:20 ` João Távora
2019-01-17 15:00 ` Stefan Monnier
2019-01-17 15:22 ` João Távora
2019-01-17 15:46 ` Drew Adams
2019-01-17 15:55 ` Stefan Monnier
2019-01-17 15:55 ` João Távora [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm505iA24J2QOyRQK8w3BKm0UNTdnAegL0XBMGoyNKeU-mQ@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=34070@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.