From: Ergus <spacibba@aol.com>
To: "kevin.legouguec@gmail.com" <kevin.legouguec@gmail.com>,
"dgutov@yandex.ru" <dgutov@yandex.ru>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"juri@linkov.net" <juri@linkov.net>
Subject: Re: vertical fido-mode
Date: Thu, 18 Jun 2020 10:19:32 +0000 (UTC) [thread overview]
Message-ID: <738801972.57184.1592475572083@mail.yahoo.com> (raw)
In-Reply-To: <878sgkzsuv.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
Hi
I agree that this (C-p/C-n && <up> <down>) is the most intuitive in vertical and they shouldn't apply in non-vertical mode (cause <right> <left> is more intuitive then). C-s && C-r could do the same in both cases. For history navegation in vertical M-p and M-n could work fine.
If we want fido fully emulate ido; in the package ido-vertical there is something we could also provide somehow (maybe not exactly in the same way):
| (defun ido-vertical-define-keys () |
| | (when ido-vertical-define-keys |
| | (define-key ido-completion-map (kbd "C-n") 'ido-next-match) |
| | (define-key ido-completion-map (kbd "C-p") 'ido-prev-match) |
| | (define-key ido-completion-map (kbd "C-c C-t") 'ido-toggle-prefix)) |
| | (when (memq ido-vertical-define-keys '(C-n-C-p-up-and-down C-n-C-p-up-down-left-right)) |
| | (define-key ido-completion-map (kbd "<up>") 'ido-prev-match) |
| | (define-key ido-completion-map (kbd "<down>") 'ido-next-match)) |
| | (when (eq ido-vertical-define-keys 'C-n-C-p-up-down-left-right) |
| | (define-key ido-completion-map (kbd "<left>") 'ido-vertical-prev-match) |
| | (define-key ido-completion-map (kbd "<right>") 'ido-vertical-next-match))) |
-----Original Message-----
From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Ergus <spacibba@aol.com>; emacs-devel@gnu.org <emacs-devel@gnu.org>; monnier@iro.umontreal.ca <monnier@iro.umontreal.ca>; Juri Linkov <juri@linkov.net>
Sent: Thu, Jun 18, 2020 10:22 am
Subject: Re: vertical fido-mode
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 18.06.2020 00:50, Juri Linkov wrote:
>> Actually the hardest question is to decide what keys to use
>> to navigate completions in the vertical layout. It would be
>> natural to use arrow keys and M-p/n, but there keys are used
>> for history navigation in the minibuffer.
>
> I think C-n/P-n is what users would expect. See Ivy, Helm, etc.
>
> Arrow keys, too.
As a former Ivy user who went back to icomplete and is now following
this thread with a lot of attention, my vote also goes for C-n/C-p for
next/previous candidate selection, and M-n/M-p for history navigation.
(Actually, I wouldn't mind C-n/C-p in regular (non-vertical) icomplete;
C-. is not super-ergonomic on AZERTY. I liked C-M-i, but it's been
decommissioned in Emacs 27…)
[-- Attachment #2: Type: text/html, Size: 16588 bytes --]
next prev parent reply other threads:[~2020-06-18 10:19 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1704199899.1577092.1591806438580.ref@mail.yahoo.com>
2020-06-10 16:27 ` vertical fido-mode Ergus
2020-06-10 16:53 ` Stefan Monnier
2020-06-10 19:01 ` Dmitry Gutov
2020-06-10 19:45 ` Basil L. Contovounesios
2020-06-10 21:54 ` Ergus
2020-06-10 22:00 ` Dmitry Gutov
2020-06-10 23:08 ` Juri Linkov
2020-06-10 23:23 ` Dmitry Gutov
2020-06-11 13:22 ` Ergus
2020-06-11 13:28 ` Noam Postavsky
2020-06-11 13:40 ` Ergus
2020-06-11 15:49 ` Protesilaos Stavrou
2020-06-11 15:52 ` Omar Antolín Camarena
2020-06-11 17:37 ` Basil L. Contovounesios
2020-06-17 21:50 ` Juri Linkov
2020-06-17 21:57 ` Dmitry Gutov
2020-06-17 22:17 ` João Távora
2020-06-17 22:31 ` Drew Adams
2020-06-17 22:40 ` João Távora
2020-06-17 22:56 ` Drew Adams
2020-06-17 22:52 ` Juri Linkov
2020-06-17 23:20 ` Drew Adams
2020-06-17 22:22 ` Juri Linkov
2020-06-17 22:52 ` Dmitry Gutov
2020-06-17 22:57 ` Dmitry Gutov
2020-06-17 22:58 ` Drew Adams
2020-06-17 23:15 ` Drew Adams
2020-06-18 21:54 ` Juri Linkov
2020-06-18 22:41 ` João Távora
2020-06-18 22:51 ` Juri Linkov
2020-06-19 8:53 ` João Távora
2020-06-18 8:22 ` Kévin Le Gouguec
2020-06-18 10:19 ` Ergus [this message]
2020-06-11 13:10 ` Ergus
2020-08-19 12:17 ` Ergus via Emacs development discussions.
2020-08-20 0:35 ` Juri Linkov
2020-08-20 10:37 ` Ergus
2020-08-20 23:15 ` Juri Linkov
2020-08-21 0:05 ` Ergus
2020-08-23 18:45 ` Juri Linkov
2020-08-24 19:06 ` vertical fido-mode (new branch) Ergus via Emacs development discussions.
2020-08-25 18:55 ` Juri Linkov
2020-08-25 23:11 ` Ergus
2020-08-25 23:42 ` Stefan Monnier
2020-08-26 4:34 ` Ergus
2020-08-26 13:30 ` Stefan Monnier
2020-08-28 10:09 ` Ergus
2020-06-10 19:45 ` vertical fido-mode Basil L. Contovounesios
2020-06-11 0:55 Omar Antolín Camarena
2020-06-11 13:03 ` Ergus
2020-06-11 13:44 ` Omar Antolín Camarena
2020-06-11 14:07 ` Ergus
2020-06-11 17:29 ` Basil L. Contovounesios
2020-06-18 13:51 ` Stefan Monnier
2020-06-29 14:44 ` Ergus
[not found] <mailman.50.1591891219.14559.emacs-devel@gnu.org>
2020-06-11 17:06 ` Andrew Schwartzmeyer
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=738801972.57184.1592475572083@mail.yahoo.com \
--to=spacibba@aol.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=kevin.legouguec@gmail.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 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).