unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: 63472@debbugs.gnu.org, kristofer.hjelmtorp@mailbox.org
Subject: bug#63472: 30.0.50; internal-border-width > 0 "eats" tab-bar for Emacs --pgtk
Date: Sat, 13 May 2023 09:44:06 +0300	[thread overview]
Message-ID: <833540buix.fsf@gnu.org> (raw)
In-Reply-To: <sdvjzxd6k9d.fsf@netyu.xyz> (bug-gnu-emacs@gnu.org)

> Cc: 63472@debbugs.gnu.org
> Date: Sat, 13 May 2023 10:19:08 +0800
> From:  Ruijie Yu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> Kristofer Hjelmtorp via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> writes:
> 
> > The problem is the interaction between the frame parameter 
> > `internal-border-width'
> > and `tab-bar-mode' when Emacs is compiled with '--with-pgtk'. 
> > When `internal-border-width' is larger than 0 and tab-bar-mode is 
> > active the result is that
> > the bottom of the tab bar is overwritten/blocked depending on how 
> > high the value of 
> > `internal-border-width' is. 
> > If you have compile Emacs with '--with-pgtk' you can reproduce 
> > this with:
> > 1. Start Emacs with: 'emacs -Q'
> > 2. In *scratch* buffer, evalute:
> >    (tab-bar-mode +1)
> >    (modify-all-frames-parameters
> >    '((internal-border-width . 10)))
> > 3. The bottom half of the tab bar should now be hidden/blocked. 
> 
> Reproducible on a 3-days-old master, in-source Emacs build.

How about the emacs-29 branch?

At this point, it is much more important to reproduce bugs on the
release branch than on master, TIA.





      parent reply	other threads:[~2023-05-13  6:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 18:38 bug#63472: 30.0.50; internal-border-width > 0 "eats" tab-bar for Emacs --pgtk Kristofer Hjelmtorp via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  2:19 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  2:28   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  6:47     ` Eli Zaretskii
2023-05-13  8:13       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-18 18:47     ` Kristofer Hjelmtorp via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-19  0:52       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13  6:44   ` 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=833540buix.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63472@debbugs.gnu.org \
    --cc=kristofer.hjelmtorp@mailbox.org \
    --cc=ruijie@netyu.xyz \
    /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).