From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16013@debbugs.gnu.org, jan.h.d@swipnet.se
Subject: bug#16013: 24.3.50; Rows in height is interpreted as pixels.
Date: Wed, 09 Sep 2020 17:46:21 +0300 [thread overview]
Message-ID: <837dt3knya.fsf@gnu.org> (raw)
In-Reply-To: <87o8mf9jzs.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 09 Sep 2020 15:07:19 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 09 Sep 2020 15:07:19 +0200
> Cc: "16013@debbugs.gnu.org" <16013@debbugs.gnu.org>,
> Jan Djärv <jan.h.d@swipnet.se>
>
> martin rudalics <rudalics@gmx.at> writes:
>
> > I would proceed as follows: For the release, apply the attached patch.
>
> [...]
>
> > After the release I would try to change the behavior such that when a
> > frame is created, the toolbar is not counted in the text height on these
> > builds.
>
> This was six years ago (and this was the final email in the thread), and
> I seem to recall a large number of tweaks done to this area, so I'm not
> sure whether this bug report should be closed? It seems like the
> original reported bug was fixed by Martin at the time, but then there
> were some followup considerations...
Martin should tell, but from where I stand, we already have a
satisfactory solution to these issues. It took us (took Martin,
really) a lot of blood, sweat, and tears to get there, but the results
seems to be OK, as I've not seen any complaints about that for quite
some time.
next prev parent reply other threads:[~2020-09-09 14:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 13:08 bug#16013: 24.3.50; Rows in height is interpreted as pixels Jan Djärv
2013-11-30 15:00 ` martin rudalics
2013-11-30 18:52 ` Jan Djärv
2013-12-01 9:44 ` martin rudalics
2013-12-01 10:01 ` Jan Djärv
2013-12-01 11:24 ` martin rudalics
2013-12-01 12:02 ` Jan Djärv
2013-12-02 18:15 ` martin rudalics
2013-12-02 22:03 ` Stephen Berman
2013-12-03 7:56 ` martin rudalics
2013-12-03 9:13 ` Stephen Berman
2013-12-03 18:34 ` martin rudalics
2013-12-03 20:02 ` Stephen Berman
2013-12-03 7:53 ` Jan Djärv
2013-12-03 7:58 ` martin rudalics
2013-12-03 16:30 ` Jan Djärv
2013-12-03 18:34 ` martin rudalics
2013-12-03 19:30 ` Jan Djärv
2013-12-03 19:45 ` Jan Djärv
2013-12-04 18:06 ` martin rudalics
2013-12-07 17:53 ` Jan Djärv
2013-12-07 18:09 ` martin rudalics
2013-12-09 18:26 ` martin rudalics
2014-01-11 14:01 ` martin rudalics
2014-01-11 17:46 ` Jan Djärv
2014-01-12 9:54 ` martin rudalics
2014-01-12 11:13 ` Jan Djärv
2014-01-12 11:46 ` martin rudalics
2014-01-12 20:25 ` Stefan Monnier
2014-01-12 22:21 ` Jan Djärv
2014-01-14 17:30 ` Jan Djärv
2014-01-14 18:10 ` martin rudalics
2014-01-16 10:03 ` martin rudalics
2014-01-16 10:14 ` martin rudalics
2014-01-18 11:30 ` Jan Djärv
2014-01-18 12:07 ` martin rudalics
2014-01-29 10:14 ` martin rudalics
2020-09-09 13:07 ` Lars Ingebrigtsen
2020-09-09 14:46 ` Eli Zaretskii [this message]
2020-09-10 12:40 ` Lars Ingebrigtsen
2013-12-04 18:06 ` martin rudalics
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=837dt3knya.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16013@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=larsi@gnus.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).