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: Drew Adams <drew.adams@oracle.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: feature/completions-highlight-modifications e3c5b99 3/6: Add completions-highlight-mode initial implementation.
Date: Thu, 19 Nov 2020 04:25:19 +0100	[thread overview]
Message-ID: <20201119032519.lpa53ixezgpdppze@Ergus> (raw)
In-Reply-To: <87d00acuh3.fsf@mail.linkov.net>

Hi Juri:

I made some of the changes you suggested, I think the behavior is a bit
more reliable now. 

On Wed, Nov 18, 2020 at 09:43:28PM +0200, Juri Linkov wrote:
>> The code is extremely simple, so, if you think you could improve
>> anything it is more tan welcome.
>
>The branch contains many different features with different problems,
>so here is a short summary for these 4 separate features:
>
>1. feature of setting minibuffer-tab-through-completions-function to
>   completions-highlight-minibuffer-tab-through-completions:
>
>The problem is that such TAB cycling is limited only to the case
>when the whole *Completions* buffer is visible.
>
This was as I said intentional. And to change that could be relatively
easy but I am not 100% we should. Maybe with a custom in the future...

>The original behavior of multiple presses of TAB is limited too:
>its browsing is uni-directional, there is no way to use S-TAB
>to scroll completions backwards.
>
>So I don't see how relying on TAB could improve navigation in completions.
>
>2. completion-set-suffix sometimes doesn't work;
>
I think it is fixed now.

>3. commands that dispatch navigation keys from the minibuffer to the
>   *Completions* buffer: this doesn't cover other navigation keys.
>
>Maybe like windmove-default-keybindings defines modifiers,
>a similar function could set up modifiers for scrolling completions
>from the minibuffer, then the users could choose whether to use
>e.g. 'M-' modifier for scrolling completions, or no modifier at all.
>
I will try that when have some time.

>4. the feature of using completions-highlight-overlay often fails to
>   update highlighting when point is moved in the *Completions* buffer
>   by other navigation commands.
>
>To fix this, it could work like hl-line-mode, but instead of
>highlighting the whole line, it could highlight only completions.
>
Done.

I didn't use the post-command-hook before because I didn't know about it
when I started and then I forgot to fix that. Please give it a try now.

>Then completion highlighting would be useful on its own.
>A new defcustom e.g. 'completion-highlight' (disabled by default)
>could add a post-command-hook like hl-line-mode does.
>Then other completion commands could enable this variable locally.

I made this on the beginning, but I didn't want to add more code to
simple.el...

Maybe not a custom but a minor mode is better and simpler. It is just to
divide my current code in two minor modes instead of just one.

I will consider that...



  parent reply	other threads:[~2020-11-19  3:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201115023629.19537.77471@vcs0.savannah.gnu.org>
     [not found] ` <20201115023631.C78AB20A27@vcs0.savannah.gnu.org>
2020-11-15 18:41   ` feature/completions-highlight-modifications e3c5b99 3/6: Add completions-highlight-mode initial implementation Stefan Monnier
2020-11-15 22:49     ` Ergus
2020-11-15 23:32       ` Stefan Monnier
2020-11-16  3:37         ` Ergus
2020-11-16  3:56           ` Stefan Monnier
2020-11-16  5:40             ` Drew Adams
2020-11-16  7:39             ` Ergus
2020-11-16  5:38           ` Drew Adams
2020-11-16  8:54             ` Juri Linkov
2020-11-16 10:27               ` Ergus
2020-11-16 20:23                 ` Juri Linkov
2020-11-16 21:16                   ` Drew Adams
2020-11-17  0:46                   ` Ergus
2020-11-17 20:02                     ` Juri Linkov
2020-11-17 20:52                       ` Drew Adams
2020-11-18 19:43                 ` Juri Linkov
2020-11-18 22:45                   ` Drew Adams
2020-11-19  3:25                   ` Ergus [this message]
2020-11-19  7:45                     ` Juri Linkov
2020-11-19 10:50                       ` Ergus
2020-11-20  9:32                         ` Juri Linkov
     [not found]                           ` <20201120145248.wmbv2zgbvs7bg25i@Ergus>
2020-11-21 19:30                             ` Juri Linkov
2020-11-22 13:28                               ` Ergus
2020-11-22 20:03                                 ` Juri Linkov
2020-11-22 23:09                               ` Ergus
2020-11-23  9:14                                 ` Juri Linkov
2020-11-23 11:46                                   ` Ergus
2020-11-23 14:13                                     ` Jean Louis
2020-11-23 19:12                                       ` Eli Zaretskii
2020-11-23 19:44                                         ` Jean Louis
2020-11-23 20:54                                     ` Dmitry Gutov
2020-11-23 23:27                                       ` Ergus via Emacs development discussions.
2020-12-10  1:16                                         ` Dmitry Gutov
2020-12-10  8:23                                           ` Juri Linkov
2020-11-25  8:49                                     ` Juri Linkov
2020-11-20 14:24                         ` Stefan Monnier
     [not found]                           ` <20201120144940.p55brblxpuowslag@Ergus>
2020-11-20 15:15                             ` Stefan Monnier
2020-11-16 16:03               ` Drew Adams
2020-11-16 20:28                 ` Juri Linkov
2020-11-16 21:31                   ` Drew Adams
2020-11-18 19:30                   ` 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=20201119032519.lpa53ixezgpdppze@Ergus \
    --to=spacibba@aol.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --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).