From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 16013@debbugs.gnu.org
Subject: bug#16013: 24.3.50; Rows in height is interpreted as pixels.
Date: Mon, 02 Dec 2013 23:03:09 +0100 [thread overview]
Message-ID: <871u1u52si.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <529CCE48.9090404@gmx.at> (martin rudalics's message of "Mon, 02 Dec 2013 19:15:36 +0100")
On Mon, 02 Dec 2013 19:15:36 +0100 martin rudalics <rudalics@gmx.at> wrote:
>>> (/ (frame-text-height) (frame-char-height))
>>
>> 47.
>>
>>> (/ (frame-text-width) (frame-char-width))
>>
>> This is a bit random. On 5 starts, I got 79 once, 83 once and 84
>> three times. And the number of columns match, 79, 83 and 84.
>
> My old patch was silly - it propagated the frame's pixel sizes instead
> of the text sizes to xg_frame_set_char_size. Please try the attached
> one. I still have two problems here: The height of the initial frame
> is by six lines too small and a new frame made via C-x 5 2 is two
> lines higher than the initial one.
FYI I applied the new patch and started the rebuilt Emacs with my
initializations, which contain this:
(modify-frame-parameters nil '((width . 85) (fullscreen . fullheight)))
However, window-width in fact returned 73 (but window-height was the full
height). Then I evalled this:
(modify-frame-parameters nil '((width . 85)))
Now, window-width was 78. (Maybe the increase despite the same passed
width value is because I customize the tool bar to appear on the left
side, and maybe that takes effect after the initial frame width is set.)
To get a window-width of 85 columns, I had to give the width
frame-parameter a value of 92.
This is with the xft backend and font
-unknown-DejaVu Sans Mono-normal-normal-normal-*-12-*-*-*-m-0-iso10646-1
Steve Berman
next prev parent reply other threads:[~2013-12-02 22:03 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 [this message]
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
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=871u1u52si.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=16013@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).