From: Eli Zaretskii <eliz@gnu.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: ghe@sdf.org, monnier@iro.umontreal.ca, 42383-done@debbugs.gnu.org
Subject: bug#42383: 28.0.50; Two bugs with M-x compile
Date: Sat, 18 Jul 2020 11:22:50 +0300 [thread overview]
Message-ID: <837dv1i65h.fsf@gnu.org> (raw)
In-Reply-To: <87zh7zrvf6.fsf@gmail.com> (message from Alex Branham on Thu, 16 Jul 2020 17:39:57 -0400)
unarchive 10417
reopen 10417
unarchive 34330
reopen 34330
thanks
> From: Alex Branham <alex.branham@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Gregory Heytings <ghe@sdf.org>,
> 42383@debbugs.gnu.org
> Date: Thu, 16 Jul 2020 17:39:57 -0400
>
> > yet, `pcomplete-completions-at-point` is supposed to perform filename
> > completion also (via `pcomplete-default-completion-function`), so
> > I think `pcomplete-completions-at-point` should come first and I suspect
> > that the problem in bug#34330 is internal to pcomplete and the above
> > commit just worked around it.
>
> I find pcomplete really confusing (why is it that there's a whole second
> kind of completion framework outside completion-at-point?). But yes,
> sounds like this should be reverted. I didn't notice this regression
> since I use ivy which obviates the need to re-complete after typing a
> letter.
>
> Someone will need to reopen bugs #10417 and #34330.
OK, thanks. I've reverted the change and reopened those two bugs.
prev parent reply other threads:[~2020-07-18 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 23:23 bug#42383: 28.0.50; Two bugs with M-x compile Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-16 9:48 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-16 15:17 ` Eli Zaretskii
2020-07-16 18:55 ` Stefan Monnier
2020-07-16 21:39 ` Alex Branham
2020-07-16 22:37 ` Stefan Monnier
2020-07-18 8:22 ` Eli Zaretskii [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
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=837dv1i65h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42383-done@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=ghe@sdf.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).