From: Gregory Heytings via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: 43572@debbugs.gnu.org
Subject: bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones
Date: Thu, 24 Sep 2020 08:06:37 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2009240947240453.11676@sdf.lonestar.org> (raw)
In-Reply-To: <jwvh7roq66w.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
To illustrate the need for this feature, I attach four screenshots taken
under the exact same conditions.
- "vanilla.png" is what a user would see without changing any default
(after pressing TAB to display the completion candidates): the prompt,
their input, and completion candidates in a *Completions* buffer above the
minibuffer
- "master-icomplete-vertical-after-tab.png" is what a user would see with
icomplete-mode activated and (setq icomplete-separator "\n") after having
completed the last directory name with a TAB: the prompt and their input
is completely hidden
- "master-icomplete-vertical-after-tab-tab.png" is what a user would see
after pressing TAB a second time; note the "ng/" before point, which was
hidden after pressing TAB for the first time and is now visible again
- "patched-icomplete-vertical.png" is what a user would see with the
proposed patch
[-- Attachment #2: Type: image/png, Size: 50216 bytes --]
[-- Attachment #3: Type: image/png, Size: 28832 bytes --]
[-- Attachment #4: Type: image/png, Size: 62417 bytes --]
[-- Attachment #5: Type: image/png, Size: 35481 bytes --]
next prev parent reply other threads:[~2020-09-24 8:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:57 bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 15:17 ` Eli Zaretskii
2020-09-23 19:15 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 19:37 ` Eli Zaretskii
2020-09-23 20:15 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 14:24 ` Eli Zaretskii
2020-09-24 14:41 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 15:11 ` Eli Zaretskii
2020-09-24 16:09 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:20 ` Eli Zaretskii
2020-09-24 16:40 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 17:03 ` Eli Zaretskii
2020-09-24 21:51 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 6:59 ` Eli Zaretskii
2020-09-25 8:34 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 9:14 ` Eli Zaretskii
2020-09-25 10:14 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 11:17 ` Eli Zaretskii
2020-09-25 11:34 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 22:59 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 18:31 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 18:33 ` Stefan Monnier
2020-09-23 18:47 ` Eli Zaretskii
2020-09-23 23:18 ` Stefan Monnier
2020-09-24 14:34 ` Eli Zaretskii
2020-09-24 16:44 ` Stefan Monnier
2020-09-24 16:59 ` Eli Zaretskii
2020-09-27 21:59 ` Stefan Monnier
2020-09-28 6:20 ` Eli Zaretskii
2020-09-28 13:30 ` Stefan Monnier
2020-09-28 13:44 ` Eli Zaretskii
2020-09-28 16:58 ` Stefan Monnier
2020-10-02 15:40 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 16:08 ` Stefan Monnier
2020-10-02 16:11 ` Eli Zaretskii
2020-10-02 16:25 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 19:30 ` Eli Zaretskii
2020-10-02 21:49 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 14:02 ` Lars Ingebrigtsen
2020-09-23 19:46 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 20:00 ` Stefan Monnier
2020-09-23 22:47 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 23:20 ` Stefan Monnier
2020-09-23 23:26 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 2:07 ` Stefan Monnier
2020-09-24 7:45 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:26 ` Stefan Monnier
2020-09-24 8:06 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-09-24 14:43 ` Eli Zaretskii
2020-09-24 14:52 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 15:20 ` Eli Zaretskii
2020-09-24 14:26 ` Eli Zaretskii
2020-09-24 14:20 ` Eli Zaretskii
2020-09-24 14:27 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:40 ` Stefan Monnier
2020-09-24 16:54 ` Eli Zaretskii
2020-09-27 16:11 ` Eli Zaretskii
2020-09-27 21:52 ` Stefan Monnier
2020-09-28 6:10 ` Eli Zaretskii
2020-09-28 13:24 ` Stefan Monnier
2020-09-28 13:42 ` Eli Zaretskii
2020-09-28 16:56 ` Stefan Monnier
[not found] <<alpine.NEB.2.22.394.2009222215560453.32542@sdf.lonestar.org>
[not found] ` <<jwvwo0ktlge.fsf-monnier+emacs@gnu.org>
[not found] ` <<alpine.NEB.2.22.394.2009232116430453.29439@sdf.lonestar.org>
[not found] ` <<834knnuugm.fsf@gnu.org>
[not found] ` <<jwvimc3p2a0.fsf-monnier+emacs@gnu.org>
[not found] ` <<83h7rnt8s3.fsf@gnu.org>
[not found] ` <<833633nqru.fsf@gnu.org>
[not found] ` <<jwvwo0e6gcb.fsf-monnier+emacs@gnu.org>
[not found] ` <<83r1qmmnxu.fsf@gnu.org>
2020-09-28 15:53 ` Drew Adams
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=alpine.NEB.2.22.394.2009240947240453.11676@sdf.lonestar.org \
--to=bug-gnu-emacs@gnu.org \
--cc=43572@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ghe@sdf.org \
--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).