From: Tu Do <tuhdo1710@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>, fgunbin@fastmail.fm, joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Minibuffer per buffer
Date: Sat, 7 Mar 2015 13:43:52 +0700 [thread overview]
Message-ID: <CAOEd9jmATrBcRpAAN4aAgjrsH7xZKm3Zk-oKkkzdFYuk1qBeCQ@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8UrHaP7Ni8V+xnV3mrC-+P7JfoDQ5erzz9D6x4bLgMoyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
I just want to mention this issue to make it a feature request in the
wishlist. Using frame as another minibuffer is not always nice because we
have another OS window floating around. And it can't be used in the
terminal.
On Sat, Mar 7, 2015 at 12:42 PM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Thu, Mar 5, 2015 at 3:43 PM, Filipp Gunbin <fgunbin@fastmail.fm> wrote:
> > On 05/03/2015 11:47 +0700, Tu Do wrote:
> >> As monitor becomes larger with higher resolution (i.e. 4k monitor), I
> think it would be beneficial to have an option to activate minibuffer
> >> per buffer.
>
> The motivation, as I understand it, is to bring the minibuffer closer
> to the focus of user’s attention, which is in the selected window.
>
> An easy workaround is to use multiple frames (perhaps with a tiling
> window manager), each of which would by default have a minibuffer.
>
> I actually do this with a pre-4k (24″ 16:10 1920×1200) monitor,
> splitting it into left and right halves. When working on code, I
> frequently have both halves occupied with Emacs frames (each of which
> may be further split into the top and bottom windows).
>
> > Where should echo messages (including not related to the current buffer)
> > be displayed in this case?
>
> This can probably be solved the same way they choose a minibuffer when
> multiple frames are involved.
>
[-- Attachment #2: Type: text/html, Size: 1853 bytes --]
prev parent reply other threads:[~2015-03-07 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 4:47 Minibuffer per buffer Tu Do
2015-03-05 8:33 ` joakim
2015-03-05 9:43 ` Filipp Gunbin
2015-03-07 5:29 ` Alexis
2015-03-07 5:42 ` Yuri Khan
2015-03-07 6:43 ` Tu Do [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=CAOEd9jmATrBcRpAAN4aAgjrsH7xZKm3Zk-oKkkzdFYuk1qBeCQ@mail.gmail.com \
--to=tuhdo1710@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=joakim@verona.se \
--cc=yuri.v.khan@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).