all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: John Yates <john@yates-sheets.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: The future of Follow Mode - a proposal.
Date: Fri, 19 Feb 2016 16:21:59 +0000	[thread overview]
Message-ID: <20160219162159.GB3193@acm.fritz.box> (raw)
In-Reply-To: <CAJnXXogCcjO7gFtskOV66f2fhXL5sqCbG3NkWR+vhW3ViU0GJQ@mail.gmail.com>

Hello, John.

On Thu, Feb 18, 2016 at 03:41:22PM -0500, John Yates wrote:
> On Thu, Feb 18, 2016 at 2:56 PM, Alan Mackenzie <acm@muc.de> wrote:

> > There may be better ways to achieve the single mode line, but one way
> > would be to implement mode lines as windows in their own right, thus giving
> > them scope to be somewhere else other than squashed up into a window's last
> > line.


> I have yet to use FM.  OTOH I have often wanted to put the mode line
> at [the top] of my windows.  There are some hacks out on the web that
> approximate such behavior.  They do so by usurping the header line,
> thereby breaking various modes.

> Putting the mode line at the top of the window is especially desirable on
> large, high resolution screens.  When a buffer's contents does not fill
> a vertical window there can be a large expanse of blank space between
> EOB and that window's mode line.

I don't think this would be too difficult to implement, as a hack, and
would be a good learning exercise for the display code.  One problem I
foresee is that there would no longer be anything to separate the main
window area from the minibuffer.  Have you any thoughts on how this
would be handled?

> /john

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2016-02-19 16:21 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 [this message]
2016-02-19 16:32     ` Eli Zaretskii
2016-02-19 19:25     ` John Yates
2016-02-19 20:27       ` Eli Zaretskii

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=20160219162159.GB3193@acm.fritz.box \
    --to=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 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.