unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Evgeny Roubinchtein <zhenya1007@gmail.com>,
	 Emacs Development <emacs-devel@gnu.org>
Subject: Re: Minibuffer positioned at a location other than the bottom of the frame?
Date: Tue, 21 Nov 2017 10:27:54 +0100	[thread overview]
Message-ID: <5A13F19A.9000502@gmx.at> (raw)
In-Reply-To: <CAGYXaSZLy=kMFFQqPzHcJzn1jvaQZHROKF8j68yJH8=V6ZW_sA@mail.gmail.com>

 > Has any consideration been given to having the option of displaying the
 > minibuffer window somewhere other than the bottom of the frame?

No, because ...

 > For
 > example, if I have a frame split horizontally with bufferA on top and
 > bufferB at the bottom, and I do an isearch in bufferA, it might (arguably)
 > be nice to have the minibuffer window appear below bufferA's mode line, as
 > opposed to below bufferB's mode line.

... if you now decide to delete the window showing bufferA, where would
the minibuffer window move to?  Keeping the minibuffer window constantly
below a frame's selected window, for example, could be very annoying
because the window configuration would change continuously.  Moving it
to the window where a user interaction via the minibuffer is initiated
as well.  So ...

 > moving a separate minibuffer frame to
 > achieve something similar,

... seems indeed the only practicable way to do what you want.

martin



  reply	other threads:[~2017-11-21  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 21:24 Minibuffer positioned at a location other than the bottom of the frame? Evgeny Roubinchtein
2017-11-21  9:27 ` martin rudalics [this message]
2017-11-21 15:49   ` Eli Zaretskii
2017-11-25 14:43     ` John Yates
2017-11-25 16:05       ` Eli Zaretskii
2017-11-26 10:26         ` martin rudalics
2017-11-26 16:01           ` Eli Zaretskii
2017-11-27  8:49             ` martin rudalics
2017-11-26 16:29       ` Yuri Khan
2017-11-26 18:55         ` John Yates
2017-11-26 23:00       ` very large displays Stephen Leake

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=5A13F19A.9000502@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=zhenya1007@gmail.com \
    /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).