From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.devel Subject: Re: The future of Follow Mode - a proposal. Date: Thu, 18 Feb 2016 15:41:22 -0500 Message-ID: References: <20160218195630.GA2697@acm.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b6785b4b5a6ca052c1163a8 X-Trace: ger.gmane.org 1455828108 23220 80.91.229.3 (18 Feb 2016 20:41:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Feb 2016 20:41:48 +0000 (UTC) Cc: Anders Lindgren , Emacs developers To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 18 21:41:45 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aWVOS-0003UW-PY for ged-emacs-devel@m.gmane.org; Thu, 18 Feb 2016 21:41:44 +0100 Original-Received: from localhost ([::1]:45401 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWVOP-0007hl-4V for ged-emacs-devel@m.gmane.org; Thu, 18 Feb 2016 15:41:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44811) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWVO9-0007fy-0p for emacs-devel@gnu.org; Thu, 18 Feb 2016 15:41:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aWVO7-0000sA-M9 for emacs-devel@gnu.org; Thu, 18 Feb 2016 15:41:24 -0500 Original-Received: from mail-pa0-x22c.google.com ([2607:f8b0:400e:c03::22c]:36303) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWVO7-0000s4-EQ for emacs-devel@gnu.org; Thu, 18 Feb 2016 15:41:23 -0500 Original-Received: by mail-pa0-x22c.google.com with SMTP id yy13so36814691pab.3 for ; Thu, 18 Feb 2016 12:41:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=df/M+EKHOa+JI3b9sDR/TKfZhqZfoGuCpxI1wOo3nJ0=; b=dA8+L0mmziuTHJcNjLbQtBZvkj2RvvnU+Ag23ajsVEAJJ/LDUSDGvvXPrOlKq9bE2H arBi+3OrsbGSVkCUkG5P4PM+iaVux9ex62mPQGF4dTkgeYcgK7Sgog5NNkgYBOwE0yzA 8M7r8ydTZ1/xw/BCwWKoVQ1+O2Cl+IXRdBjZ0ZZa8bUgM8DU1skRq3YO+5Ye0eASdmel 32h+whyY0vy7vB910fulqOAKF0V4KL0xXhhOpsckRwf691dJAugs4Z/JVgi7mVu0eNXB SaxbNBDS7N7c68vme/BASp6fBZFeOGzzu+CgGjehrmQCvJu3rh5ncsVOzWvsPAzCp1C6 NH6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=df/M+EKHOa+JI3b9sDR/TKfZhqZfoGuCpxI1wOo3nJ0=; b=PH4fJWWPRnv7bNYu3e25choC/RIkSuO3LfYYCVhgfmc7XwPBdTZXx/GHdL89GJ7fi8 azhYPVItVrdVpklwLZ0WRlTQbvRx4K63s+tB35jj+draPevX38/6Y26Xrzx7wmGqyVIx 6p5xRqcWvhuxh7uktIKR+PdECk8X4NAay+D2g7Cvqgm8dKloP5LH0eZ+Hq9keuU7lPgt Yam5Uk47ujFc/trBKGfhC0E7oQzxST2Kt5qDhYgLmmHINc/wCMZzf6EAW5x+h4Lkt7CE nF1jRhrpiW77/3wrmivp2tXbQBorhmJVuK2CghGp1jgOQRjHVyZXEQittqDhnXcexExY mwkA== X-Gm-Message-State: AG10YOR7dQMF3QF04mEBGuuFVX2dJ52aZ16KvHrwoY71ZmHFmQQQ8jB6j0MEpuRzeNsd//pxrMNt07xN8dS6fg== X-Received: by 10.66.146.196 with SMTP id te4mr13007829pab.125.1455828082466; Thu, 18 Feb 2016 12:41:22 -0800 (PST) Original-Received: by 10.66.246.137 with HTTP; Thu, 18 Feb 2016 12:41:22 -0800 (PST) In-Reply-To: <20160218195630.GA2697@acm.fritz.box> X-Google-Sender-Auth: nMTK-kGf9HzEuXi-0lmx-TSmxfQ X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400e:c03::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200158 Archived-At: --047d7b6785b4b5a6ca052c1163a8 Content-Type: text/plain; charset=UTF-8 On Thu, Feb 18, 2016 at 2:56 PM, Alan Mackenzie 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 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. /john --047d7b6785b4b5a6ca052c1163a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Feb 18, 2016 at 2:56 PM, Alan Mackenzie <acm@muc.de> wrote:
There may be better ways to achieve the si= ngle 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.=C2=A0 OTOH I ha= ve often wanted to put the mode line at
of my windows.=C2=A0 Ther= e are some hacks out on the web that approximate
such behavior.= =C2=A0 They do so by usurping the header line, thereby breaking
v= arious modes.

Putting the mode line at the top of = the window is especially desirable on
large, high resolution scre= ens.=C2=A0 When a buffer's contents does not fill
a vertical = window there can be a large expanse of blank space between
EOB an= d that window's mode line.

/john
--047d7b6785b4b5a6ca052c1163a8--