From: Visuwesh via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 49937@debbugs.gnu.org
Subject: bug#49937: 28.0.50; feature/pgtk: tetris blocks are comparatively larger
Date: Mon, 9 Aug 2021 18:48:00 +0200 (CEST) [thread overview]
Message-ID: <Mgfo4Mm--3-2@tutanota.com> (raw)
In-Reply-To: <874kbysiku.fsf@gmail.com>
9 Aug 2021, 21:42 by rpluim@gmail.com:
>>>>>> On Sun, 8 Aug 2021 05:01:29 +0200 (CEST), Visuwesh via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:
>>>>>>
>
> Visuwesh> In tetris, pong and friends, the size of each grid is much larger in
> Visuwesh> the pgtk branch compared to master (see the attached files). However,
> Visuwesh> I'm not sure if this can be considered a bug since the physical size of
> Visuwesh> each grid, measured using a ruler, is 7 mm in the pgtk branch as one
> Visuwesh> would expect from the value of `gamegrid-glyph-height-mm'.
>
> Are they using the same font? You can check by putting point on one of
> the blocks and doing 'C-u C-x ='
>
> Robert
> --
>
Are you sure the font size affects the display? Doing as you suggested, I get
the following.
what-cursor-position: Wrong type argument: arrayp, (image :type xpm :data "/* XPM */
static char *noname[] = {
/* width height ncolors chars_per_pixel */
\"24 24 3 1\",
/* colors */
\"+ s col1\",
\". s col2\",
\"- s col3\",
/* pixels */
\"-----------------------+\",
\"----------------------++\",
\"---------------------+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"---..................+++\",
\"--++++++++++++++++++++++\",
\"-+++++++++++++++++++++++\",
\"++++++++++++++++++++++++\"
};
" :ascent center :color-symbols (("col1" . "#4c4c4c") ("col2" . "#666666") ("col3" . "#7f7f7f")))
next prev parent reply other threads:[~2021-08-09 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 3:01 bug#49937: 28.0.50; feature/pgtk: tetris blocks are comparatively larger Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-09 16:12 ` Robert Pluim
2021-08-09 16:48 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-08-09 21:45 ` Alan Third
2021-08-10 12:51 ` Lars Ingebrigtsen
2021-08-10 14:55 ` Robert Pluim
2021-08-21 12:30 ` Alan Third
2021-08-21 12:47 ` Eli Zaretskii
2021-08-22 9:14 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22 11:53 ` Lars Ingebrigtsen
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=Mgfo4Mm--3-2@tutanota.com \
--to=bug-gnu-emacs@gnu.org \
--cc=49937@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=visuwesh@tutanota.com \
/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).