unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Gregory Heytings <gregory@heytings.org>
Cc: emacs-devel@gnu.org, Juri Linkov <juri@linkov.net>
Subject: Re: icomplete-vertical above prompt
Date: Mon, 12 Apr 2021 12:37:10 +0300	[thread overview]
Message-ID: <YHQUxvwAlCOLB39t@protected.localdomain> (raw)
In-Reply-To: <3755fe92dcc24a345c43@heytings.org>

* Gregory Heytings <gregory@heytings.org> [2021-04-12 02:03]:
> 
> > 
> > Regardless of the value of icomplete-vertical-mode-above-prompt, in both
> > cases it jumps once, and that's the problem for users who don't like
> > such jumps, even once.
> > 
> 
> I'm not sure I understand what you mean.  How could you display completion
> candidates without moving the modeline?  I suppose what you have in mind is
> posframes?  But posframes are a completely different beast, and don't work
> in terminals AFAIK.
> 
> For that matter, I also don't understand why users "don't like such jumps
> even once".  The point is to make some room to display some information, the
> same happens in many cases, like when *Completions* is opened, or with
> popular packages such as Magit or which-key.

For me mode line is always static as by impression, standard
completion does not jerk it up and only completion packages do
that. First completion I was using was helm and it did not fiddle with
the mode line. Great. Until I found ivy and others who do that. IMHO
best representation is when a small window appears with candidates
above the mode line, or even full screen in some cases.

Jerking mode line up down is not in harmony with the description of
mode line in the manual.

File: emacs.info,  Node: Mode Line,  Next: Menu Bar,  Prev: Echo Area,  Up: Screen

1.3 The Mode Line
=================

At the bottom of each window is a “mode line”, which describes what is
going on in the current buffer.  When there is only one window, the mode
line appears right above the echo area; it is the next-to-last line in
the frame.

Non-jerked mode line offers better accessibility.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/




      parent reply	other threads:[~2021-04-12  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 14:58 icomplete-vertical above prompt Gregory Heytings
2021-04-11 15:11 ` Gregory Heytings
2021-04-11 21:59 ` Juri Linkov
2021-04-11 23:02   ` Gregory Heytings
2021-04-11 23:19     ` Juri Linkov
2021-04-11 23:25       ` Gregory Heytings
2021-04-11 23:34         ` Juri Linkov
2021-04-11 23:41           ` Ergus
2021-04-12  9:37     ` Jean Louis [this message]

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=YHQUxvwAlCOLB39t@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.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).