unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Juri Linkov <juri@linkov.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: vertical fido-mode
Date: Fri, 21 Aug 2020 02:05:13 +0200	[thread overview]
Message-ID: <20200821000513.xqdhsdwxm7ov7fkw@Ergus> (raw)
In-Reply-To: <87pn7llbnb.fsf@mail.linkov.net>

On Fri, Aug 21, 2020 at 02:15:36AM +0300, Juri Linkov wrote:

>
>An alternative would be to use the same keys as used in web browsers
>to navigate completions from the url input field where M-up and M-down
>are used to display a list of completions and to navigate in completions,
>without switching to the completions buffer.
>
yes, but this is what we have already in fido and the others somehow. I
wanted to keep things easier.

>
>There are other keys that currently scroll the completions buffer as well:
>M-PgUp, M-PgDown, M-C-v, S-M-C-v.
>
Yes, I know, but I shouldn't be able to change the TAB one. BTW in
terminal S-M-C-v conflicts with terminal yank.

>
>I think whether to show/update completions only on demand or to show/update
>them automatically on input should be customizable with a new option.
>
This is something simple to implement, but again, this something more in
the icompletes-ivy-ido experience.


>> The only addition was the jump to completions with a TAB when all
>> completions are shown.
>
>The existing key that already jumps to completions is PgUp (M-v).
>
Yes but somehow I found more "intuitive" to do it with tab.

>> And exit completions with C-g like in zsh.
>
>The existing key to exit completions is ESC (delete-completion-window).
>
Actually it is ESC ESC ESC. C-g was unbind in the Completions
buffer. Doing C-g (go return to minibuffer) and again C-g (to exit
minibuffer) is shorter and more intuitive than q C-g or ESC ESC ESC.

But don't worry this kind of changes I understand they require
discussion in the ML and are only kind of "proposals" to see reactions.

>> Do you think it worth doing a stronger change?
>
>I think that adding more logic to the existing key TAB is too strong
>change: for example, when the user doesn't notice that the completions
>buffer already displays all completions, types TAB again, and it switches
>to the completions buffer contrary to user wishes.
>
I agree, here. I just ran out of ideas to make it simple and "Intitive"

>OTOH, the feature of using TAB to switch to the completions buffer
>doesn't work when the list of completions is too big and
>not all completions are displayed.
>
Yes this was intentional to avoid changing the defaults.



  reply	other threads:[~2020-08-21  0:05 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
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 [this message]
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=20200821000513.xqdhsdwxm7ov7fkw@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-devel@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).