From: Eli Zaretskii <eliz@gnu.org>
To: John Yates <john@yates-sheets.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: The future of Follow Mode - a proposal.
Date: Fri, 19 Feb 2016 22:27:28 +0200 [thread overview]
Message-ID: <83bn7cqwcv.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXoi21Hs=7q7hcohRYnmBobA2L7BY3DMTmm9gW0mzaF+6nQ@mail.gmail.com> (message from John Yates on Fri, 19 Feb 2016 14:25:10 -0500)
> Date: Fri, 19 Feb 2016 14:25:10 -0500
> From: John Yates <john@yates-sheets.org>
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> This may seem heretical but I would move the mini-buffer to the topof
> the frame. I can already approximate such a layout using a separate
> mini-buffer frame and the _NET_WM_STRUT_PARTIAL property.
>
> Ideally there would be a frame parameter that would allow me to specify
> that the mini-buffer should be positioned at the top of the frame.
>
> My motivation here is that I have a single, large, very high resolution
> screen. I maintain a set of tall, horizontally arrayed windows. I advise
> split-window and delete-window to keep all windows balanced. Since
> these windows are so tall very often they are only partially filled. The
> net effect is that interesting content is concentrated at the top of my
> screen. That being the case needing to look to the bottom of the
> screen to inspect the mode-line and/or mini-buffer only slows me down.
> I would be much happier if I could have:
> * the mini-buffer at the top of its frame
> * the mode-line at the top of its window
It might be much easier to make text display at the bottom of a
window. Have you considered that possibility?
prev parent reply other threads:[~2016-02-19 20:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:56 The future of Follow Mode - a proposal Alan Mackenzie
2016-02-18 20:24 ` Eli Zaretskii
2016-02-19 14:25 ` Alan Mackenzie
2016-02-19 14:34 ` martin rudalics
2016-02-19 16:12 ` Eli Zaretskii
2016-02-19 16:08 ` Eli Zaretskii
2016-02-19 18:18 ` Alan Mackenzie
2016-02-19 18:45 ` Eli Zaretskii
2016-02-20 12:44 ` Alan Mackenzie
2016-02-20 13:05 ` Eli Zaretskii
2016-02-23 23:11 ` Alan Mackenzie
2016-02-24 3:57 ` Stefan Monnier
2016-02-24 17:14 ` Eli Zaretskii
2016-02-24 18:57 ` Stefan Monnier
2016-02-24 19:19 ` Eli Zaretskii
2016-02-24 20:10 ` Stefan Monnier
2016-02-24 20:21 ` Eli Zaretskii
2016-02-25 0:30 ` Stefan Monnier
2016-02-25 16:28 ` Eli Zaretskii
2016-02-25 16:46 ` Stefan Monnier
2016-02-25 17:29 ` Eli Zaretskii
2016-02-25 20:30 ` Alan Mackenzie
2016-02-25 20:57 ` Alan Mackenzie
2016-02-25 21:10 ` Stefan Monnier
2016-02-25 22:17 ` Alan Mackenzie
2016-02-28 16:40 ` Stefan Monnier
2016-02-24 18:34 ` Eli Zaretskii
2016-02-25 20:18 ` Alan Mackenzie
2016-02-19 14:56 ` Anders Lindgren
2016-02-19 16:30 ` Eli Zaretskii
2016-02-19 18:45 ` Alan Mackenzie
2016-02-18 20:41 ` John Yates
2016-02-19 16:21 ` Alan Mackenzie
2016-02-19 16:32 ` Eli Zaretskii
2016-02-19 19:25 ` John Yates
2016-02-19 20:27 ` Eli Zaretskii [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=83bn7cqwcv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.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).