From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#38992: 27.0.60; when enabled, fido-mode seems to break vc-git-grep Date: Thu, 23 Jan 2020 16:51:31 +0000 Message-ID: References: <288610218.111246.1578330546916@office.mailbox.org> <780526337.114357.1578556168662@office.mailbox.org> <944631362.128066.1578605073103@office.mailbox.org> <98df50d8-44fb-448e-e893-f20601f1ca54@yandex.ru> <51d12435-274b-be14-95b8-f790804f1a61@yandex.ru> <157c6af1-c900-188d-490c-4f48ea17da3d@yandex.ru> <5dc9535d-9b2f-56f1-2e63-b75ff3aaaf55@yandex.ru> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000aeba98059cd17412" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="21723"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 38992@debbugs.gnu.org, waah@yellowfrog.io, Dmitry Gutov To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jan 23 20:48:31 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iuiSs-0005Zj-B9 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 23 Jan 2020 20:48:30 +0100 Original-Received: from localhost ([::1]:60558 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iuiSr-0008Rr-8y for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 23 Jan 2020 14:48:29 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43520) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iufi7-0000wl-H1 for bug-gnu-emacs@gnu.org; Thu, 23 Jan 2020 11:52:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iufi6-0002ts-AG for bug-gnu-emacs@gnu.org; Thu, 23 Jan 2020 11:52:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:47131) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iufi6-0002th-3k for bug-gnu-emacs@gnu.org; Thu, 23 Jan 2020 11:52:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iufi6-0005MS-2M for bug-gnu-emacs@gnu.org; Thu, 23 Jan 2020 11:52:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 23 Jan 2020 16:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38992 X-GNU-PR-Package: emacs Original-Received: via spool by 38992-submit@debbugs.gnu.org id=B38992.157979831120593 (code B ref 38992); Thu, 23 Jan 2020 16:52:02 +0000 Original-Received: (at 38992) by debbugs.gnu.org; 23 Jan 2020 16:51:51 +0000 Original-Received: from localhost ([127.0.0.1]:53104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iufhv-0005M3-01 for submit@debbugs.gnu.org; Thu, 23 Jan 2020 11:51:51 -0500 Original-Received: from mail-qv1-f51.google.com ([209.85.219.51]:42796) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iufhs-0005Lq-Q1 for 38992@debbugs.gnu.org; Thu, 23 Jan 2020 11:51:49 -0500 Original-Received: by mail-qv1-f51.google.com with SMTP id dc14so1781279qvb.9 for <38992@debbugs.gnu.org>; Thu, 23 Jan 2020 08:51:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HfMjjbwU88WzbhrRasEP8GFks5xuVSDB+xQXZeBypwg=; b=WEZB/HKwB+jI0zmPyolAoV70phe3NdiJm4cFGW9uyx6cdXIUth6Eq7wg1NXDElfhdw /sQd1x24ZULqs4yq54fIIgfa/iOmRNZx5HZrMqnZV5JYi4jDhgqx0EpW2eFYciQpG9JP FrqPTuxnbA6a6JmfMx3Kd67vZpB42s272Di3UFFXh95R+zTxuuiRXdHXxfm08nxQnvEU js2+XZnUEjFMMiLst4qNT67adg4W6Qvo5iXX1mXJpxGBIy+RwCrX3aHdvxYG0I0jROwG 4JN9YvoteUcq2F2bLNarBgxRXi4Gg5KL8YgkFnDu2bzJmtNyaIxy63ezH/aLwCAMzwq+ sENw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HfMjjbwU88WzbhrRasEP8GFks5xuVSDB+xQXZeBypwg=; b=rTl25XtxFhiBerQsva/QNve8KOLlQwXLMYdp8p27kPk7YniuP0gWhAOrXa7Lxr3i3D WFXbbn0YbGf7n+ByF0m5MR0mxMebCERsUzu0d0tlNcMwxaWM197cC2/4p+S3KYlR18sr k6b+aW/qUWEF7AfO0Si15HSPMfHmOQvleVEF0+lfhMKNaq2Y44RGcHoeB45E8r3XKpYn d7fCjT+mYtx0aGdrGfIQ3A6iaVt68ldEDvZyIvxf5KoZR3rvYugg2lnt3nbtqAhtVwEV eRC7SnfJNanurNr70krGQughLf/9OiImSJSVOJmVc8UzFfZuDE/8EWawOQFJrUA4I44m PS3g== X-Gm-Message-State: APjAAAXn6iHO8Z/uncH2r8KANA/Xls0a0O10PZzFz0YRrvYo+2k0XX9B TV0Ye9go7EPRFwapXkKknK9zkFBdWrt3DRAPVgg= X-Google-Smtp-Source: APXvYqwd/sgHhemJ3iy4UBxxmakO+x1BJuAad9rNud+S/gRxa9kfZ79xwJPESblbNgpk2eel+ypMeP1HvmX7KsQeI1A= X-Received: by 2002:a0c:f7c3:: with SMTP id f3mr17098147qvo.52.1579798303255; Thu, 23 Jan 2020 08:51:43 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:175180 Archived-At: --000000000000aeba98059cd17412 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 23, 2020 at 4:28 PM Stefan Monnier wrote: > > >> Good point: `minibuffer-force-complete-and-exit` probably needs to be > >> changed accordingly (i.e. to just `exit-minibuffer` when `required` > >> was nil). > > How will it determine that? minibuffer-completion-confirm seems to be the > > same whether require-match is t or not. > > We could introduce a new `minibuffer-require-match` variable (and mark > `minibuffer-completion-confirm` obsolete). +1. Not particularly pretty, but it would you join the ranks of many other `minibuffer-*` special variables that hold these kinds of things. -- Jo=C3=A3o T=C3=A1vora --000000000000aeba98059cd17412 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jan 23, 2020 at 4:28 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote= :
>
> >> Good point: `minibuffer-force-complete-and-exit`= probably needs to be
> >> changed accordingly (i.e. to just `e= xit-minibuffer` when `required`
> >> was nil).
> > How= will it determine that? minibuffer-completion-confirm seems to be the
&= gt; > same whether require-match is t or not.
>
> We could i= ntroduce a new `minibuffer-require-match` variable (and mark
> `= minibuffer-completion-confirm` obsolete).

+1. Not particularl= y pretty, but it would you join the ranks of many
other `min= ibuffer-*` special variables that hold these kinds of things.
--
Jo=C3=A3o T=C3=A1vora
--000000000000aeba98059cd17412--