all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Tu Do <tuhdo1710@gmail.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Minibuffer per buffer
Date: Sat, 7 Mar 2015 11:42:59 +0600	[thread overview]
Message-ID: <CAP_d_8UrHaP7Ni8V+xnV3mrC-+P7JfoDQ5erzz9D6x4bLgMoyQ@mail.gmail.com> (raw)
In-Reply-To: <m2twxzvkxa.fsf@fastmail.fm>

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.



  parent reply	other threads:[~2015-03-07  5:42 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 [this message]
2015-03-07  6:43     ` Tu Do

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP_d_8UrHaP7Ni8V+xnV3mrC-+P7JfoDQ5erzz9D6x4bLgMoyQ@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=tuhdo1710@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.