From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51632@debbugs.gnu.org, acm@muc.de
Subject: bug#51632: Emacs 28: posn-at-x-y fails to take a tab line into account.
Date: Sat, 6 Nov 2021 20:22:10 +0100 [thread overview]
Message-ID: <73507221-d99e-de54-5f51-370d6ba9c648@gmx.at> (raw)
In-Reply-To: <83mtmh9jxj.fsf@gnu.org>
>> From: martin rudalics <rudalics@gmx.at>
>> Date: Sat, 6 Nov 2021 19:50:23 +0100
>>
>> > (i) emacs -Q
>> > (ii) C-u C-h i <and info file> RET
>> > (iii) M-: (point) ; Note this value
>> > (iv) M-: (posn-at-x-y 0 18) ; Where 18 is the height of your default
>> > font. Note that the second element of the result matches that from
>> > (iii)
>> >
>> > (v) M-x tab-bar-mode RET
>> > (vi) M-: (posn-at-x-y 0 18) ; This returns the same as (iv).
>> >
>> > Because of the tab line, (vi) should return the symbol `header-line' in
>> > its second element, not the same as (iv). This is a bug.
>>
>> I'm not sure I understand. 'tab-bar-mode' puts a tab bar on top of the
>> frame. How is this related to 'posn-at-x-y' which, by default, deals
>> with the selected window?
>
> It should be "tab-line-mode".
In that case I get with emacs -Q on the release branch the following in
my *Messages* buffer:
Composing main Info directory...done
(#<window 3 on *info*> 173 (0 . 0) 0 (#("(dir)Top
" 0 8 (font-lock-face info-header-node)) . 0) 173 (0 . 0) nil (0 . 0) (9 . 18))
Tab-Line mode enabled in current buffer
(#<window 3 on *info*> header-line (8 . 18) 0 (#("No next, prev or up links -- This is the top of the INFO tree" 31 63 (fontified nil)) . 0) nil (0 . -1) nil (8 . 1) (9 . 18))
martin
prev parent reply other threads:[~2021-11-06 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 12:42 bug#51632: Emacs 28: posn-at-x-y fails to take a tab line into account Alan Mackenzie
2021-11-06 18:50 ` martin rudalics
2021-11-06 19:13 ` Eli Zaretskii
2021-11-06 19:22 ` martin rudalics [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=73507221-d99e-de54-5f51-370d6ba9c648@gmx.at \
--to=rudalics@gmx.at \
--cc=51632@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.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).