From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 55800@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#55800: using rgrep function interactively with fido-mode or fido-vertical-mode causes errors
Date: Mon, 13 Jun 2022 18:13:54 +0300 [thread overview]
Message-ID: <CAJddU=p8eg9bT7CM8RkrGtbp9q5OdpFbK3Wg04M9nBNKXJemuA@mail.gmail.com> (raw)
In-Reply-To: <867d5lau4j.fsf@mail.linkov.net>
Thanks Juri. I think this is much better behaviour.
On Mon, Jun 13, 2022 at 10:43 AM Juri Linkov <juri@linkov.net> wrote:
>
> >> So maybe fido-mode could be fixed to always provide the default value
> >> as the first highlighted candidate? Then RET will select it.
> >
> > Another part of the problem is still unsolved and the question still is:
> > shouldn't fido-mode bubble the default value to the top of the list
> > even when the default value doesn't exist in the list of completion
> > candidates? This is the same question as was asked in
> > https://debbugs.gnu.org/38992#76
>
> It seems there is no way to change the behaviour of fido-mode,
> so what remains to do is to add the default values to the completion list
> only in rgrep, then fido-mode will highlight the default at the top:
>
next prev parent reply other threads:[~2022-06-13 15:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 1:11 bug#55800: using rgrep function interactively with fido-mode or fido-vertical-mode causes errors Yilkal Argaw
2022-06-05 5:45 ` Eli Zaretskii
2022-06-05 7:15 ` Yilkal Argaw
2022-06-05 7:20 ` Yilkal Argaw
2022-06-05 9:46 ` Eli Zaretskii
[not found] ` <CAJddU=ot4BHXmtW6jFGFniz8KcyPo=_2JLXNK9cQUAPiOFvSTg@mail.gmail.com>
2022-06-05 13:02 ` Eli Zaretskii
2022-06-05 13:25 ` Yilkal Argaw
2022-06-08 7:19 ` Juri Linkov
2022-06-09 11:11 ` Yilkal Argaw
2022-06-09 17:09 ` Juri Linkov
2022-06-10 3:34 ` Yilkal Argaw
2022-06-10 7:58 ` Juri Linkov
2022-06-12 18:24 ` Juri Linkov
2022-06-13 7:20 ` Juri Linkov
2022-06-13 15:13 ` Yilkal Argaw [this message]
2022-06-13 17:20 ` Juri Linkov
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='CAJddU=p8eg9bT7CM8RkrGtbp9q5OdpFbK3Wg04M9nBNKXJemuA@mail.gmail.com' \
--to=yilkalargawworkneh@gmail.com \
--cc=55800@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).