From: Oleh Krehel <ohwoeowho@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Jean Louis <bugs@gnu.support>, emacs-devel@gnu.org
Subject: Re: Could ivy minibuffer stay where it is?
Date: Sat, 07 Nov 2020 13:51:44 +0100 [thread overview]
Message-ID: <86zh3txrbz.fsf@gmail.com> (raw)
In-Reply-To: <87y2je5gof.fsf@tcd.ie>
>> That is it! Definitely good solution.
>>
>> Can that function `ivy-display-function-window' be included in
>> ivy on
>> GNU ELPA?
>
> I don't know, that's Oleh's call. I vaguely remember a
> preference for
> showcasing these potential customisations in the wiki, rather
> than
> maintaining them as part of Ivy, but I'm not sure.
I think `ivy-display-function-window' is not in a good enough
state to be included as part of Ivy. My suggestion right now, if
you want to avoid the minibuffer, is to use
https://github.com/tumashu/ivy-posframe. It's higher quality and
more customizable.
But if someone wants to work on `ivy-display-function-window' to
make it usable, PRs are welcome.
kind regards,
Oleh
next prev parent reply other threads:[~2020-11-07 12:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201104161200.tyeo2r5jibdahukb.ref@Ergus>
2020-11-04 16:12 ` Feature branches review please Ergus
2020-11-04 23:18 ` Basil L. Contovounesios
2020-11-05 8:30 ` Gregory Heytings via Emacs development discussions.
2020-11-05 10:05 ` Jean Louis
2020-11-05 16:10 ` Gregory Heytings via Emacs development discussions.
2020-11-05 16:27 ` Manuel Uberti
2020-11-05 17:00 ` Gregory Heytings via Emacs development discussions.
2020-11-05 17:32 ` Jean Louis
2020-11-05 18:50 ` Stefan Monnier
2020-11-05 19:30 ` Jean Louis
2020-11-05 19:52 ` Eli Zaretskii
2020-11-05 21:55 ` Adam Porter
2020-11-05 22:18 ` hyperscope Jean Louis
2020-11-06 18:18 ` hyperscope Eduardo Ochs
2020-11-06 19:18 ` hyperscope Jean Louis
2020-11-06 5:50 ` Feature branches review please Jean Louis
2020-11-05 20:39 ` Gregory Heytings via Emacs development discussions.
2020-11-05 21:09 ` Ergus
2020-11-05 21:19 ` Gregory Heytings via Emacs development discussions.
2020-11-05 21:36 ` Jean Louis
2020-11-05 21:44 ` Stefan Monnier
2020-11-05 22:00 ` Gregory Heytings via Emacs development discussions.
2020-11-05 22:36 ` Ergus
2020-11-06 8:42 ` Gregory Heytings via Emacs development discussions.
2020-11-05 21:33 ` Jean Louis
2020-11-05 21:46 ` Basil L. Contovounesios
2020-11-05 22:24 ` Gregory Heytings via Emacs development discussions.
2020-11-05 22:48 ` Jean Louis
2020-11-06 9:19 ` Gregory Heytings via Emacs development discussions.
2020-11-06 10:51 ` Feature branches review please (ivy hello) Jean Louis
2020-11-06 11:17 ` Oleh Krehel
2020-11-06 11:42 ` Jean Louis
2020-11-06 11:49 ` Basil L. Contovounesios
2020-11-06 12:01 ` Jean Louis
2020-11-06 21:12 ` Basil L. Contovounesios
2020-11-06 11:57 ` Could ivy minibuffer stay where it is? Jean Louis
2020-11-06 15:20 ` Basil L. Contovounesios
2020-11-06 15:36 ` Jean Louis
2020-11-06 21:17 ` Basil L. Contovounesios
2020-11-07 12:51 ` Oleh Krehel [this message]
2020-11-07 17:23 ` Jean Louis
2020-11-08 11:21 ` Oleh Krehel
2020-11-08 12:51 ` Jean Louis
2020-11-06 13:56 ` Feature branches review please (ivy hello) Stefan Monnier
2020-11-06 14:10 ` Eli Zaretskii
2020-11-06 14:55 ` Stefan Monnier
2020-11-06 15:24 ` Jean Louis
2020-11-06 12:07 ` Gregory Heytings via Emacs development discussions.
2020-11-06 14:02 ` Stefan Monnier
2020-11-06 14:41 ` Gregory Heytings via Emacs development discussions.
2020-11-06 19:23 ` Jean Louis
2020-11-06 21:09 ` Gregory Heytings via Emacs development discussions.
2020-11-15 20:12 ` Feature branches review please Juri Linkov
2020-11-15 22:32 ` Drew Adams
2020-11-06 10:31 ` Alan Mackenzie
2020-11-06 10:55 ` Jean Louis
2020-11-05 17:22 ` Jean Louis
2020-11-05 13:25 ` Andrii Kolomoiets
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=86zh3txrbz.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=bugs@gnu.support \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
/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).