From: Alex Branham <alex.branham@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Gregory Heytings <ghe@sdf.org>, 42383@debbugs.gnu.org
Subject: bug#42383: 28.0.50; Two bugs with M-x compile
Date: Thu, 16 Jul 2020 17:39:57 -0400 [thread overview]
Message-ID: <87zh7zrvf6.fsf@gmail.com> (raw)
In-Reply-To: <jwv365rtprb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 16 Jul 2020 14:55:05 -0400")
On Thu 16 Jul 2020 at 14:55, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> * lisp/shell.el (shell-dynamic-complete-functions): Move
> pcomplete-completions-at-point down the list so that filename
> completion has a chance to complete before pcompletion.
>
> Fixes bug#34330
>
> 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.
Alex
next prev parent reply other threads:[~2020-07-16 21:39 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 [this message]
2020-07-16 22:37 ` Stefan Monnier
2020-07-18 8:22 ` Eli Zaretskii
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=87zh7zrvf6.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=42383@debbugs.gnu.org \
--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 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.