unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51590@debbugs.gnu.org, juri@linkov.net
Subject: bug#51590: follow-mode is broken with header-line and tab-line
Date: Sun, 7 Nov 2021 14:28:07 +0000	[thread overview]
Message-ID: <YYfid0bniqj2FoJt@ACM> (raw)
In-Reply-To: <83tugo85wa.fsf@gnu.org>

Hello, Eli.

On Sun, Nov 07, 2021 at 15:14:13 +0200, Eli Zaretskii wrote:
> > Date: Sun, 7 Nov 2021 12:48:22 +0000
> > Cc: Eli Zaretskii <eliz@gnu.org>, 51590@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>

> > > Indeed, I tested with the header-line, and it has the same problem,
> > > so retitled this bug report.

> > > After trial and error, I arrived to the following patch that completely
> > > fixes these problems.  However, I can't explain how it works.

> > I've spent some time on this patch, and I've transformed it into a
> > similar patch that I can explain, and I believe is nearly correct[*].
> > Could you possibly try it out in your system.  Thanks!

> So what's the verdict about posn-at-x-y? does it have a bug when
> tab-line is present, or doesn't it?

There is no bug there.  It was merely me getting confused between tab
lines and tab bars.  The first of these is part of the window, the
second part of the frame.

I closed bug #51632 as notabug late last night.  Sorry I neglected to
put you onto the Cc:.

I think there are still inconsistencies in the documentation with the
terms "window body" and "window text area", but I'll have to look at
that more systematically to find them, if they are there.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2021-11-07 14:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 18:24 bug#51590: Tab-line breaks windows of follow-mode Juri Linkov
2021-11-03 18:35 ` Eli Zaretskii
2021-11-04 17:29   ` bug#51590: follow-mode is broken with header-line and tab-line Juri Linkov
2021-11-04 18:46     ` Eli Zaretskii
2021-11-04 19:06       ` Alan Mackenzie
2021-11-05 21:45       ` Alan Mackenzie
2021-11-06  7:00         ` Eli Zaretskii
2021-11-06 11:50           ` Alan Mackenzie
2021-11-06 12:12             ` Eli Zaretskii
2021-11-06 18:31               ` martin rudalics
2021-11-06 18:40                 ` Eli Zaretskii
2021-11-08 15:36                   ` martin rudalics
2021-11-08 17:32                     ` martin rudalics
2021-11-08 18:47                     ` Eli Zaretskii
2021-11-09 10:14                       ` martin rudalics
2021-11-06 18:44                 ` martin rudalics
2021-11-08 17:59               ` Alan Mackenzie
2021-11-08 18:23                 ` Eli Zaretskii
2021-11-09 10:12                   ` martin rudalics
2021-11-09 10:10                 ` martin rudalics
2021-11-04 18:52     ` martin rudalics
2021-11-07 12:48     ` Alan Mackenzie
2021-11-07 13:14       ` Eli Zaretskii
2021-11-07 14:28         ` Alan Mackenzie [this message]
2021-11-07 17:46       ` Juri Linkov
2021-11-07 19:44         ` Alan Mackenzie
2021-11-07 19:56           ` Juri Linkov
2021-11-08  7:13             ` Alan Mackenzie
2021-11-05  7:42 ` Stefan Kangas
2021-11-05  8:55   ` Juri Linkov
2021-11-05 10:15     ` Stefan Kangas

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=YYfid0bniqj2FoJt@ACM \
    --to=acm@muc.de \
    --cc=51590@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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).